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

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

Compare with Current View Page History

« Previous Version 8 Current »

Date

Feb 25, 2014

Attendees

Goals

  • 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 (http://id.loc.gov/vocabulary/relators.html) and URIs for qualified contributors. References user guide: http://wiki.dublincore.org/index.php/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. In RDF: qualifier = subproperty. MARC relator code expressed as subproperty of creator or contributor. 

 

Discussion Items

TimeItemWhoNotes
    

Action Items

  •  
  • No labels