1 / 30

ISAAR (CPF) and a possible mapping to CIDOC CRM

ISAAR (CPF) and a possible mapping to CIDOC CRM. Based on http://socialarchive.iath.virginia.edu/ and “State of the art report on EAC-CPF and recommendations for implementation in Archives Portal Europ e, 2013”. CIDOC-CRM SIG meeting, Den Haag 02.04.2014

elaine-skinner
Download Presentation

ISAAR (CPF) and a possible mapping to CIDOC CRM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ISAAR (CPF) and a possible mapping to CIDOC CRM Based on http://socialarchive.iath.virginia.edu/ and “State of the art report on EAC-CPF and recommendations for implementation in Archives Portal Europe, 2013” CIDOC-CRM SIG meeting, Den Haag 02.04.2014 Christian-Emil Ore, University of Oslo, Norway

  2. Example from socialarchive.iath.virginia.edu 1

  3. Example from socialarchive.iath.virginia.edu 2

  4. Example from socialarchive.iath.virginia.edu 3

  5. One xml-record for each person/corp. body /family <eac-cpf xmlns="urn:isbn:1-931666-33-4" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"xmlns:xlink="http://www.w3.org/1999/xlink"> <control>...</control> <cpfDescription>...</cpfDescription> </eac-cpf>

  6. CONTROL -element <control> <recordId>DLC.ms008095.r074</recordId> …. <otherRecordId localType="VIAFId">VIAFId:44376228 </otherRecordId> <maintenanceStatus>new</maintenanceStatus> <maintenanceAgency>...</maintenanceAgency> <languageDeclaration>...</languageDeclaration> <conventionDeclaration>...</conventionDeclaration> <maintenanceHistory>...</maintenanceHistory> <sources>...</sources> </control>

  7. cpfDescription -element <cpfDescription> <identity>...</identity> <description>...</description> <relations>...</relations> < alternativeSet >…</alternativeSet> </cpfDescription>

  8. cpfDescription -element • <identity> - Identity. Complex structure containing the name or names used by the entity over the course of the entity’s existence. Contains a repeatable <nameEntry> element for different names, and a repeatable <nameEntryParallel> element for more than one <nameEntry> expressed in different languages. Required. • <description> - Description. Contains formal description elements parallel to those in ISAAR (CPF) for the description of the entity. An additional <localDescription> allows for local implementation of additional descriptive information not included in the other <description> elements. Optional.

  9. cpfDescription -element • <relations> - Relations. Contains one or more references to or descriptions of related corporate bodies, persons or families <cpfRelation>, functions <functionRelation>, or resources <resourceRelation>. Optional. • <alternativeSet> - Alternative set. Contains two or more authority records for the same entity derived from two or more authority systems, expressed within a single EAC-CPF instance. The <alternativeSet> consists of two or more <setComponent> elements for the authority records.

  10. cpfDescription -element <cpfDescription> <identity>...</identity> <description>...</description> <relations>...</relations> < alternativeSet >…</alternativeSet> </cpfDescription>

  11. identity -element <identity> - Identity Brief description: A wrapper element for the name or names related to the identity being described within the <cpfDescription>element in the EAC-CPF instance. Can contain following sub elements: <nameEntryParallel> <nameEntry> <entityId> <entityType> <descriptiveNote> Can contain following attributes: @identityType

  12. identity element – example <identity> <entityType>person</entityType> <nameEntry scriptCode="Latn" xml:lang="eng"> <part>Oppenheimer, J. Robert, 1904-1967.</part> <authorizedForm>DLC</authorizedForm> </nameEntry> ... <nameEntry localType="VIAF:MainHeading"> <part>Oppenheimer, J. Robert (Julius Robert), 1904-1967</part> <alternativeForm>VIAF</alternativeForm> </nameEntry> ... <nameEntry localType="VIAF:x400"> <part>Ou-pẽn-hai-mo,1904-1967</part> <alternativeForm>VIAF</alternativeForm> </nameEntry> </identity>

  13. description element – example <description> <existDates>...</existDates> <localDescription localType="subject">...</localDescription> ... <localDescription localType="subject">...</localDescription> <localDescription localType="VIAF:nationality">... </localDescription> <localDescription localType="VIAF:gender">...</localDescription> <languageUsed>...</languageUsed> <occupation>...</occupation> <occupation>...</occupation> <biogHist>...</biogHist> </description>

  14. biogHistelement <biogHist>- Biographical or historical note Brief description: A concise essay and/or chronology that provides biographical or historical information about the CPF entity. Can contain following sub elements: <abstract> <chronList> <p> <citation> Can contain following attributes: @localType

  15. chronItemelement <chronItem> Chronological item Brief description: A container element that keeps a date or a date range paired with an associated event and an optional place within a Chronology List <chronList>. Can contain following sub elements: <date> <dateRange> <event> <placeEntry> Can contain following attributes: @localType @xml:lang

  16. biogHistelement - example <biogHist> <chronList> <chronItem><date>1904, Apr. 22</date> <placeEntry>New York, N.Y.</placeEntry> <event>Born, New York, N.Y.</event></chronItem> … <chronItem><date>1927</date> <placeEntry>Göttingen, Germany</placeEntry> <event>Ph. D., University of Göttingen, Göttingen, Germany</event> </chronItem> .... <chronItem><date>1967, Feb. 18</date> <placeEntry>Princeton, N.J.</placeEntry> <event>Died, Princeton, N.J.</event></chronItem> </chronList> <citation>From the finding aid for J. Robert Oppenheimer Papers 1799-1980 (bulk 1947-1967) ( Manuscript Division Library of Congress) </citation> </biogHist>

  17. relationelement <relations> – Relations Brief description: A wrapper element that groups together one or more relation elements, each of which encodes a specific relationship. Can contain following sub elements: <cpfRelation> <functionRelation> <resourceRelation> Can contain following attributes: /

  18. relation element – example <relations> … <cpfRelation xmlns:xlink="http://www.w3.org/1999/xlink" xlink:arcrole="associatedWith" xlink:role="http://RDVocab.info/uri/schema/FRBRentitiesRDA/Person"xlink:type="simple">...</cpfRelation> <resourceRelation xmlns:xlink="http://www.w3.org/1999/xlink"  xlink:arcrole="referencedIn" xlink:href="http://hdl.loc.gov/loc.mss/eadmss.ms008095"xlink:role="archivalRecords" xlink:type="simple">...</resourceRelation> …. <resourceRelation xmlns:xlink="http://www.w3.org/1999/xlink" xlink:arcrole="referencedIn" xlink:href="http://hdl.loc.gov/loc.mss/eadmss.ms008095"xlink:role="archivalRecords" xlink:type="simple">...</resourceRelation> … </relations>

  19. <cpfRelation> – CPF relation Brief description: The <cpfRelation> element contains the description of a corporate body, person, or family related to the described CPF entity. Such related entities are typically described in another EAC-CPF instance. Can contain following sub elements: <relationEntry> <date> <dateRange> <dateSet> <placeEntry> <descriptiveNote> Can contain following attributes: @cpfRelationType, @lastDateTimeVerified, @xml:lang, xlink:type, @xlink:hrer, @xlink:arcrole, @xlink:role, @xlink:title

  20. <relationEntry> – CPF relation <relationEntry> – Relation entry Brief description: A descriptive element of the relation. A descriptive element for relations that provides discursive text identifying a related CPF entity, a resource created by or otherwise related to the named CPF entity (eg, archival records), or the name of a related function. Can contain following sub elements: NO Can contain following attributes: @localType  values! @scriptCode @transliteration @xml:lang

  21. cpfRelation element – example <relations>… <cpfRelation xmlns:xlink="http://www.w3.org/1999/xlink" xlink:arcrole="associatedWith" xlink:role="http://RDVocab.info/uri/schema/FRBRentitiesRDA/Person"xlink:type="simple"> <relationEntry>Alsop, Stewart.</relationEntry> <descriptiveNote> <p>recordId: DLC.ms008095.c2</p> </descriptiveNote> </cpfRelation> <cpfRelation xmlns:xlink="http://www.w3.org/1999/xlink" xlink:arcrole="correspondedWith" xlink:role="http://RDVocab.info/uri/schema/FRBRentitiesRDA/Person"xlink:type="simple"> <relationEntry>Bethe, Hans A. (Hans Albrecht), 1906-2005.</relationEntry> <descriptiveNote> <p>recordId: DLC.ms998007.r001</p> </descriptiveNote> </cpfRelation> … </relations> Finding Aid PermalinkCite http://hdl.loc.gov/loc.mss/eadmss.ms998007

  22. Example from socialarchive.iath.virginia.edu 4

  23. resourceRelation-element <resourceRelation xmlns:xlink="http://www.w3.org/1999/xlink" xlink:arcrole="creatorOf" xlink:href="http://hdl.loc.gov/loc.mss/eadmss.ms998007"xlink:role="archivalRecords" xlink:type="simple"> <relationEntry> J. Robert Oppenheimer Papers, 1799-1980 (bulk 1947-1967) </relationEntry> <objectXMLWrap> <did xmlns="urn:isbn:1-931666-22-9" id="mferd5940e69"> ... </did> </objectXMLWrap> </resourceRelation>

  24. did-element (EAD-element) did = content of the finding aid <did xmlns="urn:isbn:1-931666-22-9" id="mferd5940e69"> <head>Collection Summary</head> <unittitle encodinganalog="245$a" label="Title">...</unittitle> <unitid countrycode="US" encodinganalog="590" label="ID No." repositorycode="US-DLC">MSS35188</unitid> <origination label="Creator"> <persname encodinganalog="100" source="lcnaf">Oppenheimer, J. Robert, 1904-1967</persname> </origination> <physdesc label="Extent"> <extent encodinganalog="300">74,000 items</extent> <extent encodinganalog="300">294 containers plus 2 classified</extent> <extent encodinganalog="300">117.4 linear feet</extent> </physdesc> <langmaterial label="Language">...</langmaterial> <repository encodinganalog="852" label="Location">...</repository> <abstract encodinganalog="520$a" label="Summary">...</abstract> </did>

  25. BioHist and relations (Bernstein) <biogHist><chronList> <chronItem> <date>1918</date> <event>Born August 25, Lawrence, Massachusetts, first child of Samuel and Jennie Bernstein. </event> </chronItem> …. <chronItem> <date>1957</date> <event>Joint principal conductor, New York Philharmonic, 1957- 58; premiere of West Side Story; conducted inaugural concert of Mann Auditorium, Tel Aviv. </event> </chronItem> …. </chronList></biogHist>

  26. BioHist and relations (Bernstein) <relations> … <resourceRelation xlink:arcrole="referencedIn" xlink:href="http://www.oac.cdlib.org/findaid/ark:/13030/tf6d5nb1hh" xlink:role="archivalRecords" xlink:type="simple" xmlns:xlink="http://www.w3.org/1999/xlink"> <relationEntry>Stefan Lorant collection ca. 1869-1993 1920-1992</relationEntry>…</ <resourceRelation> …. <resourceRelation xlink:arcrole="creatorOf" xlink:role="resource" xlink:type="simple"><relationEntry>West Side story.</relationEntry></resourceRelation>…. <resourceRelation xlink:arcrole="creatorOf" xlink:role="resource" xlink:type="simple"><relationEntry>Symphonic dances from &quot;West side story&quot;</relationEntry> … </relations>

  27. Problem (Bernstein) • No identification between bioHist and relations • <chronItem><date>1957</date><event>Joint principal conductor, New York Philharmonic, 1957-58; premiere of West Side Story; conducted inaugural concert of Mann Auditorium, Tel Aviv.</event></chronItem> • <resourceRelation xlink:arcrole="creatorOf" xlink:role="resource" xlink:type="simple"><relationEntry>West Side story.</relationEntry></resourceRelation>

  28. Mapping to CRM 1 • Identity part is a set of alternative appellations • <chronItem> can be mapped to a temporal entity (events) • Relations: the mapping will depend on the type and the sub types, e.g. attr: xlink:arcrole

  29. Mapping to CRM 2 • Relations: the mapping will depend on the type and the sub types, e.g. • attr: xlink:arcrole, no controlled vocabulary • attr: cpfRelationType – value list suggested not used in socialarchive.iath.virginia.edu • <cpfRelation> • associatedWith, correspondedWith, … • <functionRelation> • controls, owns, performs, … • <resourceRelation> • referencedIn, creatorOf, …

  30. Mapping to CRM 3 • General problem • Events in EAC-CPF cannot contain relations • No linking between instances of relations and events • Minimal suggestion • Adjust the XML-schema for EAC-CPF add relations to <chronItem> • Introduce at least record internal identifiers in addition to the current use of free text descriptions

More Related