What is DublinCore (dc)?
DublinCore is metadata, which is to say data about data. According to the DCMIL
The word "metadata" means "data about data". Metadata articulates a context for objects of interest -- "resources" such as MP3 files, library books, or satellite images -- in the form of "resource descriptions". As a tradition, resource description dates back to the earliest archives and library catalogs. The modern "metadata" field that gave rise to Dublin Core and other recent standards emerged with the Web revolution of the mid-1990s.
DublinCore was started 1995 in Dublin (Ohio, USA, not Ireland!) as an attempt to describe items on what was still the newly-popular and organized internet. Essentially, it works as a modern version of the old style library card catalogs.
Originally, DublinCore used only 15 terms–which you can see in the "/elements/1.1/ namespace" box here, along with the current list of terms.
You can see the available dc metadata terms in DSpace listed comprehensively here.
How does IUSW use DublinCore?
IUSW largely uses DublinCore in DSpace. You can see an example of a IUSW DC Metadata below. Here is the item I am using for an example: https://scholarworks.iu.edu/dspace/handle/2022/13398
To edit, add, or change items in our DSpace, go to an item in DSpace, and select "Edit Metadata" on the right hand side – this will only show up if you are logged in.
This is an example of what that looks like, with fake data:
Essential IUSW DublinCore Metadata:
|dc Term||Explanation or Use||Example||Multiple Instances Allowed?|
|dc.contributor.author||Author||dc.contributor.author= Gilbert, Don||Y|
|dc.date.issued||Date it was first made publicly available. Use YYYY-MM-DD format||dc.date.issued= 2018-Jan||N|
URI – usually something with hdl.handle in it. Use only following placeholder if needed (without quotes): "http://hdl.handle.net/WW_HANDLE"
|dc.language.iso||What language is it?||dc.language.iso= en||Y|
|dc.type||The type of work it is. Only use Dataset for data.||dc.type= Dataset|
|dc.title||Title of the article or work.||dc.title= Genes of Lytechinus variegatus, green sea urchin reconstructed with EvidentialGene||N|
|dc.description.abstract||An abstract or first paragraph (essential for ETDs)||dc.description.abstract= The Readers’ Guide to Periodical Literature (RGPL) has be described as a cultural barometer. It supports scholars of history ( ... )||N|
Optional or Case-Specific IUSW DublinCore Metadata:
|dc Term||Explanation or Use (if applicable)||Example||Multiple Instances Allowed?|
|dc.rights.uri||What is the license given to the material?|
Use only following placeholder if needed (without quotes): "http://hdl.handle.net/WW_DOI"
|dc.contributor.advisor||Adviser (for PhD ETD theses)||dc.contributor.advisor= Gray, Donald J.||N|
|dc.description.methodology||Methodology (if provided)||dc.description.methodology= RNA-Seq data of Lytechinus variegatus, green sea urchin are assembled with several RNA assemblers, using multiple options. EvidentialGene pipeline is used to process the many resulting assemblies by coding sequences, translated proteins, and gene evidence, then classify/reduce to a biologically informative transcriptome of primary and alternate transcripts. en||Y|
Is saved elsewhere, other versions exist elsewhere.
Can also link to final version of the published article/paper for the data.
|dc.subject||Subject of item.|
dc.subject= genome informatics en
|dc.description.provenance||If there is an earlier item history that is important for documentation.|
dc.description.provenance= Made available in DSpace on 2011-07-19T20:11:35Z (GMT). No. of bitstreams: 1
|dc.identifier.citation||Citation, if needed or available||dc.identifier.citation= Pierce, J. B., & Shaw, D. (2005). Looking for love in all the wrong places: Accessing sexual and reproductive health information via the Readers’ Guide to Periodical Literature. Library & Information Science Research, 27(4), 467-484||N|
|dc.publisher||Journal title, if published elsewhere (e.g. green deposit)||dc.publisher= Library & Information Science Research||N|
Finalized, exported examples:
README file example: