Attendees
Bram Luyten - @mire
Ciarán Walsh - Enovation Solutions, Ltd
Iryna Kuchma - eIFL.net
Jim Ottaviani - University of Michigan
Maureen Walsh - The Ohio State University
Sarah Potvin - Texas A&M University
Sarah Shreeves - University of Illinois at Urbana-Champaign
Sue Kunda - Oregon State University
Valorie Hollister - DuraSpace
Time
- 10:00am Eastern/14:00 UTC
Dial-in
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
Discussion Topics
| Topic | Discussion leader |
|---|
1 | News / announcements / events, etc. | Val |
| 2 | Metadata improvements discussion at OAI8 Repository manager session next week - feedback on slides Bram emailed | Bram/Iryna |
| 3 | Metadata improvements discussion at OR on Friday, July 12 - need any help with approach? strategize some discussion starter questions? | Metadata Sub-Team: Sarah P., Amy, Maureen |
| 4 | Any discussion topic ideas for Committer/DCAT mtg? - metadata improvements
- discuss overlap mtgs/joint mtgs - whether to pursue or not
| Val |
| 5 | Anyone selected new JIRA issues? https://jira.duraspace.org/browse/DS#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel - "More Details Needed" - Try to ask relevant questions in the comments, poking the original submitter to provide more detail
- "Volunteer Needed" - These are issues waiting for a volunteer. You can put some of these tickets in the spotlight by commenting or +1 on them to indicate that they are really important to you.
- "Received" - Help to judge whether the incoming tickets contain enough detail
| Val |
Discussion Notes/References
3) Metadata improvements discussion at OR
- how to lead discussion / how to get people to talk
- want one revolution or 2
- how inconvenient will this be
- propose senarios for lockdown - maybe just element and qualifier - what it would look like, what it would mean, what would you do?
- have an anonomous repository - show example of what the impact would be
- lockdown on element level only to begin with
- some people really don't understand how it will affect them, what a repo mgr would have to do with the deal with changes
- what are we looking for out of the discussion
- feedback to move forward
- need dev volunteers to move forward
- help in figuring out how we are going to do it
- identify more specifics to project - w/hours estimate - features rely on metadata get cleaned up (might not be approriate for them the be relying on metadata)
- locking it down in UI for element level to begin with, later for qualifier level
- identifying necessary tools for migration – or ok to plan manually migration for now
- don't really want feedback on proposal - more about gettiing them familar with some of the challenges – DCAT proposal to work on key challenges
- 3 key challenges
- not metadata for bitstreams
- validation
- increase costs/mtn because not fully DC compliant
- OR discussion
- start with brief overview
- identify senarios
- identify specific project components
Actions Items
Action Item | Assignee | Deadline |
|---|
| Check on finding time slot for a discussion metadata improvement proposal at both DSUG OR13 and OAI8 DSUG | Val, Bram/Iryna | DONE |
Re-start JIRA reviews 1) Everyone should select a JIRA issue of interest (Bram's recommended view: https://jira.duraspace.org/browse/DS#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel) - Received: help to judge whether the incoming tickets contain enough detail
- More details needed: try to ask relevant questions in the comments, poking the original submitter to provide more detail
- Volunteer needed: There are today 155 issues waiting for a volunteer. You can put some of these tickets in the spotlight by commenting or +1 on them to indicate that they are really important to you.
2) If the issue you select merits DCAT discussion (you want to confirm the importance of the request, want input on request, want to propose DCAT sending a msg to the listserve to find volunteers, etc.) please schedule the month for which you'd like to hold the discussion on the 2013 DCAT Discussion Schedule. If your JIRA issue doesn't merit a DCAT discussion, use JIRA to follow up directly. 3) Monthly discussion leaders should use the DCAT Discussion Forum to start your discussions with the rest of DCAT. 4) Post links/updates to the JIRA issue (summary of DCAT discussion with links to forum, etc.). | ALL | |
| Create (provocative) questions for community discussions - including brief description of what is planned and potential implications | Metadata Sub-Team: Sarah P., Amy, Maureen | |
| Start discussion on the institutional profile for organizations that should be keenly interested in the metadata improvement project | Val to start | |