Connect <relations> more specifically with elements that already represent other entities related to the material described

[kerstarno]

Creator of issue

1. Kerstin Arnold
2. EAD team lead, TS-EAS
3. @kerstarno
4. [email protected]

The issue relates to

• EAC-CPF schema issue
• EAC-CPF Tag Library issue
• EAD schema issue
• EAD Tag Library issue
• Schema issue
• Tag Library issue
• Suggestions for all schemas
• Suggestions for all Tag Libraries
• Other

Wanted change/feature

• Text: Apart from aligning <relations> with the way of encoding in EAC-CPF 2.0 (see Align <relations> across EAD and EAC-CPF #33), the EAD sub-team decided during their meeting on 15 December 2023 to connect <relations>, <relation> and its sub-elements more directly to those EAD elements that already represent other entities related to the materials being described rather than keeping it as a separate section within <archDesc> and the numbered and unnumbered <c> elements. With this, the experimental status of the element as defined in the context of EAD3 is meant to be lifted and next to naming a related entity and possibly pointing to an external vocabulary for a detailed description of such entity, there will now also be the option to describe the relationship between this entity and the materials being described directly within the relevant context. The changes listed below are a result of this conceptual shift.

Note for working on and testing this issue: When the schema changes are done in development branch, please mark this by ticking the box on the higher level of the list (printed in bold); once the changes have been tested successfully please mark this by ticking the box on the lower levels of the list and - if applicable - the intermediate levels (printed in italics).

• Remove <relations> from
  • <archDesc>
  • <c>>
  • <c01>
  • <c02>
  • <c03>
  • <c04>
  • <c05>
  • <c06>
  • <c07>
  • <c08>
  • <c09>
  • <c10>
  • <c11>
  • <c12>
• Add <relations> as optional, but not repeatable sub-element to
  • <otherFindAid>
  • <publicationNote> (renamed from < bibliography>, see Rename certain elements for better alignment with ISAD(G), DACS, etc. respectively for being better understandable #66)
  • <relatedMaterial>
  • <separatedMaterial>
  • The new <formAvailable>, which will incorporate <altformavail>, <originalsloc> and <dao> (see Add new element <formAvailable> to encode any type of instantiations of the materials described #65)

There are four more elements - <agent>, <function>, <place>, and <subject> - which fall into the same category of EAD elements, but will have different content models as they already include a series of sub-elements of <relation> anyway. Hence, only the "missing pieces" will be added as further optional sub-elements to these.

See separate issues #42, #58, #61, and #67 for details.

[kerstarno]

Tested with the XSD and the RNG and can confirm that <relations> does not exist in the first list of elements above anymore, but is now available in the second list of elements.