...
- A top level
record tag - A container
instances tag - Individual vocabulary
instance tags
| Code Block |
|---|
|
<record id="organization" type="authority">
<instances id="organization">
<instance id="organization-organization">
...
|
|
and then for each Organization vocabulary instance matched within that <instances> block, it inserts a new tag, <nptAllowed>false</nptAllowed>, that will be merged into the default configuration file's settings:
| Code Block |
|---|
|
<instance id="organization-organization">
<nptAllowed>false</nptAllowed>
...
|
|
Testing your merged changes
...
Within most or all of the configuration files in the Application layer's defaults folder, are tags similar to this one, found in the default configuration file for Loan Out records:
| Code Block |
|---|
|
<include src="domain-procedure-loanout. | " strip-root="yes"/>
|
|
This means that, if you take a default configuration file, such as base-procedure-loanout.xml, from within the defaults folder, 'clone' (copy) that file into your tenant folder, and change base to domain at the start of its name (e.g. domain-procedure-loanout.xml), this would then become an "includes" file.
...
By default, most of the entries in that file each reference a single base- configuration file; for example:
| Code Block |
|---|
|
<include src="base-procedure-intake.xml"/>
<include src="base-procedure-loanin.xml"/>
<include src="base-procedure-loanout.xml"/>
|
|
However, if you edit one or more of these entries to include a comma-separated list of configuration files, you will set up an overlay mechanism specifically for that particular record type (or other discrete unit of configuration listed in the main configuration file). E.g.:
| Code Block |
|---|
|
<include src="mymuseum-procedure-intake-overlay1. | ,mymuseum-procedure-intake-overlay2.xml,base-procedure-intake.xml"/>
|
|
This entry specifies that settings will be used from whichever of the files mymuseum-procedure-intake-overlay1.xml, mymuseum-procedure-intake-overlay2.xml, and base-procedure-intake.xml is found first, in that order. And that means that, if you add a mymuseum-procedure-intake-overlay1.xml or mymuseum-procedure-intake-overlay2.xml file to your tenant folder, it will overlay (replace outright) the settings in the default configuration file, base-procedure-intake.xml:
...