You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Nov 26, 2013
We will use the international conference call dial-in. Please follow directions below.
- U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
- International toll free: http://www.readytalk.com/intl
- Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial in #
- Once on the call, enter participant code 2257295
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 | | - Identify any hard coded occurrence of a field, make configurable, retain the same initial value. Will allow us to get rid of hard coding while still keeping everyone on same metadata schema for now
- Example JIRA ticket:
- "Remove hard coded references to dc.title"
- Identify all hard coded occurrences of dc.title and replace them with values that can be stored and retrieved from dspace configuration files.
- After all hard coded fields are configurable, repository managers could more easily switch to a new schema by moving all the metadata to the fields in the new schema and changing the configuration.
- Example: after moving every title from dc.title to dcterms.title, the repo manager would only need to do a search & replace on dc.title in a centralized dspace configuration file.
- Could a tool be built for this step?
- Could start project by identifying the kind of tasks for fields that have the most prominent hard coding problems (title, author, dates, url, description...)
- Any problems with this approach?
|
25 | Impact of above approach on project phases: | | - Revised proposal as written: Proposed phased schemas
- do project phases change
- list of metadata implications - identify what needs to get cleaned up
- what tools would be helpful
- how could task & finish / review groups be helpful
|
5 min | Next steps - including next metadata team mtg | | |