Skip to content

Commit 96993c4

Browse files
committed
Merge pull request 'Release v25.07' (#55) from release_25.07 into master
2 parents 33adff7 + 5d5b926 commit 96993c4

File tree

32 files changed

+951
-128
lines changed

32 files changed

+951
-128
lines changed

docs/03_config/de.md

Lines changed: 39 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Des weiteren gibt es noch eine Reihe weiterer optionaler Angaben:
6060
| `@showField` | Definiert, ob das Feld in der Detailanzeige geöffnet angezeigt wird, auch wenn noch kein Wert vohanden ist. Das Feld darf die beiden Werte `true` und `false` \(default\) enthalten. |
6161
| `@rulesetName` | Hier kann ein Metadatum aus dem Regelsatz angegeben werden. Wenn für den Knoten ein Goobi-Vorgang erstellt wird, wird das konfigurierte Metadatum erstellt. |
6262
| `@importMetadataInChild` | Hierüber kann gesteuert werden, ob das Metadatum auch in Goobi-Vorgängen von Kind-Knoten erstellt werden soll. Das Feld darf die beiden Werte `true` und `false` \(default\) enthalten. |
63-
| `@fieldType` | Steuert das Verhalten des Feldes. Möglich sind `input` \(default\) , `textarea`, `dropdown`, `multiselect`, `vocabulary`, `nodelink`, `gnd`, `geonames`, `viaf` |
63+
| `@fieldType` | Steuert das Verhalten des Feldes. Möglich sind `input` \(default\) , `textarea`, `dropdown`, `multiselect`, `vocabulary`, `nodelink`, `gnd`, `geonames`, `viaf`, `group`, `person`, `corporate` |
6464
| `value` | Dieses Unterelement wird nur bei den beiden Typen `dropdown` und `multiselect` genutzt und enthält die möglichen Werte, die zur Auswahl stehen sollen. |
6565
| `vocabulary` | Dieses Unterelement enthält den Namen des zu verwendenden Vokabulars. Es wird nur ausgewertet, wenn `vocabulary`, `dropdown` oder `multiselect` im Typ des Feldes gesetzt ist und keine `<value>` Elemente konfiguriert wurden. Die Auswahlliste enthält jeweils den Hauptwert der Records. |
6666
| `searchParameter` | Mit diesem wiederholbaren Unterfeld können Suchparameter definiert werden, mit denen das Vokabular gefiltert wird, die Syntax ist `fieldname=value`. |
@@ -185,6 +185,44 @@ Es können auch mehrere Validierungsregeln kombiniert werden, zum Beispiel `uniq
185185
![VIAF Feld](screen20_de.png)
186186

187187

188+
## Gruppierte Felder
189+
```xml
190+
<metadata xpath="./ead:archdesc/ead:did/ead:repository" group="true" name="repository" level="1" repeatable="true" visible="false" fieldType="group" rulesetName="Repository">
191+
<metadata xpath="@label" xpathType="attribute" name="repositoryLabel" level="1" repeatable="false" visible="true" rulesetName="RepositoryLabel" />
192+
<metadata xpath="ead:address/ead:addressline" xpathType="element" name="repositoryaddressline" level="1" repeatable="true" visible="true" rulesetName="RepositoryAddress" />
193+
<metadata xpath="ead:extref/@href" xpathType="attribute" name="extrefhref" level="1" repeatable="true" visible="true" rulesetName="RepositoryLink" />
194+
<metadata xpath="ead:extref" xpathType="element" name="extref" level="1" repeatable="true" visible="true" rulesetName="RepositoryLinkName" />
195+
</metadata>
196+
```
197+
198+
![Gruppiertes Feld](screen21_de.png)
199+
200+
201+
## Personen
202+
```xml
203+
<metadata xpath="(./ead:archdesc/ead:indexentry/ead:persname[@relator='aut'] | ./ead:indexentry/ead:persname[@relator='aut'])" name="Author" level="2" repeatable="true" visible="true" fieldType="person" rulesetName="Author">
204+
<lastname xpath="ead:part[@localtype='surname']" xpathType="element" />
205+
<firstname xpath="ead:part[@localtype='givenname']" xpathType="element" />
206+
<authorityValue xpath="@identifier" xpathType="attribute" />
207+
</metadata>
208+
```
209+
210+
![Person](screen22_de.png)
211+
212+
213+
## Körperschaften
214+
```xml
215+
<metadata xpath="(./ead:archdesc/ead:indexentry/ead:corpname[@relator='his'] | ./ead:indexentry/ead:corpname[@relator='his'])" name="HostInstitution" level="2" repeatable="true" visible="true" fieldType="corporate" rulesetName="HostInstitution">
216+
<value xpath="ead:part[@localtype='corporate name']" xpathType="element" />
217+
<subvalue xpath="ead:part[@localtype='subordinate unit']" xpathType="element" />
218+
<partvalue xpath="ead:part[@localtype='part/section/meeting']" xpathType="element" />
219+
<authorityValue xpath="@identifier" xpathType="attribute" />
220+
</metadata>
221+
```
222+
223+
![Körperschaft](screen23_de.png)
224+
225+
188226
## Konfiguration der Anzeige der Bereiche
189227
In der Standardeinstellung sind die einzelnen Bereiche 1. `Identifikation`, 2. `Kontext`, 3. `Inhalt und innere Ordnung`, 4. `Zugangs- und Benutzungsbedingungen`, 5. `Sachverwandte Unterlagen`, 6. `Anmerkungen` und 7. `Verzeichnungskontrolle` aus Platzgründen eingeklappt und werden nicht angezeigt. Damit sie bereits beim auswählen eines Knotens ausgeklappt und angezeigt werdden, kann das Element `<showGroup level="1" />` verwendet werden. Über die Ordnungsnummer im Attribut level wird gesteuert, welcher Bereich ausgeklappt wird. Um auch unausgefüllte Metadaten gleich anzuzeigen, ohne sie mittels Badge hinzuzufügen, kann innerhalb der `<metadata>` Definition das Attribut `showField="true"` genutzt werden.
190228

docs/03_config/en.md

Lines changed: 39 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ There are also a number of other optional details:
5959
| `@showField` | Defines whether the field is displayed open in the detail display, even if no value is yet available. The field may contain the two values `true` and `false` \(default\). |
6060
| `@rulesetName` | A metadata from the rule set can be specified here. When a Goobi process is created for the node, the configured metadata is created. |
6161
| `@importMetadataInChild` | This can be used to control whether the metadata should also be created in Goobi processes of child nodes. The field may contain the two values `true` and `false` \(default\). |
62-
| `@fieldType` | Controls the behaviour of the field. Possible are `input` \(default\) , `textarea`, `dropdown`, `multiselect`, `vocabulary`, `nodelink`, `gnd`, `geonames`, `viaf` |
62+
| `@fieldType` | Controls the behaviour of the field. Possible are `input` \(default\) , `textarea`, `dropdown`, `multiselect`, `vocabulary`, `nodelink`, `gnd`, `geonames`, `viaf`, `group`, `person`, `corporate` |
6363
| `value` | This sub-element is only used for the two types ‘dropdown’ and ‘multiselect’ and contains the possible values that are to be available for selection. |
6464
| `vocabulary` | This sub-element contains the name of the vocabulary to be used. It is only evaluated if `vocabulary`, `dropdown` or `multiselect` is set in the field type and no `<value>` elements have been configured. The selection list contains the main value of each record. |
6565
| `searchParameter` | This repeatable subfield can be used to define search parameters with which the vocabulary is filtered, the syntax is `fieldname=value`. |
@@ -184,6 +184,44 @@ Several validation rules can also be combined, for example `unique+required`, `r
184184
![VIAF field](screen20_en.png)
185185

186186

187+
## Grouped fields
188+
```xml
189+
<metadata xpath="./ead:archdesc/ead:did/ead:repository" group="true" name="repository" level="1" repeatable="true" visible="false" fieldType="group" rulesetName="Repository">
190+
<metadata xpath="@label" xpathType="attribute" name="repositoryLabel" level="1" repeatable="false" visible="true" rulesetName="RepositoryLabel" />
191+
<metadata xpath="ead:address/ead:addressline" xpathType="element" name="repositoryaddressline" level="1" repeatable="true" visible="true" rulesetName="RepositoryAddress" />
192+
<metadata xpath="ead:extref/@href" xpathType="attribute" name="extrefhref" level="1" repeatable="true" visible="true" rulesetName="RepositoryLink" />
193+
<metadata xpath="ead:extref" xpathType="element" name="extref" level="1" repeatable="true" visible="true" rulesetName="RepositoryLinkName" />
194+
</metadata>
195+
```
196+
197+
![Grouped field](screen21_en.png)
198+
199+
200+
## Persons
201+
```xml
202+
<metadata xpath="(./ead:archdesc/ead:indexentry/ead:persname[@relator='aut'] | ./ead:indexentry/ead:persname[@relator='aut'])" name="Author" level="2" repeatable="true" visible="true" fieldType="person" rulesetName="Author">
203+
<lastname xpath="ead:part[@localtype='surname']" xpathType="element" />
204+
<firstname xpath="ead:part[@localtype='givenname']" xpathType="element" />
205+
<authorityValue xpath="@identifier" xpathType="attribute" />
206+
</metadata>
207+
```
208+
209+
![Person](screen22_en.png)
210+
211+
212+
## Corporates
213+
```xml
214+
<metadata xpath="(./ead:archdesc/ead:indexentry/ead:corpname[@relator='his'] | ./ead:indexentry/ead:corpname[@relator='his'])" name="HostInstitution" level="2" repeatable="true" visible="true" fieldType="corporate" rulesetName="HostInstitution">
215+
<value xpath="ead:part[@localtype='corporate name']" xpathType="element" />
216+
<subvalue xpath="ead:part[@localtype='subordinate unit']" xpathType="element" />
217+
<partvalue xpath="ead:part[@localtype='part/section/meeting']" xpathType="element" />
218+
<authorityValue xpath="@identifier" xpathType="attribute" />
219+
</metadata>
220+
```
221+
222+
![Corporate](screen23_en.png)
223+
224+
187225
## Configuration of the display of the areas
188226
In the default setting, the individual sections 1 `Identification`, 2 `Context`, 3 `Content and internal organisation`, 4 `Access and usage conditions`, 5 `Related documents`, 6 `Notes` and 7 `Directory control` are collapsed for reasons of space and are not displayed. The element `<showGroup level=‘1’ />` can be used so that they are already expanded and displayed when a node is selected. The ordinal number in the level attribute is used to control which area is expanded. The attribute `showField=‘true’` can be used within the `<metadata>` definition to display unfilled metadata immediately without adding it using a badge.
189227

docs/03_config/screen21_de.png

13.9 KB
Loading

docs/03_config/screen21_en.png

12.6 KB
Loading

docs/03_config/screen22_de.png

15.3 KB
Loading

docs/03_config/screen22_en.png

15.6 KB
Loading

docs/03_config/screen23_de.png

24.1 KB
Loading

docs/03_config/screen23_en.png

27.1 KB
Loading

0 commit comments

Comments
 (0)