Page History

...

• 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

display

item import

OAI

---

...

1. for testing purposes, point to current doc for adding local schema if you want to use locally (Bram)

...

1. Check on OAI

...

1. , see

...

1. DC

...

1. Terms schema is

...

1. 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

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

...

1. 2. goal for 5.0 is to have everything

...

1. 1. included, new installs everything

...

1. 1. defaults to DC Terms

...

1. 2. perhaps 2nd phase

...

1. 1. 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

...

1. 1. keep metadata flat - if you add hierarchal metadata it complicates the use of DSpacee
   2. create an application profile or validator to support

...

1. 1. – so assumptions can be questioned and vetted – makes it easier for people to give feedback on

---

...

1. 1. create web services query tool (Richard's idea) - to find out

...

1. 1. 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?

task & finsh on project phasing

---

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