Page tree
Skip to end of metadata
Go to start of metadata


Feb 25, 2014



  • JIRA tickets-- any further discussion?
    • Ticket on making dc.contributor.* dependencies configurable has been created:  DS-1927 - Getting issue details... STATUS
    • Next step would be to get confirmation from other committers that this is a good approach
    • After that, we need to find time/volunteers to do this work.
  • Mark Wood's initial code contribution for collection & community metadata
    • DS-1582 - Getting issue details... STATUS
    • Work in progress and code review needed
  • Conferences
    • OR2014 proposal
    • Coverage at SPARC?
    • DC2014 proposal?
  • Orient Stefanie Ruehle, who has graciously agreed to serve as task & finish, to the project.
    • Team members introduce themselves
      • Elin is chairing group that is updating metadata standards for Norway libraries
      • Stefanie's institution uses DSpace, has done some mapping from DSpace to other metadata formats. Experience with the data that is coming out of DSpace.
    • Origins/impetus of the project
    • Feedback from Diane Hillman
    • Decision to retain flat metadata in first incarnation
    • Particular constraints of DSpace data model
    • Work by Richard Rodgers to build mapping tool
    • Decision to transition from QDC to DCTERMS and DC
    • Interest in integrating other schemas to ship with DSpace
    • DCTERMS as an optional schema that now ships with DSpace 4.0
    • Related projects

Question from Stefanie of whether we will ever be able to move to non-flat metadata. Example of dcterms.publisher and need to use URI, as specified in domain and range. If only providing a string, will need to use dc.publisher rather than dcterms.publisher. Bram suggests could store a URI but would need functionality of human lookup name for that URI, for display. These values would not necessarily reside in the metadata but in some other index. Maureen suggests need to supercede and maybe replace the old mappings-- more current mapping would indicate that both DCTERMS and DC ship with DSpace. Do need to address the mapping document.

Bram asks about QDC in the DC community. Stefanie reports that most projects use DCTERMS alongside DC. Did some work on application profile for RDF representation, published this year, using DC, DCTERMS, and terms from other vocabularies, like VIVO, to describe objects. Use of MARC relator codes ( and URIs for qualified contributors. References user guide: Need a mix&match approach, ability to pull in terms beyond Dublin Core. Bibframe, replacement for MARC, working on vocabularies for bibliographic data. Focus on work & instance as a version/simplification of FRBR. In RDF: qualifier = subproperty. MARC relator code expressed as subproperty of creator or contributor. 

Discussion of whether RDF needs to be integrated into DSpace internal format or not. Possibility, instead, of capability to crosswalk RDF out of internal format. Stefanie indicates that this is a matter of preference-- some prefer that the internal format of the database be distinct from the export format (makes it more flexible to transform to DC, DC RDF, MODS, etc.). Not absolutely fixed on the format-- more flexible and allows for transformation. But have to make sure that what is in the data is what you really need to generate RDF. Need to be able to store URIs and MARC relator codes in internal format. Others say it is easier to keep data in the format you intend for distribution. Points us to German National Library and data transformation efforts ( Recommendation is "rather flat" but seen as "first step on our way to good linked data having in mind the Europeana Data Model... and BIBFRAME."

Stefanie will look at changes her colleagues have made to the original DSpace registry. 

For Dublin Core, possibility of discussing this proposal at the Libraries community meeting.



Discussion Items


Action Items

  • Update DCTERMS/DC mappings on wiki to reflect current recommendations
  • Supply Stefanie with registry that ships with DSpace