Date

December 19, 2013

Attendees

• Sarah Potvin

• Unknown User (mpwalsh)

• Bram Luyten (Atmire)

• @Monica Rivero

Discussion Items/Notes

DSpace metadata not completely flat-- ability to use authority keys (part of 1.6 Authority Control feature). Can be used for LC Name Authority lookup. Also a place to store staff ID, ORCiD, etc. Currently useful as way to hover over value to see additional key or provide lookup. Also queryable when harvested. Integrated in submission form. For proper DCTERMS, would need to enforce use of that authority key for certain terms, and stored literal is more "eye candy" for display.

ContentDM based on DCTERMS? Or just Simple DC?

Application profile and ability to specify multiple schema-- DCTERMS alongside DC, local, thesis, etc.

Potential need to adopt RIOXX for SHARE: http://rioxx.net/v1-0/

Bram Luyten (Atmire) worked to ensure DSpace/RIOXX compliance. 

Will definitely need to maintain DC alongside DCTERMS.

Non-intrusive approach to modifying hard-coded metadata values via JIRA tickets

• Identify any hard coded occurrence of a field, make configurable, retain the same initial value. Will allow us to get rid of hard coding while still keeping everyone on same metadata schema for now
  • Example JIRA ticket:
    • "Remove hard coded references to dc.title"
    • Identify all hard coded occurrences of dc.title and replace them with values that can be stored and retrieved from dspace configuration files.