>>>>> gd2md-html alert: ERRORs: 1; WARNINGs: 1; ALERTS: 1.
- See top comment block for details on ERRORs and WARNINGs.
- In the converted Markdown or HTML, search for inline alerts that start with >>>>> gd2md-html alert: for specific instances that need correction.
Links to alert messages:
alert1>>>>> PLEASE check and correct alert issues and delete this message and the inline alerts.
Table of Contents
[TOC]
- following ISAAR(CPF), not RiC-CM (yet)
Schema: EAC-CPF
Context: Encoding uncertain dates in <date>, <toDate>, <fromDate>
Description:
The attributes @certainty, @notBefore and @notAfter can be used with the <date>, <toDate>, <fromDate> elements to express the level of certainty of a particular date. @notBefore and @notAfter can be used to indicate the earliest and latest possible dates that an uncertain date might fall between. @certainty can be used to encode a term such as approximate, circa, or uncertain to indicate the level of certainty of the date provided. The @calendar and @era attributes are also available to provide additional information about a date.
EAC-CPF will also enable the use of the Extended Date/Time Format (EDTF), which has been included in the latest version of the ISO 8601 standard. This allows for the encoding of dates as '?', '' and '%' ‘uncertain’ (?), ‘approximate’ (), and ‘uncertain and approximate’ (%) within the machine-processable date in the @standardDate attribute for <date>, <fromDate> and <toDate>.
**Examples: **
<dateRange>
<fromDate notBefore="1971" notAfter="1975">around 1973</fromdate>
<toDate standardDate="1992">1992</toDate>
</dateRange>
<date certainty="uncertain" standardDate="1968?">c. 1968</date>
<dateRange>
<fromDate calendar="gregorian" certainty="approximate" era="ce" standardDate="1950">1950</fromDate>
<toDate calendar="gregorian" certainty="approximate" era="ce" standardDate="2000">2000</toDate>
</dateRange>
Schema: EAC-CPF
Context: Encoding unknown or ongoing dates.
Description: In some circumstances it may not be possible to include information about particular dates in an EAC-CPF instance because they are either unknown, or because a date range is ongoing. An example of an ongoing date range is a Corporate Body that continues to operate. Standalone dates may be unknown or a date range may be incomplete, for example when a date of birth is unknown. It may be important to indicate the status of these dates, rather than omitting them from the EAC-CPF instance.
The @status attribute can be used with the <date>, <fromDate> and <toDate> elements, with a controlled list of values, to allow for indicating where dates - or parts of a date range - may be unknown, or where a date range is ongoing.
The available value for <date> and <fromDate> is "unknown", and the available values for <toDate> are "unknown" or "ongoing"
**Examples: **
<dateRange>
<fromDate status="unknown"/>
<toDate toDate certainty="uncertain" standardDate="2010?">c. 2010</toDate>
</dateRange>
<dateSet>
<date standardDate="2014-07">July 2014</date>
<dateRange>
<fromDate standardDate="2016-09">September 2016</fromDate>
<toDate status="ongoing"/>
</dateRange>
</dateSet>
<date status="unknown" />
Schema: EAC-CFP
Context: Encoding a single name, if necessary with multiple name parts.
Description: Use a single <nameEntry> element within <identity> to enter a single name for an entity. Add attributes to define the names language, status, designation for display or other properties.
Use the element <part> to distinguish between parts of a name, if necessary.
Use the element <useDates> to indicate the dates the name was used.
Use several elements <nameEntry> within <identity> when an entity used different names over time.
**Examples: **
<nameEntry languageOfElement="de" preferredForm="true" status="authorized">
<part localType="surname">Arendt</part>
<part localType="firstname">Hannah</part>
</nameEntry>
<nameEntry status="authorized">
<part>Technical Subcommittee for Encoded Archival Standards</part>
<useDates>
<dateRange>
<fromDate>2015</fromDate>
<toDate status="ongoing"/>
</dateRange>
</useDates>
</nameEntry>
<nameEntry>
<part>Noel family, Earls of Gainsborough</part>
</nameEntry>
Schema: EAC-CPF
Context: Encoding multiple names for different forms of the same name.
Description: Bundle multiple elements <nameEntry> within an element <nameEntrySet> within <identity> to enter different forms of the same name, e.g. official and alternative forms of a name, translations, transliterations, abbreviations, colloquial names etc.
Add attributes in <nameEntry> to define the names language, status, designation for display or other properties.
Use the element <useDates> within the element <nameEntrySet> to indicate the dates all names were used and use the same element with <nameEntry> to indicate the date one of the names was used.
Examples:
<nameEntrySet>
<nameEntry status="authorized">
<part localType="surname">Custer</part>
<part localType="firstname">Mark</part>
</nameEntry>
**<nameEntry** status="alternative">
<part localType="GitHubName">fordmadox</part>
<useDates>
<dateRange>
<fromDate>2011</fromDate>
<toDate status="ongoing"/>
</dateRange>
</useDates>
</nameEntry>
</nameEntrySet>
Schema: EAC-CPF
Context: Qualify a name entry as authorized or alternative name of an entity according to ISAAR(CPF)1 5.1.2.
Description: Use the attribute @status for the element <nameEntry> and select one of the given values "authorized" or "alternative" to indicate if a name is authorized or alternative.
Examples:
<nameEntrySet>
<nameEntry status="authorized">
<part localType="surname">Custer</part>
<part localType="firstname">Mark</part>
</nameEntry>
**<nameEntry status="alternative">**
<part localType="GitHubName">fordmadox</part>
</nameEntry>
</nameEntrySet>
Reflect parallel usage according to cataloging rules in North America {#reflect-parallel-usage-according-to-cataloging-rules-in-north-america}
Schema: EAC-CPF
Context: Qualify a set of name entries as parallel names according to cataloguing rules in North America.
Description: Use the attribute @localType with the value “parallel” within <nameEntrySet> to reflect the usage of parallel names in North America.
Use the attribute @localType in <nameEntry> to specify the type of parallel name used, e.g. former, translation, abbreviation etc.
Examples:
<nameEntrySet localType="parallel">
<nameEntry languageOfElement="de" preferredForm="true" status="authorized" localType="native">
<part localType="surname">Arendt</part>
<part localType="firstname">Hannah</part>
</nameEntry>
<nameEntry languageOfElement="ja" scriptOfElement="Jpan" preferredForm="false" status="authorized" **localType="translation"**>
<part localType="surname">アーレント</part>
<part localType="firstname">ハナ</part>
</nameEntry>
<nameEntry languageOfElement="en" preferredForm="false" status="authorized">
<part localType="surname">Arendt</part>
<part localType="firstname">Hannah</part>
</nameEntry>
</nameEntrySet>
Qualify a name as preferred name for display purposes {#qualify-a-name-as-preferred-name-for-display-purposes}
Schema: EAC-CPF
Context: Qualify a name entry as preferred name for display purposes.
Description: An entity with multiple names needs one name as preferred name for display purposes. If there are multiple equal names over time, i.e. multiple <nameEntry> elements as siblings and child elements of <identity>, multiple preferred names are possible. If there are multiple forms of a name, i.e. multiple <nameEntry> elements within <nameEntrySet>, only one of the names should be declared as the preferred name for display purposes.
Examples:
<nameEntrySet localType="parallel">
<nameEntry languageOfElement="de" **preferredForm="true"** status="authorized" localType="native">
<part localType="surname">Arendt</part>
<part localType="firstname">Hannah</part>
</nameEntry>
<nameEntry languageOfElement="ja" scriptOfElement="Jpan" preferredForm="false" status="authorized" localType="translation">
<part localType="surname">アーレント</part>
<part localType="firstname">ハナ</part>
</nameEntry>
<nameEntry languageOfElement="en" preferredForm="false" status="authorized">
<part localType="surname">Arendt</part>
<part localType="firstname">Hannah</part>
</nameEntry>
</nameEntrySet>
Encode the rules applied for the construction of the name {#encode-the-rules-applied-for-the-construction-of-the-name}
Schema: EAC-CPF
Context: Record the national or international conventions or rules for an authorized name applied by the agency that created the entities description, cf. ISAAR(CPF)2 5.1.2 and 5.4.3.
Description: Use the element <conventionDeclaration> within <control> to declare the rule(s)/convention(s) for an authorized name applied by the agency that created the entity's description. Use @id attribute in <conventionDeclaration> to provide an option for direct link between described rule and the name.
Use the attribute @conventionDeclarationReference within the element <nameEntry> to link directly from the name to the rule.
Examples:
<conventionDeclaration id="cd1">
<reference href="https://www.legifrance.gouv.fr/loda/id/JORFTEXT000033553530/">Décret n° 2016-1689 du 8 décembre 2016 fixant le nom, la composition et le chef-lieu des circonscriptions administratives régionales - Légifrance</reference>
</conventionDeclaration>
**<conventionDeclaration id="cd2">**
<reference href="https://deliberation.maregionsud.fr/docs/ASSEMBLEEPLENIERE/2017/12/15/DELIBERATION/D0V0Q.pdf">DELIBERATION N° 17-1166, 15 DECEMBRE 2017</reference>
</conventionDeclaration>
** <conventionDeclaration id="cd3">**
<reference href="cnig.gouv.fr/wp-content/uploads/2015/03/CNT-site-collectivit%C3%A9s-fran%C3%A7aises.pdf">Commission nationale de toponymie: Collectivités territoriales françaises </reference>
</conventionDeclaration>
<nameEntrySet languageOfElement="fre">
<nameEntry **conventionDeclarationReference="cd1"** preferredForm="true">
<part>Provence-Alpes-Côte d'Azur</part>
</nameEntry>
<nameEntry **conventionDeclarationReference="cd2"**>
<part>Région Sud Provence-Alpes-Côte d'Azur</part>
</nameEntry>
<nameEntry **conventionDeclarationReference="cd3"**>
<part>Provence-Alpes-Côte-d'Azur</part>
</nameEntry>
</nameEntrySet>
Schema: EAC-CPF
Context: The encoding of relationships describes the nature of a relationship between (at least) two entities. The relationship direction always points from the person, family or corporate body described in the EAC-CPF instance to the target entity.
Description: Statements about relationships are constituted by the following basic data components:
- Name of the related entity
- Type of the related entity
- Type of the relationship
- Role of the related entity in a relationship
- Time or time frame of a relationship
- Place of a relationship
- Source of the relationship statement
All components have in common that values can be expressed as literals. It is, however, also desirable to encode the URI representing the literal (value) as well as both the authority / vocabulary source and its URI:
- Name of the authority / vocabulary source (literal)
- URI of the authority / vocabulary source (resource/URI)
- URI of the value (resource/URI)
Examples: see below
CPF entity targets resource
Schema: EAC-CPF
Context: Describe the relationship between the entity described and a resource, like archival records, fonds, papers, publications etc.
Description: Use the wrapper element <relation> to include all information about the related resource and the character of the relation. Use the required child element <targetEntity> to provide
a title or name of the related resource. Use the optional child element <relationType> to specify the type of relation. Use the optional child element <targetRole> to specify the role of the related entity. Use <date>, <dateRange>, or <dateSet> for specifying the time period of the relationship and <place> for relevant location information. <descriptiveNote> may be included for more detailed specifications or explanations of the relationship.
If needed, use <objectXMLWrap> to embed XML documenting the related entity from any (or no) namespace.
Examples:
<relation>
<targetEntity targetType="resource">
<part>Mémorial du colonel Gustafsson. - 1829</part>
</targetEntity>
<date>1829</date>
<relationType valueURI="https://www.ica.org/standards/RiC/ontology#isCreatorOf" vocabularySource="RiC-O" vocabularySourceURI="https://www.ica.org/standards/RiC/ontology">is creator of</relationType>
<targetRole>Publication</targetRole>
</relation>
CPF entity targets person, family or corporate body
Schema: EAC-CPF
Context: Describe the relationship between the entity described and a person, family or corporate body.
Description: Use the wrapper element <relation> to include all information about the related entity and the character of the relation. Use the required child element <targetEntity> to provide a
a name of the related entity. Use the optional child element <relationType> to specify the type of relation. Use the optional child element <targetRole> to specify the role of the related entity. Use <date>, <dateRange>, or <dateSet> for specifying the time period of the relationship and <place> for relevant location information. <descriptiveNote> may be included for more detailed specifications or explanations of the relationship.
If needed, use <objectXMLWrap> to embed XML documenting the related entity from any (or no) namespace.
Examples:
<relation>
<targetEntity targetType="person" valueURI="https://d-nb.info/gnd/120636123" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">
<part>Sophie</part>
<part>Baden, Großherzogin</part>
</targetEntity>
<dateRange>
<fromDate>1801</fromDate>
<toDate>1865</toDate>
</dateRange>
<relationType valueURI="https://www.ica.org/standards/RiC/ontology#hasFamilyAssociationWith" vocabularySource="RiC-O" vocabularySourceURI="https://www.ica.org/standards/RiC/ontology">has family association with</relationType>
<targetRole>daughter</targetRole>
</relation>
CPF entity targets function
Schema: EAC-CPF
Context: Describe the relationship between the entity described and a function.
Description: Use the wrapper element <relation> to include all information about the related function and the character of the relation. Use the required child element <targetEntity> to provide a
a name or title of the related function. Use the optional child element <relationType> to specify the type of relation. Use the optional child element <targetRole> to specify the role of the related entity. Use <date>, <dateRange>, or <dateSet> for specifying the time period of the relationship and <place> for relevant location information. <descriptiveNote> may be included for more detailed specifications or explanations of the relationship.
If needed, use <objectXMLWrap> to embed XML documenting the related entity from any (or no) namespace.
Examples:
Schema: EAC-CPF
**Context: **Creating a reference from one element to another element in a single EAC-CPF instance.
Description: It is possible to create internal references from one element to another element within a single EAC-CPF instance. For example, you may wish to reference a detailed <place> element from <placename> elsewhere in the EAC-CPF instance. The @id and @target attributes are used to create these internal references.
The @id attribute is available on all elements to assign an identifier to an element that is unique within the instance. The @target attribute is available on all elements, except <eac>, and can be used to refer to the @id of another element. To create the reference, use the @target attribute on the element you wish to create a reference from, and enter the value of the @id attribute on the element you wish to refer to, preceded by #. It is possible to refer to more than one element from a single element.
Examples:
<occupation>
<term>Assistant examiner - level III</term>
<placeName** target="#place1"**>Bern</placeName>
</occupation>
<place** id="place1"**>
<placeName>Bern</placeName>
<placeRole>Place of work</placeRole>
<address>
<addressLine addressLineType="street">Stauffacherstrasse 65/59g</addressLine>
<addressLine addressLineType="postalCode">3003</addressLine>
<addressLine addressLineType="country">Switzerland</addressLine>
</address>
</place>
Referencing external vocabularies, ontologies, etc. {#referencing-external-vocabularies-ontologies-etc}
Schema: EAC-CPF
Context: Creating references to external vocabularies and ontologies from an EAC-CPF instance.
Description: The @valueURI, @vocabularySource and @vocabularySourceURI attributes are available on a number of elements for referencing external vocabularies or ontologies that have been used to populate the element.
@vocabularySource is used to identify a vocabulary that is the source of the element's value. @vocabularySourceURI is used for documenting a URI identifying the vocabulary source for the element's value. @valueURI is used for documenting a URI identifying the resource to be used as the element's value.
The attributes can be used individually, or combined to provide details about the source of the contents of an element, when an external vocabulary is being used.
Examples:
<place>
<placeName valueURI="https://d-nb.info/gnd/4005728-8" vocabularySource="GND" vocabularySourceURI="https://d-nb.info/gnd/">Berlin</placeName>
<placeRole valueURI="https://d-nb.info/standards/elementset/gnd#placeOfBusiness" vocabularySource="GNDO" vocabularySourceURI="https://d-nb.info/standards/elementset/gnd#">Sitz</placeRole>
</place>
Schema: EAC-CPF
Context: Creating references to external sources from an EAC-CPF instance.
Description: To reference external sources for the contents of the EAC-CPF instance, encode the details of the external source in the <control> sections, using the <reference> element within <source>. <reference> is a required child element of <conventionDeclaration>, <localTypeDeclaration>, and <rightsDeclaration> for identifying any rules and conventions applied in the compilation of the description. It is also a required child element of <source>, used to identify any sources used in compiling the description. <source> may include multiple child <reference> elements.
<reference> is an optional child element of <abstract>, <chronItem>, <chronItemSet>, <event>, <eventDescription>, <item>, and <p> where it is used to reference any external resources that provide additional context to the contents of that element.
<reference> can include an @href attribute to point to a specific address for a remote resource.
Examples:
<source>
<reference href="https://catalog.archives.gov/search?q=:&f.oldScope=descriptions
&f.level=series&f.locationIds=53023101">Barack Obama Presidential Library</reference>
</source>
<relation>
<targetEntity targetType="corporateBody">
<part>Democratic Party</part>
</targetEntity>
<descriptiveNote>
<p>
<reference href="[https://en.wikipedia.org/wiki/](https://en.wikipedia.org/wiki/Barack_Obama)Barack_Obama">See more</reference>
</p>
</descriptiveNote>
</relation>
Schema: EAC-CPF
Context: Encoding two or more events and/or places within a timeline.
Description: Bundle multiple events <event> and/or places <place> within an element <chronItemSet> within <chronItem> to enter separate events occurring during a particular time period, e.g. multiple places visited in a particular timeframe understood better in a group than as separate occurrences. The example below contains itinerary data for a scientific expedition grouping multiple locations under distinct travel periods. Can be used to encode multiple event-based lists within a larger timeline.
Possible combinations include multiple events, a single event associated with multiple locations, multiple events associated with a single location, or multiple events associated with multiple locations. <chronItemSet> may be repeated within <chronItem> when necessary to associate multiple instances of such combinations with the date or dates recorded within <chronItem>.
A number of attributes are available to qualify data such as language, source references, maintenance event references (to indicate the occurrence and agent responsible for the data), language encoding, and locally defined conventions.
<chronItem> and <chronItemSet> are subelements of <chronList>, <bioghist>, while <description>. <event>, <place> and date elements are subelements of <chronItem> and <chronItemSet>. Refer to <place> for attributes.
Field work and expeditions in the early 20th century often involved harmful acts inflicted upon animals and communities for scientific research. While these practices are not conducted on large mammals today, historical events below are presented as they occurred or appear in evidentiary documentation.
Examples:
<chronList>
<chronItem>
<date standardDate="1909-08-31">August 31, 1909</date>
<event>The party departs Naples, Italy via SS Adolph Woermann, where they are introduced to Sir Percy Girouard, the new British East Africa governor</event>
<place valueURI="[http://vocab.getty.edu/tgn/7004474](http://vocab.getty.edu/tgn/7004474)">Naples</placeEntry>
</chronItem>
<chronItem>
<date standardDate="1909-09">September 1909</date>
**<chronItemSet>**
<event>Arrive in Mombasa, Sir Percy Girouard invites expedition party to travel by private rail to Nairobi</event>
<place valueURI="[http://vocab.getty.edu/tgn/7001115](http://vocab.getty.edu/tgn/7001115)">Mombasa</place>
<event>In Nairobi the party reconnects with old acquaintances and purchases supplies for the journey. /event>
<place valueURI ="[http://vocab.getty.edu/tgn/7001116](http://vocab.getty.edu/tgn/7001116)">Nairobi</place>
</chronItemSet>
</chronItem>
<chronItem>
<date standardDate="1909-10">October 1909</date>
**<chronItemSet** maintenanceEventReference="maintenancevent1" sourceReference="source1">
<event>Spent two weeks hunting rhino and lion, in the Lower Tana River Valley, Delia Akeley procures a small monkey and names her J.T. Jr.</event>
<place valueURI ="http://vocab.getty.edu/tgn/7593796">Tana River</place>
<event>Hunting elephants in Mt. Kenya</event>
<place valueURI ="[http://vocab.getty.edu/tgn/1105240](http://vocab.getty.edu/tgn/1105240)">Kirinyaga</place>
</chronItemSet>
</chronItem>
...
</chronList>
Schema: EAC-CPF
Context: Encoding the name of a place in relation to other aspects of the entity description
Description: When describing a CPF entity, the description of this entity’s functions, activities, roles, occupations, mandates, etc. can play a vital role. In addition to simply naming such aspects, it furthermore can be useful to add a place dimension to them, e.g. when a person described has pursued their profession in various contexts and at several locations over time. Using the attributes @valueURI, @vocabularySource, and/or @vocabularySourceURI allows linking names of geographic locations in the element <placeName> to external vocabularies and ontologies that might hold additional information such as name variations or geographic coordinates of the place. Similarly, one could use the attribute @target to point to the @id attribute of a <place> element within the same EAC-CPF instance where more details about the named location have been provided.
Examples:
<cpfDescription>
<identity>
<entityType value="person"/>
<nameEntry status="authorized" languageOfElement="eng">
<part localType="firstname">Toni</part>
<part localType="lastname">Morrison</part>
</nameEntry>
<nameEntry status="authorized" languageOfElement="eng">
<part localType="birthname">Chloe Ardelia Wofford</part>
</nameEntry>
</identity>
<description>
<occupations>
<!-- [...] -->
<occupation valueURI="https://www.wikidata.org/wiki/Q1622272" \
vocabularySource="Wikidata" vocabularySourceURI="https://www.wikidata.org">
<term>University teacher</term>
<placeName>Texas Southern University, Houston</placeName>
<placeName>Howard University, Washington, D.C.</placeName>
<placeName>State University of New York at Albany</placeName>
<placeName>New Brunswick campus, Rutger University, New Jersey</placeName>
<placeName>Bard College, Annandale-on-Hudson</placeName>
<placeName>Cornell University, Ithaca</placeName>
<placeName>Princeton University, Princeton</placeName>
</occupation>
<!-- [...] -->
</occupations>
</description>
</cpfDescription>
Schema: EAC-CPF
Context: Encoding the name of a place of relevance to the entity being described along with further details about the place
Description: Places tell a CPF entity’s story, might it be their place of birth or death, a place where they lived or worked, a place where an organization was established and made an impact. Places also provide anchor points linking one entity to another via the locations where their paths crossed. EAC-CPF enables a more detailed description of such places of relevance in the <places><place> element within its <description> section as well as in the context of a chronological list, e.g. for building a biography, and in the context of describing relationships between the entity being described and other entities. Next to naming a place using the element <placeName>, describing a place also can include specification of the place’s role (<placeRole>), address or contact details for a place (<address><addressLine> and <contact><contactLine> respectively) and geographic coordinates for a place (<geographicCoordinates). At least one of these aspects has to be covered when describing a place. In addition, an optional date dimension can be added to places of relevance and more descriptive information can be added when describing places.
When describing several places of relevance for the described entity, it is recommended to repeat the complete <place> element and to make use of sub-elements such as <placeRole>, <address>, <contact> or <geographicCoordinates> in order to distinguish between the different places. For encoding variations of the name of a place, on the other hand, it is recommended to repeat only the <placeName> element within the same <place> element.
Examples:
<cpfDescription>
<identity>
<entityType value="corporateBody"/>
<nameEntry status="authorized" languageOfElement="eng">
<part>International Council on Archives</part>
</nameEntry>
<nameEntry status="authorized" languageOfElement="fre">
<part>Conseil International des Archives</part>
</nameEntry>
</identity>
<description>
<places>
<place>
<placeName vocabularySource="GeoNames" \
vocabularySourceURI="https://www.geonames.org"
valueURI="https://www.geonames.org/2988507/paris.html" countryCode="FR"> \
Paris</placeName>
<geographicCoordinates coordinateSystem="WGS84"> \
48.8606298,2.3580453</geographicCoordinates>
<address>
<addressLine addressLineType="country">France</addressLine>
<addressLine addressLineType="street" languageOfElement="fre">60 rue des
Francs-Bourgeois</addressLine>
<addressLine addressLineType="postalCode">75003</addressLine>
<addressLine addressLineType="district" languageOfElement="fre">3e
arrondissement</addressLine>
<addressLine addressLineType="district" languageOfElement="fre"> \
Haut-Marais</addressLine>
<addressLine addressLineType="region" languageOfElement="fre"> \
Île-de-France</addressLine>
</address>
<contact>
<contactLine contactLineType="phoneNumber">+33 (0)1 81 70 55 62 \
</contactLine>
<contactLine contactLineType="fax">+33 (0)1 81 70 55 61</contactLine>
<contactLine contactLineType="email" \
href="mailto:ica@ica.org">ica@ica.org</contactLine>
<contactLine contactLineType="homepage" \
href="https://www.ica.org/en">https://www.ica.org/en</contactLine>
</contact>
<placeRole vocabularySource="Wikidata" vocabularySourceURI="https://www.wikidata.org"
valueURI="https://www.wikidata.org/wiki/Property:P159"> \
Headquarters location</placeRole>
<dateSet>
<dateRange>
<fromDate standardDate="1962-03-01">1 March 1962</fromDate>
<toDate standardDate="1978-07-15">15 July 1978</toDate>
</dateRange>
<dateRange>
<fromDate standardDate="1989-07-01">1 July 1989</fromDate>
<toDate status="ongoing"/>
</dateRange>
</dateSet>
<descriptiveNote>
<p>The headquarters has been at the National Archives of France in Paris
between 1962 and 1978. Afterwards it was moved just outside of Paris due
to extensive renovation works. Since 1989, the headquarters is again
located at rue des Francs-Bourgeois.</p>
</descriptiveNote>
</place>
</places>
</description>
</cpfDescription>
Defining a local value list to be used in the encoding {#defining-a-local-value-list-to-be-used-in-the-encoding}
Schema: EAC-CPF
Context: Defining local conventions and value lists that are not present in an online vocabulary possible to enrich the descriptions.
Description: When there are no possible on-line resources to link to for enriching the descriptions it is possible to use a locally defined convention or value list. You can use one or more locally defined conventions or value lists. The first step in making use of a local convention or value list is to declare the use of it in the encoding of the record in the <control> section of the description. The element is named <localTypeDeclaration> and with its help you can give a reference to it in combination with a possible short code or acronym that the convention or value list is known by and an descriptive note where the convention or value list can be described so the understanding of the used convention or value list is presented. The element itself is given an identification in the identification attribute in either the form of a short code or an identification code making it possible to reference the specific convention or value list used in the element throughout the whole description. The identification attribute helps to make sure that the used local type declaration is present in the description through validation functions found in the schema. It is worth noting that the identification attribute is of the type xml:id for making the validation possible and thus the rules for how identifications are created are enforced. The rules say that an Identification can not start with a number it needs to start with letters and may not contain spaces.
Examples:
<localTypeDeclaration id=”GNDO”>
<reference href="https://dnb.info/standards/elementset/gnd_20191015">
GNDO
</reference>
<descriptiveNote>
<p>Gemeinsame Normdatei Ontologie</p>
<p languageOfElement="eng">Integrated Authority File Ontology</p>
<p>Version 2019-10-15</p>
</descriptiveNote>
</localTypeDeclaration>
<localTypeDeclaration id=”ltd1”>
<reference href="[http://nad.ra.se/static/termlistor/Kategorikoder.htm](http://nad.ra.se/static/termlistor/Kategorikoder.htm)">
Category codes
</reference>
<shortCode>Category codes</shortCode>
<descriptiveNote>
<p>Codes for categorizing different types of authority records
through organizational form, operation, function, archival organization etcetera.
</p>
<p>The category codes used in Swedish NAD</p>
<p>To be used in element function</p>
</descriptiveNote>
</localTypeDeclaration>
Using a local value list to be used in the encoding {#using-a-local-value-list-to-be-used-in-the-encoding}
Schema: EAC-CPF
Context: Referencing a locally defined convention or value lists in the encoding.
Description: When the local type declaration has been made it is possible in all elements where the local type attribute is available to reference the locally defined convention or value list. The step two of referencing is based upon the use of two attributes @localType and @localTypeDeclarationReference where the first gives the value or convention used and the second gives the reference to the local type declaration that has been used. The use of the @localTypeDeclarationReference assures that the local type declaration has been used by containing the identification of the declaration and it being checked through rules present in the schema by using xml:id and the identification reference mechanism.
Examples:
<nameEntry status="authorized">
<part localType="https://d-nb.info/standards/elementset/gnd#personalName"
localTypeDeclarationReference="GNDO">Arendt, Hannah</part>
<part localType="https://dnb.info/standards/elementset/gnd#dateOfBirthAndDeath"
localTypeDeclarationReference="GNDO">1906-1975</part>
</nameEntry>
<function localType="1" localTypeDeclarationReference="ltd1">
<term>stateAuthority</term>
<descriptiveNote>
<p>En textuell beskrivning av organisationens verksamhetssektor</p>
</descriptiveNote>
</function>
Schema: EAC-CPF
Context: Using simple lists in the context of narrative description to structure information
Description: Elements such as <biogHist>, <structureOrGenealogy>, and <generalContext> can hold more narrative description relating to the history and general context of the EAC-CPF entity being described, respectively relating to the administrative structure of a corporate body or the genealogy of a family. Next to simple paragraphs (<p>) and - in the context of <biogHist> - the more specific chronological lists (<chronList>), which allow for capturing important dates and events in the life of an EAC-CPF entity, this also includes the option of creating lists (<list>). These can be useful when encoding enumerations, e.g. a list of different stages in the career of a person or a list of different departments and teams within an organization. Each stage is then represented by an <item> within the <list>. The optional element <head> can be used to include a title for the list, while the attribute @listType can be used to define whether the list would be “ordered”, i.e. numbered, or “unordered”, i.e. using symbols like bullets (●), squares (◼), or hyphens (-) for each list entry.
Examples:
<cpfDescription>
<identity>
<entityType value="person"/>
<nameEntry>
<part localType="firstname">Joan Ruth</part>
<part localType="birthname">Bader</part>
<part localType="lastname">Ginsburg</part>
</nameEntry>
</identity>
<description>
<!-- [...] -->
<biogHist>
<!-- [...] -->
<list listType="unordered">
<head>Legal and academic career</head>
<item>Clerkship for Judge Edmund L. Palmieri, U.S. District Court for the Southern District \
of New York</item>
<item>Research associate and associate director of the Columbia Law School Project on \
International Procedure</item>
<item>Professor at Rutgers Law School</item>
<item>Co-founder of the Women's Rights Law Reporter</item>
<item>Professor at Columbia Law School</item>
<item>Fellow of the Center for Advanced Study in the Behavioral Sciences at Stanford \
University</item>
<item>Co-founder of the Women's Rights Project at the American Civil Liberties \
Union</item>
<item>Judge on the District of Columbia Circuit of the U.S. Court of Appeals</item>
<item>Judge on the U.S. Supreme Court</item>
</list>
</biogHist>
</description>
</cpfDescription>
<cpfDescription>
<identity>
<entityType value="corporateBody"/>
<nameEntry>
<part>United Nations</part>
</nameEntry>
</identity>
<description>
<!-- [...] -->
<structureOrGenealogy>
<!-- [...] -->
<list listType="unordered">
<head>Principal organs</head>
<item>The General Assembly</item>
<item>The Security Council</item>
<item>The Secretariat with th Secretary-General</item>
<item>The Economic and Social Council</item>
<item>The International Council of Justice</item>
<item>The Trusteeship Council</item>
</list>
</structureOrGenealogy>
</description>
</cpfDescription>
Schema: EAC-CPF
Context: Using multi-level lists in the context of narrative description to convey more complex structures
Description: Next to allowing for the use of repeated <item> elements to create simple lists, the element <list> can also be used recursively, i.e. <list> can also include another <list>. Such multi-level lists can be of help when encoding more complex structures, e.g. a table of content of a person’s main publication in <biogHist> or in <generalContext>, or a family tree or an organizational chart in the context of <structureOrGenealogy>. Depending on the use case, there might be <item> and <list> elements next to each other within <list>, e.g. when representing the person being described as an <item> and including their children as <item>-s within a nested <list> on the same level. Especially with multi-level lists, the use of the optional element <head> would be recommended to indicate the relation of each nested <list> to their parent <list> or to the main <list> overall.
Examples:
<cpfDescription>
<identity>
<entityType value="person"/>
<nameEntry>
<part localType="firstname">Johan Sebastian</part>
<part localType="lastname">Bach</part>
</nameEntry>
</identity>
<description>
<!-- [...] -->
<structureOrGenealogy>
<!-- [...] -->
<list listType="unordered">
<head>Children of Johann Sebastian Bach and Maria Barbara Bach</head>
<item>Catharina Dorothea Bach</item>
<item>Wilhelm Friedemann Bach</item>
<list>
<head>Children of Wilhelm Friedemann Bach</head>
<item>Friederica Sophia Bach</item>
<item>Two sons who did not live past infancy</item>
</list>
<item>Carl Philipp Emanuel Bach</item>
<list>
<head>Children of Carl Philipp Emanual Bach</head>
<item>Johann Adam Bach</item>
<item>Anna Carolina Philippina Bach</item>
<item>Johann Sebastian Bach ("the Younger")</item>
<item>Other children who did not live to adulthood</item>
</list>
<item>Johann Gottfried Bernhard Bach</item>
<item>Three more children who did not live to their first birthday</item>
</list>
<list listType="unordered">
<head>Children of Johann Sebastian Bach and Anna Magdalena Wilcken</head>
<item>Gottfried Heinrich Bach</item>
<item>Johann Christoph Friedrich Bach</item>
<list>
<head>Children of Johann Christoph Friedrich Bach</head>
<item>Anna Philippiana Friederica Bach</item>
<item>Wilhelm Friedrich Ernst Bach</item>
<list>
<head>Children of Wilhelm Friedrich Ernst Bach</head>
<item>Carolina Auguste Wilhelmine Bach</item>
<item>Juliane Friederica Bach</item>
</list>
<item>Christine Luise Bach</item>
</list>
<item>Johann Christian Bach</item>
<item>Elisabeth Juliane Friederica Bach</item>
<list>
<head>Children of Elisabeth Juliane Friederica Bach</head>
<item>Johann Sebastian Altnickol</item>
</list>
<item>Johanna Carolina Bach</item>
<item>Regina Susanna Bach</item>
<item>Six more children who did not live to adulthood</item>
</list>
</structureOrGenealogy>
</description>
</cpfDescription>
<cpfDescription>
<identity>
<entityType value="person"/>
<nameEntry>
<part localType="firstname">Charles Robert</part>
<part localType="lastname">Darwin</part>
</nameEntry>
</identity>
<description>
<!-- [...] -->
<generalContext>
<!-- [...] -->
<list listType="unordered">
<head>The Origins of Species by Means of Natural Selection or The Preservation of \
Favoured Races in the Struggle of Life, 6th edition, with additions and corrections, 1873 \
</head>
<item>Additions and corrections, to the sixth edition</item>
<item>Historical sketch</item>
<item>Introduction</item>
<item>Chapter I - Variation under Domestication</item>
<list>
<item>Causes of Variability</item>
<item>Effects of Habit and the use or disuse of Parts</item>
<item>Correlated Variation</item>
<item>Inheritance</item>
<item>Character of Domestic Varieties</item>
<item>Difficulty of distinguishing between Varieties and Species</item>
<item>Origin of Domestic Varieties from one or more Specie</item>
<item>Domestic Pigeons, their Differences and Origin</item>
<item>Principles of Selection, anciently followed, their Effects</item>
<item>Methodical and Unconscious Selection</item>
<item>Unknown Origin of our Domestic Productions</item>
<item>Circumstances favourable to Man's power of Selection</item>
</list>
<item>Chapter II - Variation under Nature</item>
<list>
<!-- [...] -->
</list>
<item>Chapter III - Struggle for Existence</item>
<list>
<!-- [...] -->
</list>
<!-- [...] -->
<item>Chapter XV - Recapitulation and Conclusion</item>
<list>
<!-- [...] -->
</list>
<item>Glossary of Scientific Terms</item>
<item>Index</item>
</list>
</generalContext>
</description>
</cpfDescription>
Schema: EAC-CPF
Context: Encoding the type of agent being described in an EAC-CPF instance
Description: Following the chapter 5.1.1 Type of entity in the International Standard Archival Authority Record for Corporate Bodies, Persons, and Families (ISAAR-CPF), EAC-CPF includes the element <entityType> within the <identity> section to define whether the entity being described is an organization of some kind, a person, or a family. Meant to provide a standardized anchor supporting interoperability across variations of local applications of EAC-CPF, <entityType> itself cannot have text, but requires the attribute @value to be used with either “corporateBody”, or “person”, or “family”. These three types are designed to be mutually exclusive, so that <entityType> also cannot be repeated.
Examples:
<identity>
<entityType value="corporateBody"/>
<nameEntry status="authorized" languageOfElement="de">
<part>ICARus - Internationales Zentrum für Archivforschung</part>
</nameEntry>
<nameEntry status="authorized" languageOfElement="en-gb">
<part>ICARus - International Centre for Archival Research</part>
</nameEntry>
</identity>
<control>
[...]
<localTypeDeclaration id="GNDO">
<reference href="https://d-nb.info/standards/elementset/gnd">Gemeinsame Normdatei \
Ontology</reference>
<shortCode>GNDO</shortCode>
</localTypeDeclaration>
</control>
<cpfDescription>
<identity>
<entityType value="person"/>
<nameEntry status="authorized">
<part localType="https://d-nb.info/standards/elementset/gnd#personalName" \
localTypeDeclarationReference="GNDO">Gustaf IV Adolf</part>
<part localType="https://d-nb.info/standards/elementset/gnd#nameAddition" \
localTypeDeclarationReference="GNDO">Kung av Sverige</part>
</nameEntry>
</identity>
</cpfDescription>
<control>
[...]
<localTypeDeclaration id="MARC21_MainEntry_PersonalName">
<reference href="https://www.loc.gov/marc/bibliographic/bd100.html">MARC 21 Bibliographic \
Full 100 - Main Entry-Personal Name (NR)</reference>
<shortCode>MARC 21</shortCode>
</localTypeDeclaration>
</control>
<cpfDescription>
<identity>
<entityType value="family"/>
<nameEntry status="authorized">
<part localType="100$a">Mozart</part>
<part localType="100$c">Familie : 17.-19. Jh.</part>
</nameEntry>
</identity>
</cpfDescription>
Schema: EAC-CPF
Context: Encoding alternative types of agent being described in an EAC-CPF instance
Description: Next to <entityType>, EAC-CPF also includes the element <otherEntityType>. With <otherEntityType> it is possible e.g. to provide translations or specifications of the default values used in <entityType> or to include related agent types from other standards such as Records in Contexts (RiC).
Similar to the plural and singular elements used in the <description> section (f.i. <functions> and <function> or <occupations> and <occupation>), <otherEntityType> is used within a wrapper element <otherEntityTypes> that also allows for a <descriptiveNote> to be included to add details with regard to the alternative entity types given.
<otherEntityType> itself allows for the three vocabulary attributes (@valueURI, @vocabularySource, @vocabularySourceURI) and hence enables the connection to external vocabularies for the alternative agent type provided in <otherEntityType><term>. Same as all other singular elements, <otherEntityType> also comes with the optional sub-elements for date and place encoding, so that the alternative agent type can be bound to a specific timespan or location with regard to its use or applicability. This might e.g. be useful when a corporate body has changed its legal form over time and one would want to already emphasize this fact in the <identity> section, next to a potential use of <legalStatus> within the <description> section.
Examples:
<control>
[...]
<localTypeDeclaration id="termType" target="termTypeLocal">
<reference>Types of terms</reference>
</localTypeDeclaration>
<localControl id="termTypeLocal">
<term>translation</term>
<term>specification</term>
<term>relatedStandard</term>
</localControl>
</control>
<cpfDescription>
<identity>
<entityType value="corporateBody"/>
<nameEntry status="authorized" languageOfElement="de">
<part>ICARus - Internationales Zentrum für Archivforschung</part>
</nameEntry>
<nameEntry status="authorized" languageOfElement="en-gb">
<part>ICARus - International Centre for Archival Research</part>
</nameEntry>
<otherEntityTypes>
<otherEntityType localType="translation" localTypeDeclarationReference="termType" \
valueURI="https://d-nb.info/gnd/4128521-9" vocabularySource="GND">
<term language Of Element="de">Körperschaft</term>
</otherEntityType>
<otherEntityType localType="specification" localTypeDeclarationReference="termType" \
valueURI="https://d-nb.info/gnd/4043774-7" vocabularySource="GND">
<term languageOfElement="de">Organisation</term>
</otherEntityType>
<otherEntityType localType="specification" localTypeDeclarationReference="termType" \
valueURI="https://data.bnf.fr/ark:/12148/cb11951020r" vocabularySource="RAMEAU">
<term languageOfElement="fr">Organisation</term>
</otherEntityType>
<otherEntityType localType="specification" localTypeDeclarationReference="termType" \
valueURI="https://d-nb.info/gnd/4293729-2" vocabularySource="GND">
<term languageOfElement="de">Nonprofit-Organisation</term>
</otherEntityType>
<otherEntityType localType="specification" localTypeDeclarationReference="termType" \
valueURI="https://data.bnf.fr/ark:/12148/cb119498393" vocabularySource="RAMEAU">
<term languageOfElement="fr">Associations sans but lucratif</term>
</otherEntityType>
<otherEntityType localType="specification" localTypeDeclarationReference="termType" \
valueURI="https://d-nb.info/gnd/4062714-7" vocabularySource="GND">
<term languageOfElement="de">Verein</term>
</otherEntityType>
<otherEntityType localType="specification" localTypeDeclarationReference="termType" \
valueURI="https://data.bnf.fr/ark:/12148/cb13318322c" vocabularySource="RAMEAU">
<term languageOfElement="fr">Associations</term>
</otherEntityType>
</otherEntityTypes>
</identity>
</cpfDescription>
<control>
[...]
<localTypeDeclaration id="GNDO">
<reference href="https://d-nb.info/standards/elementset/gnd">Gemeinsame Normdatei \
Ontology</reference>
<shortCode>GNDO</shortCode>
</localTypeDeclaration>
<localTypeDeclaration id="termType" target="termTypeLocal">
<reference>Types of terms</reference>
</localTypeDeclaration>
<localControl id="termTypeLocal">
<term>translation</term>
<term>specification</term>
<term>relatedStandard</term>
</localControl>
</control>
<cpfDescription>
<identity>
<entityType value="person"/>
<nameEntry status="authorized">
<part localType="https://d-nb.info/standards/elementset/gnd#personalName" \
localTypeDeclarationReference="GNDO">Gustaf IV Adolf</part>
<part localType="https://d-nb.info/standards/elementset/gnd#nameAddition" \
localTypeDeclarationReference="GNDO">Kung av Sverige</part>
</nameEntry>
<otherEntityTypes>
<otherEntityType \
valueURI="https://d-nb.info/standards/elementset/gnd#RoyalOrMemberOfARoyalHouse" \
vocabularySource="GNDO" \
vocabularySourceURI="https://d-nb.info/standards/elementset/gnd#"
localType="specification" localTypeDeclarationReference="termType">
<term languageOfElement="ger">Regierender Fürst oder Mitglied eines regierenden \
Fürstenhauses</term>
</otherEntityType>
</otherEntityTypes>
</identity>
</cpfDescription>
<control>
[...]
<localTypeDeclaration id="MARC21_MainEntry_PersonalName">
<reference href="https://www.loc.gov/marc/bibliographic/bd100.html">MARC 21 Bibliographic \
Full 100 - Main Entry-Personal Name (NR)</reference>
<shortCode>MARC 21</shortCode>
</localTypeDeclaration>
</control>
<cpfDescription>
<identity>
<entityType value="family"/>
<nameEntry status="authorized">
<part localType="100$a">Mozart</part>
<part localType="100$c">Familie : 17.-19. Jh.</part>
</nameEntry>
<otherEntityTypes>
<otherEntityType languageOfElement="eng" \
valueURI="https://www.ica.org/standards/RiC/ontology#Agent" vocabularySource="RiC-O" \
vocabularySourceURI="https://www.ica.org/standards/RiC/ontology">
<term>Agent</term>
</otherEntityType>
<otherEntityType languageOfElement="eng" \
valueURI="https://www.ica.org/standards/RiC/RiC-O_v0-2.html#Group" \
vocabularySource="RiC-O" \
vocabularySourceURI="https://www.ica.org/standards/RiC/ontology">
<term>Group</term>
</otherEntityType>
<otherEntityType languageOfElement="eng" \
valueURI="https://www.ica.org/standards/RiC/RiC-O_v0-2.html#Family" \
vocabularySource="RiC-O" \
vocabularySourceURI="https://www.ica.org/standards/RiC/ontology">
<term>Family</term>
</otherEntityType>
</otherEntityTypes>
</identity>
</cpfDescription>
Schema: EAC-CPF
Context: Identifiers used as unambiguous references in local systems are needed to identify or to refer to records, agencies, entities, resources, and authority files. There is a difference between identifiers for records and entities.
**Description: **Different types of non-informational identifiers are used to identify
-
the present EAS instance within the element <recordId>, cf. Record identifiers
or to refer to
-
other records of the same resource or entity as described in the EAS instance within the element <otherRecordId>, cf. Record identifiers
-
the agency, responsible for creation, maintenance or dissemination of the EAS instance within the element <agencyCode>, c.f. Agency Codes
-
the entity, thus the person, family or corporate body, described the present EAC-CPF instance within the element <identityId>, c.f. Entity Identifiers
-
the materials being described in an EAD instance within the element <unidid>, c.f. ID of the Unit (coming soon)
Examples: see below
Schema: EAC-CPF
Context: Unique identifier for the present EAS instance as globally unique identifier or as local identifier, but also unique identifier(s) for multiple records representing the same entity or resource in different systems.
Record identifiers are associated with a record, not with the corporate body, person or familie, i.e. the entity, c.f. entity identifier.
Description: The present EAS instance needs a unique identifier within <recordId>, a required, not repeatable and non-empty element in <control>. The institution assigning the identifier ensures uniqueness of the <recordId> value within the archival descriptions under its control. Depending on the records environment, it can be a locally unique identifier or a globally unique identifier.
Any alternative or additional record identifiers for the same EAS instance, local or authority file record may be recorded in <otherRecordId>. Any merged, translated and aggregated records and also former or obsolete records are alternative records. Also use <otherRecordId> to enter identifiers of different records in different systems for the same entity.
Use the attributes @valueURI, @vocabularySource and @vocabularySourceURI to link to the source of the other record identifier and to identify the source system, esp. when using an authority record. The attribute @localType can be used to identify the institution or service responsible for providing the associated record identifier, by name or identifier.
The URL for the EAC-CPF instance itself may be captured in <representation>.
Examples:
Schema: EAC-CPF
Context: Code or identifier for the institution or service responsible for the creation, maintenance, and/or dissemination of the EAS instance.
Description: Identify the institution or service responsible for the present EAS instance with a unique code or identifier preferably according to the International Standard Identifier for Libraries
and Related Organizations (ISIL), ISO 15511:2019, within the element <agencyCode>. If this is not the case then local institution codes may be given with the ISO 3166-1 alpha-2 country code as the prefix to aim for international uniqueness.
Use the attribute @status with the value "authorized" or "alternative" to declare whether the agency code is using an authorized value, e.g. a registered ISIL code, or an alternative one.
Use <otherAgencyCode> to record any alternative codes representing the agency.
Examples:
<maintenanceAgency>
**<agencyCode status="authorized" vocabularySource="ISIL" **vocabularySourceURI="http://id.loc.gov/vocabulary/identifiers/isil">US-ctybr</agencyCode>
<agencyName>Beinecke Rare Book and Manuscript Library</agencyName>
**<otherAgencyCode status="authorized"** valueURI="https://id.loc.gov/vocabulary/organizations/ctybr" vocabularySource="MARC Code List for Organizations" vocabularySourceURI="https://www.loc.gov/marc/organizations/">CtY-BR</otherAgencyCode>
<otherAgencyCode status="alternative" valueURI="https://www.wikidata.org/wiki/Q814779" vocabularySource="Wikidata" vocabularySourceURI="https://www.wikidata.org/"> Q814779</otherAgencyCode>
</maintenanceAgency>
Schema: EAC-CPF
Context: Identifier associated with the corporate body, person or familie, i.e. the entity, being described in the EAC-CPF instance.
Description: The repeatable element <identityId> records identifiers such as legal identifiers, typically assigned by an authoritative agency. These identifiers can be (non exhaustive listing): business numbers, CAGE codes, Tax Identification numbers, personal registration numbers, passport numbers, ORCID ID, ISNI etc.
Examples:
<identityId localType="RegistrationCode">222000-3103</identityId>
<identityId localType="VATRegistrationCode”>SE222000310301</identityId>
<identityId localType="EInvoiceID">2220003103</identityId>
Notes (SiJa):
- conventionDeclaration, languageDeclaration, localTypeDeclaration, rightsDeclaration
Schema: EAS
Context: The control area contains information about the creation, maintenance, status and the rules and authorities used in the composition of the EAC-CPF instance.
Description: The element <control> is a mandatory element in the root element <eac>. It has 3 required child elements for the record identifier, the maintenance agency and for the maintenance history. Furthermore, the element <control> needs the required attribute @maintenanceStatus to declare the current drafting status of the EAS instance.
The control area also includes information about sources of evidence, any used conventions and local types.
Examples: see below
Schema: EAS
Context: The institution or service responsible for the EAS instance and the history of the creation and maintenance of this record that ends up in the status of the EAS instance.
Description: There is one institution or service, i.e. agency, responsible for the EAS instance and captured in the element <maintenanceAgency>. For this agency one or more agency codes, preferably one agency code is an authorized ISIL code, can be given, c.f. Agency Codes. Additionally one or more names of the agency can be entered. At least one agency code or one agency name must be there to identify the maintenance agency.
The maintenance history must contain at least one maintenance event to record an activity in
the creation and unlimited more maintenance events to record the ongoing maintenance of an EAS instance, including revisions, updates, and deletions.
So the element <maintenanceHistory> has at least one child element <maintenanceEvent> with information on the agent, in the child element <agent>, that carried out the maintenance event, and the date and time the maintenance event occurred, in the child element <eventDateTime>. The event might be described within <eventDescription>.
The <maintenanceEvent> can be used to enter information about origination and point in time of any assertion made in the EAS instance.
Add the attribute @id in <maintenanceEvent> in order to identify this particular element. Use the attribute @maintenanceEventRefercence in any of the the elements of the identity area, the description area, and the relations allows for linking back to this particular element <maintenanceEvent> in the current EAC-CPF instance.
Examples:
<eac>
<control maintenanceStatus="revised">
<recordId>record identifier</recordId>
<maintenanceAgency>
<agencyName>TS-EAS</agencyName>
</maintenanceAgency>
<maintenanceHistory>
<maintenanceEvent maintenanceEventType="derived">
<agent agentType="machine">XSLT ead2cpf.xsl/Saxon B9</agent>
<eventDateTime standardDateTime="2009-08-30T09:37:17.029-04:00"/>
<eventDescription>Derived from EAD instance.</eventDescription>
</maintenanceEvent>
<maintenanceEvent maintenanceEventType="revised">
<agent agentType="unknown"/>
<eventDateTime standardDateTime="2021-11-27"/>
</maintenanceEvent>
<maintenanceEvent maintenanceEventType="updated">
<agent agentType="human">K. Bredenberg</agent>
<eventDateTime>December 2021</eventDateTime>
</maintenanceEvent>
</maintenanceHistory>
</control> [...]
Schema: EAC-CPF
Context: Source of evidence used for the establishment of the description of the CPF entity in the EAC-CPF instance.
Description: Within the element <source> any source of evidence for any information within an EAC-CPF instance can be given. The element <source> is repeatable within its plural element <sources>.
Use the required child element <reference> to include a textual identification of the reference, like author and title of a publication or article etc. In the case of online sources, use @href with <reference> to provide a URI.
Use the optional child element <citedRange> to point to a specific location within a source, like page numbers.
Use the optional <descriptiveNote> for any additional notes about the source.
Use the optional <objectXMLWrap> to embed XML documenting the source from any namespace.
Add the attribute @id in <source> in order to identify this particular element. Use the attribute @sourceReference in any of the the elements of the identity area, the description area, and the relations allows for linking back to this particular element <source> in the current EAC-CPF instance.
Information given in the elements <source> and <maintenanceEvent>, cf.
>>>>> gd2md-html alert: undefined internal link (link text: "Maintenance agency, history and status"). Did you generate a TOC?
(Back to top)(Next alert)
>>>>>
Maintenance agency, history and status, lay the foundation to the description of an assertion to the EAC-CPF description.
Examples:
<eac>
<control maintenanceStatus="revised">[...]
<sources>
<source id=”SourceWiki”>
<reference href="https://de.wikipedia.org/wiki/Gustav_IV._Adolf_(Schweden)"> Wikipedia</reference>
</source>
<source>
<reference href="https://sok.riksarkivet.se/sbl/Presentation.aspx?id=13318">Svenskt biografiskt lexikon</reference>
<descriptiveNote>
<p>Stand: 03.12.2020</p>
</descriptiveNote>
</source>
</sources> [...]
</control> [...]
</eac>
**Declarations in the control area**
**Schema: **EAC-CPF
**Context: **
**Description: **
**Examples: **
Schema:
Context:
Description:
Examples: