Potential Attendees
Amy Lana - University of Missouri
Augustine Gitonga - Aga Khan University Hospital
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.ne
Elena Feinstein - University of North Carolina at Chapel Hill
Elin Stangeland - Cambridge University Library
xIryna Kuchma - eIFL.net
James Evans - Biomed Central/Open Repository
xJim Ottaviani - University of Michigan
Leonie Hayes - University of Auckland
xMaureen Walsh - The Ohio State University
Roger Weaver - University of Missouri
Sarah Molloy - Queen Mary, University of London
xSarah Potvin - Texas A&M University
Sarah 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 | JIRA review
| Val, Jim |
| 3 | Metadata project
| Maureen, Sarah, Amy, Bram |
Discussion Notes/References
1) News
- Advanced DSpace training
2) JIRA review
- DS-1602 (Ivan/cmtr request fro DCAT input): Some metadata is not exported through OAI with oai_dc - "We'd love to hear comments from the DC standardization working group in DCAT about what is actually needed in this respect, in light of the proposed migrations. (Note: this will affect also other metadataPrefixes besides oai_dc, but DCAT doesn't have to worry about that.)"
- Elin: I think needs for OAI output on DC depends on the fields. It would be useful to see a list of the fields that are currently not included? If a list is not available, then a general fix that enables all DC fields to be exported would be preferred.
Ivan: I can tell you the list of all fields currently included. Fields not included would be those which have been locally defined and one intentionally excluded (dc.description.provenance) administrative field. If anything else is missing, it's an omission we should fix. Following Sarah Potvin's comment in Jira, I accepted the change. This was the actual change: https://github.com/DSpace/DSpace/pull/258/files. So you can see the current list of published oai_dc metadata (after the change) here: https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl. I'm not so familiar with the proposed set of metadata fields that should be in 4.0, so if any metadata field from 4.0 is missing in oai_dc.xsl (which is a mapping of DSpace metadata to oai_dc), we should add it
need to walk through it to make sure everything is included - Maureen to review and post
- DS-1204(Ivan/cmtr request fro DCAT input): Submissions page should display Workflow Tasks before Archived Submissions
- Elin: I don't know the xml UI very well, however this seems to indicate that you get a listing of submissions and archived submissions at the top (unlike the JSP UI). For users who submit a lot, I think this would get in the way so agree that a shift towards the bottom of the page would make sense.
- Tasks You Own
- Tasks in the Pool
- Unfinished Submissions
- Archived Submissions
- Submissions Being Reviewed
- not high priority
- Elin: I don't know the xml UI very well, however this seems to indicate that you get a listing of submissions and archived submissions at the top (unlike the JSP UI). For users who submit a lot, I think this would get in the way so agree that a shift towards the bottom of the page would make sense.
- DS-1453(Ivan/cmtr request fro DCAT input): repository content analysis - "This issue serves to collect requirements from repository managers and DCAT about what kinds of reports they would like to see in a proposed content analysis module. It has been often requested, but almost no requirements have been stated so far."
- if we had a content analysis module what reports would we like to see?
- Maureen has seen some content modules built outside of DSpace preso at OR - Terry Brady from Georgetown
- maybe do a survey of community - what people currently doing, what they think they need
- DCAT create a bucket list on JIRA issue, but how does it fit with other curation tasks
- DS- 824 (Jim Ottaviani, code review in process?): Request Copy function for XMLUI; would allow author of item to give viewing privs to restricted item
- code developed by Univ of Minho code - JSP, now XML working (at UofM)
- some support/need to allow for item to be in middle ground state of open and embargoed - someone can find it, but the bitstream not immediately available for download - alerts author that someone is interested in it, author can chose to have DSpace deliver a copy of it
- addresses institution limited access
- allows for posting of some journal versions of articles depending on how agreements are written
- turned on by invoking metadata in config - presence of values in fields triggers the action
- Jim would like to implement w/o improvements in Brian's comments (not automatically email file, create temporary group permission so file can be downloaded from DSpace in case files are really large), code for improvements not done
- Texas has something in test repository
- Sarah to ask at Texas, Jim to check w/Ivan
- Any others?
metadata
- project chunk - creating and implementing admin schema
propose regular mtg w/metadata mtg to move project forward
metadata stds and practices
Diane Hillman - asked about our proposal, email to confirm understanding of supporting DC and DCTerms, recommended to hat with Tom Baker at DCMI who might be able to help find other resources to help
DCMI conference will be in Austin in Oct 2014 - could use conference to get feedback on our project
Actions Items
Action Item | Assignee | Deadline |
|---|---|---|
1) Metadata project - prepping for review group
| Metadata team - Sarah P., Bram, Amy, Maureen | |
2) Metadata project - research / brainstorm on recruiting
| ALL | |
| 3) Contact metadata project volunteers to date to update them, ask for their feedback on review group idea | Val | |
| 4) DS-1583 Adopt interface translating by Translatewiki.net - no responses from mailing list email or comments on JIRA, TWN integration php code still needs to be reviewed. | Bram | |
5) Re-start JIRA reviews 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. c) Monthly discussion leaders should use the DCAT Discussion Forum to start your discussions with the rest of DCAT. d) Post links/updates to the JIRA issue (summary of DCAT discussion with links to forum, etc.). | ALL | |
