DCAT Meeting Agenda September 10, 2013

1

News / announcements / events, etc.

• News
  
  • AVAILABLE: Sept. 2013 Issue of Library of Congress Digital Preservation Newsletter
  • CALL for Posters: Aligning National Approaches to Digital Preservation II (ANADPII), Barcelona
  • Webometrics institutional repository ranking July 2013 - by Bram from @mire
  • DSpace Committers Announce a December 2013 Release Date for DSpace 4.0
  • University of Namibia Scholarly Repository Boosts Research Visibility
  • Open Repository Welcomes First South American Institutional Repository Client
  • Office of Science and Technology Policy (OSTP) Releases Project Open Data Website
  • Fifty-six DSpace Repositories in India
  • New DSpace@MIT Look: In Support of One Million Downloads a Month
• Other Notes 
  
  • Sponsorship update - will be closing out 2013 campaign in October 
• Events
  
  • ETD 2013, Sept 23-26 in Hong Kong
  • EDUCASE Annual Conference, October 15-18 in Anaheim, California
  • Open Access Week, October 21-27
  • 2013 DLF Forum, November 4-6 in Austin, Texas
  • Fall 2013 CNI Membership Meeting, December 9-10 in Washington, D.C.
  • Open Repositories 2014, June 9-13 in Helsinki, Finland
• Other?
  •  

Val

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.)"

DS-1204 (Ivan/cmtr request fro DCAT input): Submissions page should display Workflow Tasks before Archived Submissions

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."

Metadata project

• Need DCAT input on metadata tools / ideas for tools
  
  • MetadataMapper tool - testing BEFORE Richard commits code? (in comments section Proposal to Update QDC Registry and Add DCTERMS Registry)
  • Web service add-on to remotely query and profile the metadata usage -  list all defined schema and within each schema, list all the defined metadata fields and how much they are used. Include the ability to 'harvest' these profiles from all participating sites, and combine the results (kind of like OAI-PMH harvesting) to get an aggregate picture of metadata usage. (in comments section Proposal to Update QDC Registry and Add DCTERMS Registry)
    
• Need DCAT input on process / next steps?
  
  • Starting with the following project chunks: https://wiki.duraspace.org/display/DSPACE/Phase+1+Project+Chunks
    
    • validate preliminary DC mapping
    • validate the phases/stagings - are all phases necessary/make sense: Proposal to Update QDC Registry and Add DCTERMS Registry
  • Metadata team to clear up DC mapping
  • Get more people/teams to review / refine mapping and project phases
  • Set up review group meetings (aka task & finish group)
• Volunteers/possible volunteers
  • Any good DC conference contacts (Sarah P?)
  • Jessica Lindholm from Univ of Malmo, Sweden metadata expert

Any 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

1) Metadata project - prepping for review group

• • fix references to preliminary mappings on proposal page - make easier to find?
  • add link to OR13 preso on proposal page
  • clean up the preliminary DC mapping

2) Metadata project - research / brainstorm on recruiting

• • look at other applications using DC - Omeka uses unqualified DC, others?
  • think about / ask others about who could participate in review groups

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)

• • 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.

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