...
goal - see what problems people care about - what should we be tackling with metadata project
- 10-15 5 min: introduction highlight WHO?
- what the work has looked like so far - update dublin core stds in DSpace - seems like an abitrary or narrow task; actuality in looking at how DC stds have evolved looking at more complex metadata needs in the community
- started in Austin committer mtg - commttters wanted to align DSpace dublin core with current std
- part of the goal is to broaden discussion w/community
- metadata std not performing the way we want it to
- as we look at D6 look more at our reqmts
- challenge aroudn flexibity:
- 1) ingest (material in diff std, need to map so fields import correctly)
- 2) crosswalks for exports - for harvesting or other purposes - metadata should be flex enought
- 3) what you want to do w/in your own dspace - how easy is it to manage local needs - separate from import/export needs
- point out problems
- not just stdardize to current dublin core
- adding new metadata standards
- clean ingests / or exporting - if funders have asked for clean ingests / harvesting - more plug and play / easy to use
- getting data in and out is very important for CRIS - ORCHID - ecosystem is much more complex - need to coordinate metadata on national level
- dspace was built to be metadata agnostic - some fields are hard coded - like date
- creating CRIS friendly metadata - creating separate namespace
- creating custom fields - requires you to login to XML in order to do so or sometimes a Java programer to do and rebuild
- why we are having panel, what we want to get out of it
- validate ideas/plans - not missing a reqmt from the community or reqmt by external standards
- 5 3 min or less each: each panelist present backgrounds and views
- specific examples of current challenges and some approaches/solutions
- summary of problems all dealing with
- set up to explain backgroud background - how and why we are invovled in this panel - show audience which person they might most closely relate to
- subtheme: how you have hacked dspace metadata has been hacked? what should be taken in consideration with future DSpace - so that you don't lose your local customization*
- what mistakes have you made with DSpace metadata - what are the implications of workrounds (address an unmet need)
- what would you prefer to do differently
- workarounds for metadata: what/how far have you stretched the metadata in DSpace
- discussion - list of issues - strawman of biggest issues that need to be addressed
- Pedro - adapting DSpace to meet OpenAIRE reqmts
- exporting metadata to diff schemas DC to METS
- doing metadata better for DSpace -
- clean importing /exporting / harvesting
- linked data
- Discussion: a few topic prompts to guide discussion
- how does this plan sync up or create conflicts with your current work?
- linked data - what benefits are there in linked data?
- how to serve common use cases - as everyone repositories evolve?
- how have people hacked DSpace to get it to do what they want - make sure current plan addresses some of those needs
- linking articles and journals in DSpace, ability to define relationships
- CRIS heiararchal metadata needs to be flattened in order to bring into DSpace
- what are the priorities and more imminent problems to tackle
...