Metadata Team Agenda 11.26.13

Opportunity to include anything about recently included dcterms schema and other recommendations in documentation

• add "Metadata Recommendations" to https://wiki.duraspace.org/display/DSDOC4x/Metadata+Recommendations

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.
• After all hard coded fields are configurable, repository managers could more easily switch to a new schema by moving all the metadata to the fields in the new schema and changing the configuration.
  • Example: after moving every title from dc.title to dcterms.title, the repo manager would only need to do a search & replace on dc.title in a centralized dspace configuration file.
  • Could a tool be built for this step?
• Could start project by identifying the kind of tasks for fields that have the most prominent hard coding problems (title, author, dates, url, description...)
• Any problems with this approach?

• Revised proposal as written: Proposed phased schemas
  • do project phases change
  • list of metadata implications - identify what needs to get cleaned up
  • what tools would be helpful
  • how could task & finish / review groups be helpful