Page History
...
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 term | DCTERMS | QDC | local |
|---|---|---|---|
| dc.identifier.citation | dcterms:bibliographicCitation | qdc.identifier.bibliographicCitation |
...
- 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 term | DCTERMS | QDC | local |
|---|---|---|---|
| dc.description.provenance | dcterms:provenance | qdc.provenance | local.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 term | DCTERMS | QDC | local |
|---|---|---|---|
| dc.date.accessioned | No direct match. Map to dcterms:dateAccepted? | No direct match. Map to qdc.date.accepted? | local.date.accessioned |
...
Overview
Content Tools