Establish <agent> more as a related entity rather than a piece of descriptive information #58
Closed
18 of 27 tasks
Labels
Control
This issue relates to the control attribute
EAC minor revisions
This issue is part of the annual minor revisions cycle for EAC-CPF
EAC schema
This relates to a change in the schema for EAC-CPF
EAD major revision (EAD 4.0)
This issue is part of the EAD major revision towards EAD 4.0
EAD Schema (general)
This relates to a change in the general schema for EAD
ead-archDesc
This issue relates to the ead-archDesc module
ead-findAidDesc
This issue relates to the ead-findAidDesc module (currently still named ead-fileDesc)
Implemented in draft version
This has been implemented in draft version
Milestone
Creator of issue
The issue relates to
Wanted change/feature
Add a new attribute@agentRole
to<agent>
. This will not only help to differentiate e.g. between an employee and a volunteer when used in the context of<maintenanceEvent>
, but also to differentiate between the author, publisher, and possibly sponsor when used in the context of<findAidDesc>
. Also applies to EAC-CPF.<agent>
as discussed and confirmed by the EAD sub-team during their meeting on 15 December 2023.<agent>
, along with<function>
(Establish <function> more as a related entity rather than a piece of descriptive information #61) and<formAvailable>
(Add new element <formAvailable> to encode any type of instantiations of the materials described #65), is to be established more as a related entity rather than a piece of descriptive information. It will be made available in a new and dedicated part of the archival description part of EAD (Create a separate section for elements established as entities #68), apart from already being available in<findAidDesc>
(Add <findAidDesc> as replacement of <filedesc> #27) and in<control>
under<maintenanceEvent>
(Align <control> across EAD and EAC-CPF #32).<agent>
will combine and replace all current elements that refer to an agent as a related entity, i.e.<origination>
and<repository>
, but also<corpname>
,<famname>
,<name>
, and<persname>
as sub-elements of<controlaccess>
and<index>
(for the changes in the latter two see Rename <controlaccess> to <subjectHeadings> and combine with <index> #67).Note for working on and testing this issue: When the schema changes are done in development branch, please mark the tasks on the highest levels of the list (printed in bold) by ticking the box. When the changes have been tested successfully, please mark the tasks on the lowest level of the list.
Add@agentRole
as an optional attribute to<agent>
Make@agentRole
of data type "token"<agent>
as follows:<agent>
cannot include text<agent>
includes<agentName>
as a required and repeatable sub-element<agent>
includes<agentType>
and<agentRole>
as optional and repeatable sub-elements<agentName>
,<agentRole>
, and<agentType>
all have the same content model by allowing the elements to contain text, by enabling the optional attributes@audience
,@id
,@target
,@languageOfElement
,@scriptOfElement
,@conventionDeclarationReference
,@maintenanceEventReference
,@sourceReference
,@localType
,@localTypeDeclarationReference
,@valueURI
,@vocabularySource
, and@vocabularySourceURI
, and by allowing for attributes from any other namespace<agent>
includes<relationType>
as a optional and repeatable sub-element<agent>
allows for the optional sub-elements<date>
,<dateRange>
, or<dateSet>
(choice between these three, not repeatable),<placeName>
(repeatable), and<descriptiveNote>
(not repeatable)<agent>
allows for the optional attributes@audience
,@id
,@target
,@languageOfElement
,@scriptOfElement
,@conventionDeclarationReference
,@maintenanceEventReference
,@sourceReference
,@localType
,@localTypeDeclarationReference
,@valueURI
,@vocabularySource
, and@vocabularySourceURI
<agent>
allows for attributes from any other namespace<agent>
is a required and repeatable sub-element of<agents>
(Create a separate section for elements established as entities #68), a required, not repeatable sub-element in<maintenanceEvent>
(Align <control> across EAD and EAC-CPF #32) and an optional and repeatable sub-element in<findAidDesc>
(Add <findAidDesc> as replacement of <filedesc> #27)As a result of the above:
<origination>
from EAD<repository>
from EAD<corpname>
from EAD<famname>
from EAD<name>
from EAD<persname>
from EADThe text was updated successfully, but these errors were encountered: