...
- 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
- Update documentation - DC Terms added
display
item import
OAI
---
...
- for testing purposes, point to current doc for adding local schema if you want to use locally (Bram)
...
- Check on OAI
...
- , see
...
- DC
...
- Terms schema is
...
- included (Maureen)
---
implications for new features, like RequestCopy, what metadata to use? dc.requestcopy.email, dc.requestcopy.name – use dspace.requestcopy.email, and dspace.requestcopy.name – need to keep running list of what needs to be cleaned up
--
...
Project Re-phasing Work
- Revise proposal page
- make old proposal a child of current proposal page as reference point / to mtn history
- revise proposal page on main page - streamline, focus on standards, don't focus on 'easing' as much
...
- goal for 5.0 is to have everything
...
- included, new installs everything
...
- defaults to DC Terms
...
- perhaps 2nd phase
...
- could be to create tools to help w/upgrade
---
task & finish group - get DC experts, ask very concrete questions rather than open ended questions, after re-doing the proposal make list of questions,
Sarah: does this create a need for hiearchal metadata; Maureen - have to think flatly, it is easier, less complicated
...
- keep metadata flat - if you add hierarchal metadata it complicates the use of DSpacee
- create an application profile or validator to support
...
- – so assumptions can be questioned and vetted – makes it easier for people to give feedback on
---
...
- 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
...
- Start a list of metadata implications for new features – identify what needs to be cleaned up
- like RequestCopy, what metadata to use? dc.requestcopy.email, dc.requestcopy.name – use dspace.requestcopy.email, and dspace.requestcopy.name
- Task & finish groups
- DC mapping
- find DC experts – after re-doing the proposal make list of questions, ask very concrete questions rather than open ended questions
- or, if can't resolve for free, request DSpace Steering Cmte allocate funds for consultants
- On application profile
- Others?
- DC mapping
task & finsh on project phasing
---
Next mtg for metadata team on 11/26 at 10am Eastern