...
Time | Item | Who | Notes |
---|---|---|---|
5 min | Review proposed agenda - add/change as necessary | Val | |
10 min | Opportunity to include anything about recently included dcterms schema and other recommendations in documentation
| Bram |
|
15 min | Non-intrusive approach to modifying hard-coded metadata values via JIRA tickets |
| |
25 | Impact of above approach on project phases: |
| |
5 min | Next steps - including next metadata team mtg |
Discussion Notes
Previous Action Items
- Update documentation - DC Terms added 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)
- Make old proposal page a child of current proposal page as reference point / to mtn history (Val)
- 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 (Maureen)
- 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 (UNKNOWN)
...