kerstarno
commented
1 year ago In terms of conversion, the main aspects are:
<resourceRelation>and<eagRelation>are transformed into<relation>@resourceRelationTypeand@eagRelationTypeare transformed into<relationType>and will be expressed as RiC properties along with the appropriate RiC-O URIs in the attribute@valueURIof<relationType>(i.e. https://www.ica.org/standards/RiC/ontology#isCreatorOf or https://www.ica.org/standards/RiC/ontology#isOrWasSubjectOf or https://www.ica.org/standards/RiC/ontology#isRelatedTo in@valueURIand is creator of (RiC-R027i) OR is or was subject of (RiC-R019i) OR is related to (RiC-R001) in<relationType>for the equivalent values of@resourceRelationTypeand https://www.ica.org/standards/RiC/ontology#hasChild or https://www.ica.org/standards/RiC/ontology#isChildOf or https://www.ica.org/standards/RiC/ontology#hasAncestor or https://www.ica.org/standards/RiC/ontology#hasDescendant or https://www.ica.org/standards/RiC/ontology#isAgentAssociatedWithAgent in@valueURIand has child (RiC-R018) OR is child of (RiC-R018i) OR has ancestor (RiC-R017i) OR has descendant (RiC-R017) OR is agent associated with agent (RiC-R044) in<relationType>for the equivalent values of@eagRelationType<relationEntry>is transformed into<targetEntity><part>- If there is more than one
<relationEntry>per<resourceRelation>or<eagRelation>, these are transformed into repeated<part>-s within the same<targetEntity>as<targetEntity>cannot be repeated - For a
<resourceRelation><relationEntry>, the<targetEntity>gets the@targetType="resource", while for an<eagRelation><relationEntry>, the<targetEntity>gets the `@targetType="corporateBody" - If
<resourceRelation>or<eagRelation>include an@href, this is transformed into@valueURIfor<targetEntity>as<relation>itself cannot hold a link or URI of any kind
- If there is more than one
<placeEntry>within<resourceRelation>is transformed into<place><placeName>within<relation>- If there is more than one
<placeEntry>, these are transformed into repeated<place>-s with one<placeName>sub-element
- If there is more than one
- Any date elements,
<descriptiveNote>-s or<objectXMLWrap>-s are kept as they are - Any
<objectBinWrap>-s are removed without a replacement- It might be useful to consider having the conversion script generate a message about this
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:
<eagRelation>and<resourceRelation>are to be removed and the general<relation>element following the content model as established in EAC-CPF 2.0 is to be added insteadChange 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):
<relations>Add to
Parent element(s):
<relations>Change in availability
For elements, give an indication of their changed availability within each affected 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 added attributes, indicate their changed availability with "1" for required or "0" for optional within each affected parent element. Changed availability:
<relation>will be mandatory and repeatable in<relations>, i.e 1..nChange in content model (elements)
List all sub-elements and attributes that should be removed from or added to the element's content model. For an example encoding and a conversion example see #103