...
Attendees
xAmy Amy Lana - University of Missouri
Augustine Gitonga - Aga Khan University Hospital
xBram Bram Luyten - @mire
Bharat M. Chaudhari -@ School Of Petroleum Management, Gandhinagar, India
Ciará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
xElin Elin Stangeland - Cambridge University Library
xIryna Iryna Kuchma - eIFL.net
James Evans - Biomed Central/Open Repository
xJim Jim Ottaviani - University of Michigan
Leonie Hayes - University of Auckland
Maureen Walsh - The Ohio State University
Sarah Molloy - Queen Mary, University of London
Sarah Potvin - Texas A&M University
xSarah Shreeves - University of Illinois at Urbana-Champaign
Sue Kunda - Oregon State University
Valorie Hollister - DuraSpace
Yan Han - University of Arizona Libraries
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 | Debrief on Committer/DCAT mtg at OR13 (notes: https://wiki.duraspace.org/display/DSPACE/DevMtg+2013-07-08+-+OR13+Meeting) | Maureen, Sarah, Bram |
| 3 | Debrief on metadata improvements discussion at OR13 - next steps? MAUREEN, SARAH, BRAM - Please add ideas for next steps here based on the discussion Friday | Maureen, Sarah P., Bram, Amy |
| 4 | Anyone selected new JIRA issues? https://jira.duraspace.org/browse/DS#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel
| Val |
Discussion Notes/References
2) -Debrief on Committer/DCAT mtg at OR13
- when through requirement on
...
- SHARE proposal - whether they were easy/difficult to implement - not so far fetched and DSpace could be a good candidate -
...
- not so much discussion on DSpace 4 - most institutions are trying to sort out what can be done in time - uknown whether updates on SWORD interface, improved mobile access
...
- will be Dspace 3.2 out soon - bug fixes, security issue with JSP
...
- metadata improvements - cmtrs understand concept, general agreement that we need to do it, will be some pain points for upgrading
3)
Debrief on metadata improvements discussion at OR13 - next steps?
Notes from ValNext steps from Metadata discussion (from Val):
- embark on some educational webinars/resources
- community needs best practices of how to make metadata changes - where, how - to maximize interoperability and keep schemas pure
- community needs some education on what will happen after lockdown
- need to solicit specific help from community
- need DC expert to help with crosswalk
- need help determining what metadata, if anything, should be moved to the "admin schema"
- need help identifying and addressing the affected areas: input forms, item pages, browse pages
- need to develop/revise UI screens - agree what's included and create UI screens for other tasks
From Notes from Sarah:
- My sense from the two discussions of our metadata proposal at OR (Monday developer meeting and Friday community discussion) was that there is definite support for the proposal. There are also real challenges to implementation. One community member on Friday noted that the technical challenges around the proposal are evidence for the real need for its implementation— changes need to be made to metadata in Dspace that will smooth future transitions. Some other suggestions we heard focused on documentation, the need to make the addition of new schemas easier, the need for a standard namespace URI for a local schema, emphasis on using existing schema rather than inventing solutions (this came up in the discussion about the potential use of PREMIS in the to-be-developed admin schema), the possibly of a tool that would show how making a migration change in metadata might affect other operations like indexes, crosswalks, etc., steps for locking down DC, and the potential addition of a standard ETD-MS schema. I'll add these suggestions with more detail to the wiki.
General DCAT agreement that an education component of the metadata project could be helpful in getting people interested, Val start discussion/wiki page to brainstorm out ideas
4) New JIRA issues
Bram working on oneon DS-1583 : adopt the interface translation - to make translations easier - , Bram to publish msg to community to promote effort and seek input/help
Jira
Actions Items
Action Item | Assignee | Deadline | ||
|---|---|---|---|---|
1) Re-start JIRA reviews1 a) 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)
b) 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. 3c) Monthly discussion leaders should use the DCAT Discussion Forum to start your discussions with the rest of DCAT. 4d) Post links/updates to the JIRA issue (summary of DCAT discussion with links to forum, etc.). | ALL | Start discussion on the institutional profile for organizations that should be keenly interested in the metadata improvement project | Val to start | |
| 2) Develop next steps on metadata project - to get community involved, possible education component, start virtual discussion/wiki page | Val / ALL | |||
| 3) Publish to community to promote effort and seek input/help on working on DS-1583 to make translations easier | Bram | DONE |