- short link to this page: TODO
Date & Time
- January 12 16:00 UTC/GMT - 11:00 EST
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
Agenda
RIOXX Application profile: UK only or wider interest?
RIOXX (http://www.rioxx.net) is an emerging standard for Open Access repositories, largely driven by Funder OA Compliance requirements and built in collaboration with UK institutions.
Code and documentation to add support for RIOXX to your DSpace is already available today: https://github.com/atmire/RIOXX/ as UK institutions need to be compliant by April 2016.
Interest in this application profile has already been expressed by non-UK institutions. A JIRA entry has been created to see if it's possible to add support for RIOXX in the DSpace core:
Bram Luyten (Atmire) will give a short demonstration to show what the implications are on the DSpace submission forms and metadata schema through: https://join.me/atmire_meeting
Participants are invited to share from their national and institutional context if the RIOXX profile (or selected fields) makes sense for them. Everyone is invited to think about the issues that could occur if the profile would be merged into the DSpace core, which would already have 2 concrete implications:
- Do we want to preserve DSpace's default list for dc.type? Should we enable both the DSpace dc.type vocabulary as well as the RIOXX one (which might be confusing for submitters).
- DSpace has a free text field for bitstream descriptions, while RIOXX has a controlled vocabulary. Should we keep and offer both?
- RIOXX is very explicit about the fact that the metadata should correspond with a single file. However, dspace offers uploading of multiple files in one item. The Atmire patch addresses this by using the "primary" bitstream, as the file that is relevant for RIOXX. In this way, both approaches are compatible but it's worth discussing if someone feels different.
Other topics
- DSpace 6 Testathon preparation:
- Update from DCAT's DSpace 6 Testathon Testplan Working group
- Update on the UI Working Group
Preparing for the call
RIOXX
- Explore the application profile at http://rioxx.net/v2-0-final/ and compare how it is mapped in DSpace with the Atmire patch: https://github.com/atmire/RIOXX/#General-DSpace-RIOXXTERMS
- Because the RIOXX implementation relies on the DSpace ORCID feature, it's useful to review last month's notes on ORCID.
XMLUI Test plan for DSpace 6 Testathon
Even though we have a LOT of tests already, we are still no where near "full coverage" of the DSpace featureset. If you think of a feature that is not covered by the test plan, please add your tests in the plan OR add them in the comments below so someone else can add them.
- Review the DSpace 6 Testathon Testplan Working group page
- Review the draft of the XMLUI Test plan (everyone can view, if you want to help out, hit the button on the top right corner to request edit rights)
Meeting notes
...
Call Attendees
- Bram Luyten - @mire
- Ignace Deroost - @mire
- Maureen Walsh - Ohio State University
- Sarah Middle - University of Cambridge
- Claire Knowles - University of Edinburgh (may be a little late)
- Andrew McLean - Imperial College London
- Jonathan Green - University of Nottingham
