Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

An example of a very easy mapping of the current "DC" registry in DSpace into DCTERMS, QDC, and Local registries:

1.8 "DC" DSpace registry 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.

 

More complicated mappings:

1.8 "DC" DSpace registry 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

There is no direct mapping between the registry element dc.relation.ispartofseries and either DCTERMS or QDC. Given the lack of QDC and DCTERMS matches, may suggest mapping to a local registry and leaving out of the QDC and DCTERMS registries. Alternately, we could add a qdc.relation.ispartofseries element and develop a way of coding for elements that refine, rather than match to, existing DCTERMS.

  • Decision point: map this refinement to DCTERMS and QDC, thus flexing compliance? Or map to local?

 

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

Dc.description.provenance would seem to be easily mapped to provenance terms in DCTERMS and QDC. This element, however, is automatically filled by DSpace with preservation metadata. Would it be valuable to split the values of this element into local and QDC/DCTERMS fields? This would allow the automatically-generated metadata to be stored in local.dspace.provenance, leaving DCTERMS and QDC provenance fields to be filled by users.

 

 

 

 

 

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.