1 / 58

Encoded Archival Context – Corporate Bodies, Persons and Families

Encoded Archival Context – Corporate Bodies, Persons and Families. New SAA Standard September/October 2014 Katherine M. Wisser. Agenda. ISAAR (CPF) and EAC- CPF Entities and Identities Overview of the standard Overview of existing data Implementations of EAC-CPF Discussion.

debrak
Download Presentation

Encoded Archival Context – Corporate Bodies, Persons and Families

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. Encoded Archival Context – Corporate Bodies, Persons and Families New SAA Standard September/October 2014 Katherine M. Wisser

  2. Agenda • ISAAR(CPF) and EAC-CPF • Entities and Identities • Overview of the standard • Overview of existing data • Implementations of EAC-CPF • Discussion

  3. ISAAR (CPF) and EAC-CPF

  4. Roots of Archival Description The three Dutchmen and the principles for archival description: Principle 8: “the various archival collections placed in a depository must be kept carefully separate.” Respect de Fonds: Connection to administrative body or official to whom documents belong, (p. 34).

  5. Contextual information and archival description DACS Principle 2: The principle of respect des fonds is the basis of archival arrangement and description. Principle 8: The creators of archival materials, as well as the materials themselves, must be described. 2.7: Administrative/Biographical History

  6. Why EAC-CPF? • ISAD(G) and 3.2 Context Area • 3.2.1: Name of creator(s) • 3.2.2: Administrative/Biographical history • ISAAR(CPF) “a separate ICA standard, International Standard Archival Authority Record for Corporate Bodies, Persons and Families: ISAAR(CPF), has been developed. ISAAR(CPF) gives general rules for the establishment of archival authority records that describe the corporate bodies, persons, and families that may be named as creators in descriptions of archival documents.” ISAD(G) I.14

  7. ISAAR (CPF) • 5.1 Identity Area • 5.2 Description Area • 5.3 Relationships Area • 5.4 Control Area • 6 Relating corporate bodies, persons and families to archival materials and other resources [DACS 2nd ed.: Chapters 10-14]

  8. Entities and Identities

  9. EAC-CPF Concepts Single Identity (most common) Multiple Identities – Many in one Multiple Identities – One in many Collaborative Identity Alternative set Example: Milne, A. A. (Alan Alexander), 1882-1956

  10. EAC-CPF Concepts Single Identity (most common) Multiple Identities – Many in one Multiple Identities – One in many Collaborative Identity Alternative set

  11. EAC-CPF Concepts Single Identity (most common) Multiple Identities – Many in one Multiple Identities – One in many Collaborative Identity Alternative set

  12. EAC-CPF Concepts Single Identity (most common) Multiple Identities – Many in one Multiple Identities – One in many Collaborative Identity Alternative set

  13. Overview of the Standard

  14. Basic structure <eac-cpf> <control></control> <cpfDescription> <identity></identity> <description></description> <relations></relations> </cpfDescription> </eac-cpf>

  15. Basic Structure <control>: identity, creation, maintenance, status, rules and authorities, and sources used to generate the EAC-CPF instance. <cpfDescription>: description of the EAC-CPF entity • <identity>: names • <description>: formal and informal descriptive elements • <relations>: relationships to other entities, resources and function descriptions

  16. <control>

  17. <control>: required fields • <recordId> • <maintenanceStatus> • <maintenanceAgency> • <maintenanceHistory>

  18. <control>: required fields • <recordId> • <maintenanceStatus> • <maintenanceAgency> • <maintenanceHistory> Controlled list of values: cancelled deleted deletedReplaceddeletedSplit derived new revised

  19. <control>: required fields • <recordId> • <maintenanceStatus> • <maintenanceAgency> • <maintenanceHistory> contains: <agencyCode> <agencyName> <descriptiveNote> <otherAgencyCode>

  20. <control>: required fields • <recordId> • <maintenanceStatus> • <maintenanceAgency> • <maintenanceHistory> contains: <maintenanceEvent> contains: <agent> <agentType>: human, machine <eventType>: cancelled, created, deleted, derived, revised, updated <eventDateTime> <eventDescription>

  21. <control>: other fields>: optional fields • <otherRecordId> • <publicationStatus> • <languageDeclaration> • <conventionDeclaration> • <localControl> • <localTypeDeclaration> • <sources>

  22. <control>all fields • <recordId> (Required) • <otherRecordId> (Optional) • <maintenanceStatus> (Required) • <publicationStatus> (Optional) • <maintenanceAgency> (Required) • <languageDeclaration> (Optional) • <conventionDeclaration> (Optional) • <localTypeDeclaration> (Optional) • <localControl> (Optional) • <maintenanceHistory> (Required) • <sources> (Optional)

  23. <cpfDescription>

  24. <cpfDescription>/<identity> : required fields • <entityType> • <nameEntry> * • <nameEntryParallel> * * <identity> requires either a <nameEntry> or a <nameEntryParallel> element.

  25. <entityType> • corporateBody • person • family

  26. Basic name models <nameEntry> <part>Milne, A. A. (Alan Alexander)</part> <useDates> <dateRange> <fromDate>1882</fromDate> <toDate>1956</toDate> </dateRange> </useDates> </nameEntry>

  27. <nameEntry> <part>Milne, A. A.</part> <part>(Alan Alexander)</part> <useDates> <dateRange> <fromDate>1882</fromDate> <toDate>1956</toDate> </dateRange> </useDates> </nameEntry>

  28. @localType “a means to narrow the semantic meaning” To facilitate exchange of EAC-CPF instances, it is highly recommend that the URI be absolute and resolvable to a local resource that describes the semantic scope and use of the value.

  29. <nameEntry> <part localType=“$a”>Milne, A. A.</part> <part localType=“$q”>(Alan Alexander)</part> <useDates localType=“$d”> <dateRange> <fromDate>1882</fromDate> <toDate>1956</toDate> </dateRange> </useDates> </nameEntry>

  30. Multilingual names: <nameEntryParallel> <nameEntryParallel> <nameEntry xml:lang=“eng”> <part>Library and Archives Canada</part> </nameEntry> <nameEntry xml:lang=“fre”> <part>Bibliotheque et archives Canada</part> </nameEntry> </nameEntryParallel>

  31. Additional aspects of names • <authorizedForm> • <alternativeForm> • <preferredForm>

  32. <cpfDescription>/<identity> • <entityType> (Required) • <nameEntry> (Required)* • <nameEntryParallel> (Required)* • <entityId> (Optional) • <descriptiveNote> (Optional) Generally for corporate bodies

  33. <cpfDescription>/<identity> • <entityType> (Required) • <nameEntry> (Required)* • <nameEntryParallel> (Required)* • <entityId> (Optional) • <descriptiveNote> (Optional) includes <p>

  34. <cpfDescription>/<description> • <existDates> • <function> • <generalContext> • <legalStatus> • <languageUsed> • <mandate> • <occupation> • <place> • <biogHist> • <structureOrGenealogy> • <localDescription>

  35. Description data models <function>, <legalStatus>, <mandate>, <occupation>, <localDescription> Includes: <term> But you can also contextualize with: <citation>, <date>, <dateRange>, <dateSet>, <descriptiveNote>, and <placeEntry>

  36. About Dates • <date> : a single date • <dateRange> : a range of dates, includes <fromDate> and <toDate> • <dateSet> : a combination of <date> and <dateRange> elements for complex date statements • Date attributes: @notAfter, @notBefore, @standardDate

  37. Specific models • <existDates> <date>, <dateRange>, <dateSet> • <place> <placeRole>, <placeEntry> • <languageUsed> <language>, <script>

  38. Informal Descriptive elements <biogHist>, <generalContext>, <structureOrGenealogy> Formatting elements: <citation>, <list>, <outline>, <p> * note: <biogHist> also includes <abstract> and <chronList>

  39. Grouping elements • <functions> • <languagesUsed> • <legalStatuses> • <localDescriptions> • <mandates> • <occupations> • <places>

  40. <cpfDescription>/<relations> • <cpfRelation> • <functionRelation> • <resourceRelation> • @*RelationType • <relationEntry> • <objectBinWrap> • <objectXMLWrap> • <date>, <dateRange>, <dateSet> • <placeEntry> • <descriptiveNote>

  41. <relations>: relation types cpfRelationType: identity, hierarchical, hierarchical-parent, hierarchical-child, temporal, temporal-earlier, temporal-later, family, associative resourceRelationType: creatorOf, subjectOf, other functionRelationType: controls, owns, performs • <cpfRelation> • <functionRelation> • <resourceRelation> • @*RelationType

  42. <relations>: relation information • <cpfRelation> • <functionRelation> • <resourceRelation> • @*RelationType • <relationEntry> • <objectBinWrap> • <objectXMLWrap> • <date>, <dateRange>, <dateSet> • <placeEntry> • <descriptiveNote>

  43. <relations>: relation context • <cpfRelation> • <functionRelation> • <resourceRelation> • @*RelationType • <relationEntry> • <objectBinWrap> • <objectXMLWrap> • <date>, <dateRange>, <dateSet> • <placeEntry> • <descriptiveNote>

  44. Extensible Design • <descriptiveNote> • <localDescription> • <localControl> • @localType

  45. Multiple Identities: One in many <eac-cpf> <control></control> <cpfDescription> <identity></identity> <description></description> <relations> <cpfRelation></cpfRelation> <cpfRelation></cpfRelation> </relations> </cpfDescription> </eac-cpf>

  46. Or, ….Many in one: <multipleIdentities> <eac-cpf> <control></control> <multipleIdentities> <cpfDescription></cpfDescription> <cpfDescription></cpfDescription> <cpfDescription></cpfDescription> </multipleIdentities> </eac-cpf>

  47. Finding the Standard

  48. http://eac.staatsbibliothek-berlin.de/

More Related