<?xml version="1.0" encoding="UTF-8"?>
<!-- order of configuration is:
1.) project name and step name matches
2.) step name matches and project is *
3.) project name matches and step name is *
4.) project name and step name are *
<!-- which projects to use for (can be more then one, otherwise use *) -->
<!-- name of the API user -->
<!-- password of the API user -->
<apiPassword>password</apiPassword>
<!-- URI of the URN API, must use httos -->
<apiUri>https://api.nbn-resolving.org/v2/</apiUri>
<!-- namespace in which new URNs shall be created -->
<!-- example urn:nbn:de:gbv:{SIGIL} -->
<namespace>urn:nbn:de:{SIGIL}</namespace>
<!-- infix that you want to use (optional) -->
<!-- example URN urn:nbn:de:gbv:48-goobi-20220404122233 -->
<!--target url the newly generated urn will forward to. {pi.urn} will be
replaced with the newly minted urn -->
<publicationUrl>https://viewer.example.org/viewer/resolver?urn={pi.urn}
<!--Generate URN for the work (e.g. for Monograph, Manuscript, Volume, etc.) -->
<!--Generate URN for the anchor Element -->
<!--Elements listed here will receive a URN. If work is set to true the
work element will receive a URN, even if it is not listed here -->
<!-- metadata name for urns in METS-bloc "_urn" -->
<typeNameMets>_urn</typeNameMets>
<!--metadata name for URNs in MODS-bloc. -->
<typeNameMods>URN</typeNameMods>
<!--Shall the plugin create URNs in the MODS-bloc. The rule set entries
of certain elements may have to be altered, if you wish to use this -->
<createModsUrns>false</createModsUrns>