...
Discussion Items
Time | Item | Who | Notes |
---|---|---|---|
5 min | 1) Review proposed agenda - add/change as necessary | Val | |
10 min | 2) Opportunity to include anything about recently included dcterms schema and other recommendations in documentation
| Bram |
|
15 min | 3) Non-intrusive approach to modifying hard-coded metadata values via JIRA tickets |
| |
25 | 4) Impact of above approach on project phases: |
| |
5 min | 5) Next steps - including next metadata team mtg |
Discussion Notes
2) additions to 4.0 docs
-create concise list of fields in docs you can't delete because it affects functionality - either hardcoded or used for admin
-best practices for date field
-Maureen: needs to be in - not sure about whether it belongs on the Metadata Recommendations page
-Bram: could add brief explanation about what the plan is (sep metadata schemas for admin, etc.)
-start list on wiki, with examples, ask for dev and community input, then figure out what we could move to Metadata Rec
-Bram to create JIRA tkt - list of fields that are hardcoded that functionality would be affected, Bram to email metadata team with ?s
-create JIRA tkts to isolate hard coded fields to make them configurable - Bram to start page
-Maureen: include/change field scope notes, DC XML comments "used by system, do not remove"
-date issued field - need scope notes about leaving blank? implications for Discovery - not included in browse indexes
-Monica - negative dates
-Sarah - date ranges
-Maureen: very constrained on what you can put in dc.date,
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)