Tools

EAD 1.0 to RSLP CD Schema Mapping

[UKOLN logo]

Note: This document should be read in conjunction with the earlier note on the relationship between ISAD(G) and the RSLP CLD schema.

This document supercedes the earlier draft of 21 June 2001

A separate ISAD(G) Second Edition to RSLP CD mapping is available.

This document addresses the mapping of the Encoded Archival Description (EAD) elements as they are described in the EAD 1.0 Tag Library and EAD Application Guidelines. In particular, it reflects the EAD-encoding conventions which have been adopted by the UK Archives Hub in their data entry template (though it does include some correspondences of elements not utilised in that template.

It is recognised that EAD allows considerable flexibility and that implementers' encoding conventions may vary: implementers will need to tailor this mapping to local EAD encoding and content conventions.

EAD includes

The RSLP CD schema can be used to describe either a collection or a catalogue (a collection of metadata records). The tables below provide two mappings, firstly for the description of the collection, secondly for the description of the EAD-encoded catalogue/finding aid.

Note: See also the "conservative" Dublin Core-EAD mappings in Appendix B.3 of EAD 1.0 Application Guidelines

In the case of both the Collection and the Catalogue, the RSLP CD "record" consists of a set of related resource descriptions: descriptions of the Collection (or Catalogue), the Location of the Collection, the Collection of the Collection, the Owner of the Collection, and the Administrator of the Location.

In the right hand column of the table below, the token in brackets (e.g. [Collection]) indicates the resource and the second, for convenience in the form of an XML QName (e.g. dc:title), indicates the name of the property of that resource. The same named property may occur in association with more than one resource e.g. both the Collection and the Location may have a dc:title property.

The namespace prefixes used in the XML QNames are assumed to be associated with XML namespace names as follows:

An EAD document can be represented in both SGML and XML. In the tables below EAD elements are listed "in context", using a simple XPath-like syntax to signal "parent-child" element containment relationships and element-attribute relationships as the elements typically occur within the XML "tree". The RSLP CD properties are represented as XML QNames, but the mapping is intended to be neutral on the form in which an RSLP collection description is represented.

Description of collection

EAD
archdesc (or c)		 RSLP CD Note

Attributes of archdesc (or c) element

@langmaterial

[Collection] dc:language

  

@legalstatus

or

[@legalstatus='otherlegalstatus']/ @otherlegalstatus

[Collection] rslpcd:legalStatus

  

@level

or

[@level='otherlevel']/ @otherlevel

[No correspondence.]

Could be used as part of an archive-specific collection type list
i.e. as value of [Collection] dc:type,
but this is not part of the CLDT type list.

Child elements of did element

did/unitid/@countrycode

and

did/unitid/@repositorycode

and

did/unitid

[Collection] dc:identifier

  

did/unittitle

[Collection] dc:title

  

did/unitdate

[Collection] rslpcd:contentsDateRange

and

[Collection] dcterms:temporal

  

did/origination/persname

[Collector] vcard:fn

and

[Collection] rslpcd:agentName

In EAD, this is the name of the individual or organization responsible for the creation, accumulation, or assembly of the described materials before their incorporation into an archival repository. In most cases, this will correspond to the the RSLP CD concept of the Collector, but there may be some cases where it does not. If necessary, the selection of the EAD element might be further specified using the value of the role attribute.

Where a normalised form of the name is provided (as the value of the normal attribute, that value should be used.

did/origination/corpname

[Collector] vcard:org

and

[Collection] rslpcd:agentName

In EAD, this is the name of the individual or organization responsible for the creation, accumulation, or assembly of the described materials before their incorporation into an archival repository. In most cases, this will correspond to the the RSLP CD concept of the Collector, but there may be some cases where it does not. If necessary, the selection of the EAD element might be further specified using the value of the role attribute.

Where a normalised form of the name is provided (as the value of the normal attribute, that value should be used.

did/physdesc/

[Collection] dc:format

  

did/physloc/

[No correpondence]

EAD usage generally refers to specific location within repository. That value would not be appropriate as [Location] dc:title in most cases.

did/repository/corpname

[Administrator] vcard:org

Where a normalised form of the name is provided (as the value of the normal attribute, that value should be used.

did/repository/address

[Location] cld:address

  

did/abstract

[Collection] dc:description

Should probably be mapped only if full scopecontent element not available.

(End of child elements of did element)

bioghist

[Collector] cld:agentHistory

  

scopecontent

[Collection] dc:description

  

arrangement

[No correspondence]

  

organization

[No correspondence]

  

Child elements of admininfo element

admininfo/acqinfo

[Collection] rslpcd:custodialHistory

  

admininfo/custodhist

[Collection] rslpcd:custodialHistory

  

admininfo/custodhist/
date[@type="accumulation"]

[Collection] rslpcd:accumulationDateRange

  

admininfo/appraisal

[Collection] cld:custodialHistory

  

admininfo/accruals

[Collection] cld:accrualStatus

  

admininfo/processinfo

[No correspondence.]

Could be "dumbed-down" to [Collection] dc:description

admininfo/accessrestrict

[Collection] cld:accessControl

  

admininfo/userestrict

[Collection] cld:accessControl

  

admininfo/altformavail

[No correspondence]

Could be "dumbed-down" to [Collection] dc:description

admininfo/prefercite

[Collection] dc:title

  

(End of child elements of admininfo element)

Child elements of add element

add/otherfindaid

[Collection] hasDescription

  

add/relatedmaterial

[Collection] cld:hasAssociation

  

add/separatedmaterial

[Collection] cld:hasAssociation

  

add/bibliography

[Collection] cld:hasPublication

  

End of child elements of add element

odd

[Collection] cld:note

  

Child elements of controlaccess element

controlaccess/subject

[Collection] dc:subject

Where a normalised form of the name is provided (as the value of the normal attribute, that value should be used.

controlaccess/persname

[Collection] cld:agentName

Where a normalised form of the name is provided (as the value of the normal attribute, that value should be used.

controlaccess/corpname

[Collection] cld:agentName

Where a normalised form of the name is provided (as the value of the normal attribute, that value should be used.

controlaccess/geogname

[Collection] dcterms:spatial

Where a normalised form of the name is provided (as the value of the normal attribute, that value should be used.
 

[Collection] dc:type

For a description of an archival collection, the value of [Collection] dc:type should be "collection.archive"

Description of catalogue

EAD
eadheader		 RSLP CD Note

eadid

[Collection] dc:identifier

  

filedesc/titlestmt/titleproper

[Collection] dc:title

  

filedesc/titlestmt/author

[Collector] vcard:fn

  

filedesc/publicationstmt/publisher

[Administrator] vcard:fn

  

filedesc/notestmt/note

[Collection] cld:note

  

profiledesc/langusage/language

[Collection] dc:language

  

revisiondesc/list/item/date

[Collection] cld:contentsDateRange

  
 

[Collection] dc:type

For a description of a catalogue of an archival collection, the value of [Collection] dc:type should be "finding-aid.archive"
Maintained by: Pete Johnston
Last updated: 26-Mar-2003

[UKOLN]  [Collection Description Focus]  [Tools]

 [RSLP logo]