Versions Compared

Old Version 3

changes.mady.by.user Sarah Potvin

Saved on

compared with

New Version Current

changes.mady.by.user Maureen Walsh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Examples of simple mappings of the current "DCdc" registry schema in the DSpace metadata registry into "dcterms" (DCTERMS), "qdc" (QDC), and Local registries"local" (Local) schemas:

1.8 "DC" DSpace registry schema termDCTERMSQDClocal
dc.publisherdcterms:publisherqdc.publishern/a

dc.publisher maps very simply to dcterms and qdc values of publisher. Because the element matches in dcterms and qdc, there is no need to devise a local registry element.

1.8 "DC" DSpace registry schema termDCTERMSQDClocal
dc.identifier.citationdcterms:bibliographicCitationqdc.identifier.bibliographicCitation 

...

More complicated mappings:

1.8 "DC" DSpace registry schema termDCTERMSQDClocal
dc.relation.ispartofseriesThere is no direct match in DCTERMS. Can specify that this refines dcterms:isPartOf?There is no direct match in QDC. Can add qdc.relation.ispartofseries or relegate to local?local.relation.ispartofseries
dc.identifier.isbnNo direct match. Refines dcterms:identifier.No direct match. Refines qdc.identifier.local.identifier.isbn

...

  • Decision point: map this refinement to DCTERMS and QDC, thus flexing compliance? Or map to local? When there are no direct matches in DCTERMS and QDC, it is preferable to extend those namespaces to incorporate refinements to existing elements? Or to move to local?

 

1.8 "DC" DSpace registry schema termDCTERMSQDClocal
dc.description.provenancedcterms:provenanceqdc.provenancelocal.dspace.provenance?

...

  • Decision point: Separate DSpace administrative field into local namespace and reserve DCTERMS and QDC terms for users? Or directly map between registries without distinguishing DSpace-filled fields?

 

 

1.8 "DC" DSpace registry schema termDCTERMSQDClocal
dc.date.accessionedNo direct match. Map to dcterms:dateAccepted?No direct match. Map to qdc.date.accepted?local.date.accessioned

Are dcterms:dateAccepted and qdc.date.accepted reasonable mappings for dc.date.accessioned? Or should this DSpace-generated value be relegated to a local element? According to DCTERMS documentation, dateAccepted is defined as "Date of acceptance of the resource," with Comment: "Examples of resources to which a Date Accepted may be relevant are a thesis (accepted by a university department) or an article (accepted by a journal)." This definition seems distinct from the DSpace-filled dc.date.accessioned value.