Open kerstarno opened 1 year ago
For conversion, the current encoding
<repositoryType>National archives<repositoryType/>
- OR -
<repositoryType>Regional archives<repositoryType/>
- OR -
<repositoryType>County/local authority archives<repositoryType/>
- OR -
<repositoryType>Municipal archives<repositoryType/>
- OR -
<repositoryType>Specialised government archives<repositoryType/>
- OR -
<repositoryType>Private persons and family archives<repositoryType/>
- OR -
<repositoryType>Church and religious archives<repositoryType/>
- OR -
<repositoryType>Business archives<repositoryType/>
- OR -
<repositoryType>University and research archives<repositoryType/>
- OR -
<repositoryType>Media archives<repositoryType/>
- OR -
<repositoryType>Archives of political parties, of popular/labour movement and other non-governmental organisations, associations, agencies and foundations<repositoryType/>
- OR -
<repositoryType>Specialised non-governmental archives and archives of other cultural (heritage) institutions<repositoryType/>
becomes
<repositoryType value="nationalArchives"/>
- OR -
<repositoryType value="regionalArchives"/>
- OR -
<repositoryType value="localArchives"/>
<otherRepositoryTypes>
<otherRepositoryType>
<term>County/local authority archives</term>
<otherRepositoryType>
</otherRepositoryTypes>
- OR -
<repositoryType value="localArchives"/>
<otherRepositoryTypes>
<otherRepositoryType>
<term>Municipal archives</term>
<otherRepositoryType>
</otherRepositoryTypes>
- OR -
<repositoryType value="specialisedGovernmentArchives"/>
- OR -
<repositoryType value="personalAndFamilyArchives"/>
- OR -
<repositoryType value="religiousInstitutionsArchives">
- OR -
<repositoryType value="businessArchives"/>
- OR -
<repositoryType value="universityArchives"/>
- OR -
<!-- removed <repositoryType>Media archives<repositoryType/> and added <genreForm> to <holdings> below -->
<description>
[...]
<holdings>
<genreForm>
<part>Media archives</part>
</genreForm>
</holdings>
</description>
- OR -
<!-- removed <repositoryType>Archives of political parties, of popular/labour movement and other non-governmental organisations, associations, agencies and foundations<repositoryType/> and added <subject> to <holdings> below -->
<description>
[...]
<holdings>
<subject>
<part>Political parties, popular/labour movement and other non-governmental organisations, associations, agencies and foundations</part>
</subject>
</holdings>
</description>
- OR -
<repositoryType value="specialisedNongovernmentalArchives"/>
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:
<repositoryType>
Change in content model (elements)
List all sub-elements and attributes that should be removed from or added to the element's content model.
Remove
Sub-element(s): predefined content (moved to the new attribute
@value
Add
Sub-element(s): n/a,
<repositoryType>
cannot contain any text anymore Attributes (with default values, if applicable):@value
with the values "businessArchives", "communityArchives", "internationalArchives", "localArchives", "nationalArchives", "nonUniversityEducationArchives", "personalAndFamilyArchives", "regionalArchives", "religiousInstitutionsArchives", "specialisedGovernmentArchives", "specialisedNongovernmentalArchives", "universityArchives" (1),@audience
with the values "external" and "internal" (0),@id
(0),@target
(0), and an option to include attributes from any other namespaceNew element / attribute
Give the name of the new element / attribute. Include the tag name and the full name. Name:
<otherRepositoryTypes>
with sub-element<otherRepositoryType>
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):
<otherRepositoryTypes>
is optional and not repeatable (0..n) within<identity>
;<otherRepositoryType>
is required and repeatable (1..n) within<otherRepositoryTypes>
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.
otherRepositoryTypes
<otherRepositoryTypes>
includes a required and repeatable sub-element<otherRepositoryType>
and an optional and not repeatable sub-element<descriptiveNote>
. Furthermore,<otherRepositoryTypes>
allows for the attributes@audience
with the values "external" and "internal" (0),@id
(0),@languageOfElement
(0),@scriptOfElement
(0),@target
(0),@conventionDeclarationReference
(0),@maintenanceEventReference
(0),@sourceReference
(0), and an option to include attributes from any other namespace.otherRepositoryType
<otherRepositoryType>
includes the following sequence of sub-elements:<term>
(1..n), one of<date>
,<dateRange>
or<dateSet>
(0..1),<placeName>
(0..n),<descriptiveNote>
(0..1). Furthermore,<otherRepositoryType>
allows for the attributes@audience
with the values "external" and "internal" (0),@id
(0),@languageOfElement
(0),@scriptOfElement
(0),@target
(0),@localType
(0),@localTypeDeclarationReference
(0),@conventionDeclarationReference
(0),@maintenanceEventReference
(0),@sourceReference
(0),@valueURI
(0),@vocabularySource
(0),@vocabularySourceURI
(0), and an option to include attributes from any other namespace.<term>
can contain text and allows for the attributes@audience
with the values "external" and "internal" (0),@id
(0),@languageOfElement
(0),@scriptOfElement
(0),@target
(0),@conventionDeclarationReference
(0),@maintenanceEventReference
(0),@sourceReference
(0), and an option to include attributes from any other namespace.<term>
only with<localControl>
, which is now removed (#110), so this is a completely new addition of<term>
following the definition of the element in EAC-CPF 2.0.<placeName>
can contain text and allows for the attributes@audience
with the values "external" and "internal" (0),@id
(0),@languageOfElement
(0),@scriptOfElement
(0),@target
(0),@countryCode
(0) of data type NMTOKEN,@localType
(0),@localTypeDeclarationReference
(0),@conventionDeclarationReference
(0),@maintenanceEventReference
(0),@sourceReference
(0),@valueURI
(0),@vocabularySource
(0),@vocabularySourceURI
(0), and an option to include attributes from any other namespace.Example for usage of the new / changed element (including potential attributes)
Describe how the new / changed element should be used. Write your text after the "Text:" below. Text:
<otherRepositoryType>
and the wrapper plural element<otherRepositoryTypes>
are used to encode alternative repository types such as translations or specifications of respectively additions to the predefined values used in<repositoryType value="...">
.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: