Metadata Schema Comparison
Here we compare the qualifid Dublin Core fields that are default in DSpace to corresponding fields in ETD-MS and TDM.
|
ETD-MS Element |
ETD-MS Sub-Element |
Qualified Dublin Core Element |
Comments |
|
title |
title |
||
|
alternativeTitle |
title.alternative |
||
|
creator |
contributor.author |
DSpace suggests not using the “creator” element in DC, and instead to use the contributor element |
|
|
subject |
subject |
This is a “catch-all” situation, and we may wish to use additional qualifiers for different situations. |
|
|
description |
description.abstract |
||
|
publisher |
publisher |
||
|
contributor |
contributor.advisor |
This covers the advisor, but there still remains what, if anything, to do with the committee members |
|
|
date |
date.* |
Use multiple qualified date elements. |
|
|
type |
type |
||
|
format |
format.mimetype |
This fits exactly the specification for ETD-MS, but we may wish to take advantage of the extra fields in QDC. |
|
|
identifier |
identifier.* |
||
|
language |
language.iso |
We should stick to the standard ISO language formats. |
|
|
coverage |
coverage.* |
||
|
rights |
rights |
||
|
degree |
This may be implicit in the location it is entered into DSpace, but we may want a metadata record also. |
||
|
name |
subject |
||
|
level |
|||
|
discipline |
subject |
||
|
grantor |
description.sponsorship/ contributor.other/ contributor |
One of these options may be the correct place in the QDC to store the degree granting institution. |
TDM DTD Specification
|
TDM Element Path |
Qualified Dublin Core Element |
Comments |
|
date |
date.* |
Use multiple qualified date elements. |
|
pages |
coverage.spatial |
|
|
publisher |
publisher |
|
|
editor |
contributor.editor |
|
|
pubPlace |
??? |
|
|
volumeissue |
??? |
|
|
head |
N/A |
Head is a method of splitting up the actual document
|
|
head.title |
title |
|
|
body |
N/A |
Body is a method of splitting up the actual document
|
|
body.front |
N/A |
Front is a method of splitting up the actual document
|
|
body.front.titlePage |
N/A |
TitlePage is a method of splitting up the actual document
|
|
body.front.titlePage.docTitle |
title |
How this differs from head.title is unclear, but there should be no problem making them identical
|
|
body.front.titlePage.docTitle.worktitle |
title.alternative |
|
|
body.front.titlePage.docTitle.author |
contributor.other |
This field is for noting whose work has been used within the item.
|
|
body.front.titlePage.docAuthor |
contributor.author |
|
|
body.front.titlePage.docDate |
date.* |
Use multiple qualified date elements.
|
|
body.front.titlePage.thesisadvisor |
contributor.advisor |
|
|
body.front.thesiscopyright |
N/A |
The copyright is stored with the item in DSpace
|
|
body.front.certifapproval |
??? |
This may not be necessary
|
|
body.front.dedication |
N/A |
Content
|
|
body.front.epigraph |
N/A |
Content
|
|
body.front.acknowledgements |
N/A |
Content
|
|
body.front.abstract |
N/A |
This refers to the document segment
|
|
body.front.abstract.abstractcover |
N/A |
Layout
|
|
body.front.abstract.abstractext |
description.abstract |
|
|
body.front.abstract.abstractext.worktitle |
N/A |
No need for another title field
|
|
body.front.abstract.abstractapproval |
N/A |
Implicit in workflow
|
|
body.front.toc |
description.tableofcontents |
|
|
body.front.tablelist |
N/A |
Content
|
|
body.front.figurelist |
N/A |
Content
|
|
body.front.symbolabbrevlist |
N/A |
Content
|
|
body.front.preface |
N/A |
Content
|
|
body.back |
N/A |
Back is a method of splitting up the actual document
|
|
body.back.notes |
N/A |
Content
|
|
body.back.bibl |
N/A |
Content
|
|
body.back.appendix |
N/A |
Content
|
|
body.back.appendix.argument |
N/A |
Content
|
The following table suggests the fields that we might collect for an ETD. The first section shows fields that are definitely required, whilst the second section shows fields that could be included if we deem it necessary. The final section shows fields that can be automatically completed by the system during submission.
We must decide, then, which of the “Possible Form Elements” we wish to include in our final metadata set.
|
Field Name |
Qualified Dublin Core Element |
Comments |
|
Submission Form Elements |
||
|
Title |
title |
|
|
Alternative Title |
title.alternative |
|
|
Author |
contributor.author |
|
|
Abstract |
description.abstract |
|
|
Supervisor |
contributor.advisor |
|
|
Type |
type |
PhD Thesis or Masters etc… |
|
Language |
language.iso |
Default “en” |
|
Keywords |
subject |
|
|
Sponsors |
description.sponsorship |
|
|
Possible Form Elements |
||
|
Publisher |
publisher |
The publisher of the work in whole or part |
|
Editor |
contributor.editor |
The editor from the publishing body |
|
Coverage |
coverage |
Any spatial or temporal information. |
|
Rights |
rights |
Rights metadata |
|
Degree Name |
subject |
Name of course. |
|
Degree Level |
type |
PhD Thesis or Masters etc, duplicate of “Type” |
|
Discipline |
subject |
|
|
Number of Pages |
coverage.spatial |
|
|
Quoted/Included Work |
contributor.other |
Anyone who’s work has been relied upon to form the text. |
|
Table of Contents |
description.tableofcontents |
Students may not want to have to enter this |
|
Bibliography |
description.bibliographicCitation |
Free Text bibliography to aid serarching. This is not part of DSpace by default, but does belong to the QDC set. |
|
Implicit Metadata Elements |
||
|
Subject Category |
subject.classification |
From community/collection being submitted to. |
|
Format (file mime-type) |
format.mimetype |
Mime-Type |
|
Format (file size) |
format.extent |
File Size in bytes |
|
Date Issued |
date.issued |
|
|
Date Accessioned |
date.accessioned |
|
|
Date Available |
date.available |
|
|
Date Submitted |
date.submitted |
|
|
Degree Grantor |
contributor/description |
QDC field uncertain for this option, but implicit to UoE |
|
Identifier |
identifier.uri |
Handle server URI |