...
Amy Lana - University of Missouri
Augustine Gitonga - Aga Khan University Hospital
Bram xBram Luyten - @mire
Bharat M. Chaudhari -@ School Of Petroleum Management, Gandhinagar, India
Ciarán xCiarán Walsh - Enovation Solutions, Ltd
Claire Bundy - BioMed Central
Dibyendra Hyoju - Madan Puraskar Pustakalaya/eIFL.net
Elena Feinstein - University of North Carolina at Chapel Hill
Elin Stangeland - Cambridge University Library
Iryna xIryna Kuchma - eIFL.net
James Evans - Biomed Central/Open Repository
Jim xJim Ottaviani - University of Michigan
Leonie Hayes - University of Auckland
Maureen xMaureen Walsh - The Ohio State University
Sarah Molloy - Queen Mary, University of London
Sarah xSarah Potvin - Texas A&M University
Sarah xSarah Shreeves - University of Illinois at Urbana-Champaign
Sue xSue Kunda - Oregon State University
Valorie xValorie Hollister - DuraSpace
Yan Han - University of Arizona Libraries
...
Discussion Notes/References
3)
one revolution or 2 -
how inconvineent 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
Sue Kunda - really don't understand how it will affect us
what a repo mgr would have to do with the deal with changes
feedback to move forward
need dev volunteers to move forward
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
tools for migration? or manually for now
brief overview
senarios
specific project components
---
DCTERMS migration
2) 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
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)
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 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 |