[Major revision] Change overall structure of EAG

[kerstarno]

Creator of issue

State your name, organisation and ways to reach you.
Name: Kerstin Arnold
Organisation: Archives Portal Europe Foundation, Working Group on Standards
Email: standards@archivesportaleurope.net
GitHub username (if applicable): @kerstarno

Current status

• In EAG 2012, the root element <eag>, includes three sub-elements: <control> (mandatory), <archguide> (mandatory), and <relations>(optional). <archguide> then includes the sub-elements <identity> and <desc> with the latter including the element <repositories> that needs to hold one or more <repository> elements and can hold one or more <image> elements. The single <repository> element includes all the descriptive information including the <image> element.

EAC-CPF / EAD3 reconciliation

This section relates the revision of EAG 2012 to the ongoing major revision of the related standard EAC-CPF. There also might be references to the expected major revision of EAD3 in future.

• In order to align the overall structure of EAG more with that of EAC-CPF, in EAG 3.0, the root element <eag> is to only include the sub-elements <control> and a choice between either a single <repository> element or a plural <repositories> elements, which must have at least two <repository> elements. Both, <repository> and <repositories>, can include the <relations> element and one or more <image> elements. The single <repository> element then holds the sub-elements <identity> and <description> (renamed from <desc>).

EAG specific changes and conversion routes

This section lists any aspects of the current element which could be up for change and/or review.

• Move <repositories> and <repository> up to being direct sub-elements of <eag> and establish a choice between them to use either/or
• Move <identity> from <archguide> into <repository>
• Put a wrapper element <description> around all current sub-elements of <repository>
• Remove <desc> from <archguide>
• Remove <archguide> from <eag>
• Move <relations> from <eag> into <repositories> and <repository> alike
  • When converting EAG 2012 files, move an existing <relations> element into <repositories> when there is more than one <repository> included and into <repository> when there is only one

Change requests from the community

This section lists change requests sent in by the community.

• n/a

Encoding examples from the community

Please include your examples below.

• n/a

[kerstarno]

An updated encoding for the element <eag> could then look like this:

<eag xmlns="https://www.archivesportaleurope.net/schemas/eag/eag3.0.xsd" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" audience="external" 
base="http://censoarchivos.mcu.es/CensoGuia/" id="e1" languageOfElement="spa" 
scriptOfElement="Latn">
  <control>[...]</control>
  <repositories>
    <repository>[...]</repository>
    <repository>[...]</repository>
  </repositories>
</eag>

respectively

<eag xmlns="https://www.archivesportaleurope.net/schemas/eag/eag3.0.xsd" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" audience="external" 
base="http://censoarchivos.mcu.es/CensoGuia/" id="e1" languageOfElement="spa" 
scriptOfElement="Latn">
  <control>[...]</control>
  <repository>[...]</repository>
</eag>

[kerstarno]

For conversion, the current encoding

<eag>
   <control>
      [...]
   </control>
   <archguide>
      <identity>
         [...]
      </identity>
      <desc>
         <repositories>
            <repository>
               [sub-elements of repository]
            </repository>
         </repositories>
      </desc>
   </archguide>
</eag>

or

<eag>
   <control>
      [...]
   </control>
   <archguide>
      <identity>
         [...]
      </identity>
      <desc>
         <repositories>
            <repository>
               [sub-elements of repository]
            </repository>
            <repository>
               [sub-elements of repository]
            </repository>
         </repositories>
      </desc>
   </archguide>
</eag>

would change to

<eag>
   <control>
      [...]
   </control>
   <repository>
      <identity>
         [...]
      </identity>
      <description>
         [sub-elements of former repository]
      </description>
   </repository>
</eag>

or

<eag>
   <control>
      [...]
   </control>
   <repositories>
      <repository>
         <identity>
            [...]
         </identity>
         <description>
            [sub-elements of first former repository]
         </description>
      </repository>
      <repository>
         <identity>
            [... - use content of <repositoryName> within second former repository to create <nameEntry><part>]
         </identity>
         <description>
            [sub-elements of second former repository]
         </description>
      </repository>
   </repositories>
</eag>