ArchivesPortalEuropeFoundation / EAG2012

Maintenance of EAG2012, the Encoded Archival Guide for describing institutions with archival holdings
5 stars 1 forks source link

[Major revision] Replace <adminhierarchy> and <adminunit> with <structureOrGenealogy> #136

Open kerstarno opened 1 year ago

kerstarno commented 1 year ago

Provide a general summary of the issue in the Title above. Delete the part of the issue template that does not apply depending on whether you describe a change to an existing element / attribute or the addition of a new one.

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

Changes to existing element / attribute

Give the current name of the element / attribute. Include the tag name and the full name. Name: <adminhierarchy> and its sub-element <adminunit>

Change in context

List all parent elements to which the element / attribute should be added. Furthermore, list all parent elements from which the element / attribute should be removed.

Remove from

Parent element(s): Remove <adminhierarchy> from <repository>

New element / attribute

Give the name of the new element / attribute. Include the tag name and the full name. Name: <structureOrGenealogy>

Context and availability

List all parent elements to which the element / attribute should be added. For elements, give an indication of their availability within each parent element ("1..1" for required but not repeatable, "1 (or another number)..n" for required and repeatable, "0..1" for optional but not repeatable", "0..n" for optional and repeatable). For attributes, indicate their availability with "1" for required or "0" for optional within each parent element. Parent element(s): <structureOrGenealogy> is added as an optional and repeatable sub-element of <description> (0..n)

Content model (elements)

List all sub-elements and attributes of the new element. For sub-elements, give an indication of their availability ("1..1" for required but not repeatable, "1 (or another number)..n" for required and repeatable, "0..1" for optional but not repeatable", "0..n" for optional and repeatable). For attributes, indicate their availability with "1" for required or "0" for optional. Sub-element(s): <head> (0..1), <list> (0..n), <p> (0..n) Attributes (with default values, if applicable): @audience with values "external", "internal" (0), @id (0), @languageOfElement (0), @scriptOfElement (0), @target (0); @localType (0), @localTypeDeclarationReference (0); @conventionDeclarationReference (0), @maintenanceEventReference (0), @sourceReference; option to include attributes from any other namespace

Example of XML code

Provide a sample encoding in XML of the new / changed element (with potential attributes). Write your text after the "Example:" below. Example:

<structureOrGenealogy>
  <list>
    <item>1. Dirección</item>
    <list>
      <item>1.1 Subdirección</item>
      <item>1.2 Descripción</item>
      <item>1.3 Referencia y Difusión</item>
      <list>
        <item>1.3.1 Información</item>
        <item>1.3.2 Reprografía</item>
        <item>1.3.3 Biblioteca Auxiliar</item>
      </list>
      <item>1.4 Conservación y Restauración</item>
      <item>1.5 Administración</item>
    </list>
  </list>
</structureOrGenealogy>
kerstarno commented 1 year ago

For conversion, the current encoding

<adminhierarchy>
  <adminunit xml:lang="[language of adminunit 1]" source="[source of adminunit 1]">1. Dirección</adminunit>
  <adminunit xml:lang="[language of adminunit 2]" source="[source of adminunit 2]">1.1 Subdirección</adminunit>
  <adminunit xml:lang="[language of adminunit 3]" source="[source of adminunit 3]">1.2 Descripción</adminunit>
  <adminunit xml:lang="[language of adminunit 4]" source="[source of adminunit 4]">1.3 Referencia y Difusión</adminunit>
  [...]
</adminhierarchy>

becomes

<control>
  [...]
  <sources>
    <source id="source1">
      <reference>source of adminunit 1</reference>
    </source>
    <source id="source2">
      <reference>source of adminunit 2</reference>
    </source>
    <source id="source3">
      <reference>source of adminunit 3</reference>
    </source>
    <source id="source4">
      <reference>source of adminunit 4</reference>
    </source>
  </sources>
  [...]
<structureOrGenealogy>
  <list>
    <item languageOfElement="[language of adminunit 1]" sourceReference="#source1">1. Dirección</item>
    <item languageOfElement="[language of adminunit 2]" sourceReference="#source2">1.1 Subdirección</item>
    <item languageOfElement="[language of adminunit 3]" sourceReference="#source3">1.2 Descripción</item>
    <item languageOfElement="[language of adminunit 4]" sourceReference="#source4">1.3 Referencia y Difusión</item>
    [...]
  </list>
</structureOrGenealogy>