1) Discussion of project phases / staging

  • as currenly laid out - proposal as written - passing through QDC before moving to DC Terms: Proposed phased schemas
  • straight to DC Terms in 5.0, assuming time for full vetting, guidance from DC experts, feedback, documentation, more tool building

 

2) Discussion on what to include in 4.0 – given project phase discussion what makes sense?

  • Bram's proposed addition of dcterms schema to the default install of DSpace (creating an xml file for dspace/config/registries and a small entry in build.xml so the schema gets registered during the installation of DSpace), without enforcing it as a default yet.
  • Bram's questions: Does this look appropriate? These scope notes tend to talk about "resources" a lot, while I don't know exactly if "resources" is a term frequently used in DSpace. (usually we say items & bitstreams, so maybe some of these "resource" wording can be changed into "item"?)
  • Questions from Ivan: 
    • How does this PR fit into the stages of metadata schema upgrade as proposed by DCAT?
    • What I mean is does this do all that DCAT proposed for 4.0 (for example, I notice this doesn't add the proposed "local" schema)? And what work is planned for 5.0? (6.0?)
    • Next steps / what's still possible? Can code still be merged?
  • Dimitrios XSL transformation - 
    • provides exhaustive map of the DSpace AP elements to dcterms (a la the old qdc.properties).
      • additional elements are now exported
      • language tags are now exported
      • map everything under the dcterms namespace (rather than mixing dc with dcterms. See also [1])
      • Provide additional LOM mappings to dcterms elements (in case LOM metadata exist)
      • assign types to non-literal values
      • You can check it out at [2]. We are using this XSLT as the basis for populating the DSpace ontology of our Semantic Search plugin.

3) Next Steps

  • what work needs to be done for 4.0?
  • what work is next before setting up review groups? 


 

Notes

  • Code freeze yesterday
  • Dec 4th is final release
    • we should describe the addition of DC Terms as being for test purposes and include update scripts in registry 
    • need to make sure documentation covers change
      • new install or upgrade of 4.0 - if you don't touch use it, it won't affect you
      • if you want to use it, will need to add it as a local schema - point to documentation for adding local schema
        • implications for display issues, item import and OAI harvesting
  • Dimitrios' work
    • did DC to DC Terms mapping - doesn't seem to impact our project at all
    • we need DC Terms for OAI  - can't add this now - new DC Terms will not be exposed to OAI - unless OAI for 2.0 included it?

Immediate Actions for 4.0

  1. Update documentation - DC Terms added for testing purposes, point to current doc for adding local schema if you want to use locally (Bram)
  2. Check on OAI, see DC Terms schema is included (Maureen) 

Project Re-phasing Work

  1. Revise proposal page
    1. make old proposal a child of current proposal page as reference point / to mtn history
    2. revise proposal page on main page - streamline, focus on standards, don't focus on 'easing' as much
    3. goal for 5.0 is to have everything included, new installs everything defaults to DC Terms
    4. perhaps 2nd phase could be to create tools to help w/upgrade
    5. keep metadata flat - if you add hierarchal metadata it complicates the use of DSpacee
    6. create an application profile or validator to support – so assumptions can be questioned and vetted – makes it easier for people to give feedback on
    7. create web services query tool (Richard's idea) - to find out how people are using metadata fields - list schemas defined and identify the ones being used
  2. Start a list of metadata implications for new features – identify what needs to be cleaned up
    1. like RequestCopy, what metadata to use? dc.requestcopy.email, dc.requestcopy.name – use dspace.requestcopy.email, and dspace.requestcopy.name
  3. Task & finish groups
    1. DC mapping
      1. find DC experts – after re-doing the proposal make list of questions, ask very concrete questions rather than open ended questions
      2. or, if can't resolve for free, request DSpace Steering Cmte allocate funds for consultants
    2. On application profile
    3. Others?

 

Next mtg for metadata team on 11/26 at 10am Eastern

 

 

 

 

 

 


 

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.