Page History

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/Iryna Kuchma - eIFL.net

Elena Feinstein - University of North Carolina at Chapel Hill

Elin Stangeland - Cambridge University Library

Iryna Kuchma - eIFL.net

James Evans - Biomed Central/Open Repository

Jim Ottaviani - University of MichiganLeonie Hayes - University of Auckland

Maureen Walsh - The Ohio State University

Michael Guthrie - 

Sarah Molloy - Queen Mary, University of London

Sarah Shreeves - University of Illinois at Urbana-Champaign

Sue Kunda - Oregon State University

Valorie Hollister - DuraSpaceYan Han - University of Arizona Libraries

Guest Attendees

Sands Fish - MIT, 3.0 Release Team 

Time

• 10:00am Eastern/14:00 UTC

Dial-in

• (209) 647-1600, participant code 373133, host code: 560833 (can be done via Skype - for directions: https://wiki.duraspace.org/display/cmtygp/DCAT+Conference+Call+Dial-in). 
• Please note that we have been having lots of connectivity issues with the "freeconferencecallhd.2096471600" Skype dial-in lately. Generally you can get on, but Skype seems to boot you off at regular intervals. To avoid the frustration we recommend dialing in via a Skype phone call -- simply use the Skype dial pad and dial the USA # 209-647-1600 and then the conference code # as prompted. You will need to have a Skype account with money in it in order to place this kind of call -- and it will likely be about 3 cents a minute, depending on where you are calling from. We are looking for other solutions to the problem -- and also for your suggestions if you know of other solutions.

Discussion Topics

Actions from previous meeting

News & Events

1. Upcoming DCAT meeting dates: 
   
   1. November 13
   2. December 18 (conflict with original date of December 11)
   3. January 8, 2013
2. News 
   
   1. DuraSpace and SanDiego Supercomputer Center (SDSC) Partner to Provide Cost-Effective Cloud Storage and Preservation Services 
   2. Dell and University of Illinois at Urbana-Champaign Create Preservation Archive with Open Source Fedora Repository Software
   3. Last Chance to Become a DuraSpace Sponsor
   4. Help Define Levels for Digital Preservation: Request for Public Comments
   5. DuraCloud Helps to Ensure Future of World's Largest Archive of Social Science Data & Historic North Carolina Materials

...

2. Webinars/Podcasts/Courses:
   
   1. Upcoming
      
      1. Series Three: Get a Head on Your Repository with Hydra End-to-End Solutions - Sept/Oct 
      2. DuraCloud Brown Bag 

...

1. 1. 1. - Oct 31
   2. Gathering interest for future @mire webinars. Feel free to complete these surveys:
      
      1. Getting Started with DSpace
      2. DSpace 3.0 related topics 
   Webinars/Podcasts/Courses:
   
   1. Upcoming
      
      1. DuraCloud Brown Bag, September 26, 2012 
2. Events    
   
   1. ETD 2012PASIG in Peru, Sept 12-14 
   2. Fall 2012 Internet2 Member Mtg in Philadelphia, Sept 30-Oct 4, 
   3. iPRES 2012 in Toronto, Canada, Oct 1-5
   4. Dubin, Ireland, Oct 17-19
   5. Open Access Week Oct 22-28
   6. Euro Med 2012 in Lemesos, Cyprus Oct 29-Nov 3PASIG in Dubin, Ireland, Oct 17-19
   7. 2012 Digital Library Federation Forum in Denver, Colorado, Nov 4-5
   8. Berlin 10 Open Access in Stellenbosch, South Africa, Nov 6-8
   9. EDUCAUSE in Denver, Colorado, Nov 6-9
   10. Berlin 10 Open Access Conference in Stellenbosch, South Africa, Nov 6-8, 
   11. 6th International Conference on Metadata and Semantic Research in Cádiz, Spain, Nov 29-30
   12. Coalition for Networked Information Fall Membership Meeting in Washington DC Dec 10-11

Minutes

1)  News 

-no questions / comments

2) Action Items

-should reinforce DCAT interest DS-531 - Sarah P to follow up helix84

3) Updating Qualified Dublin Core 

Summary of discussion

1. Refining current DSpace DC according to 2005 QDC recommendations VS aiming for adding DCTERMS as a new schema

The  spreadsheet currently proposes the first approach. It's less intrusive and already helps to get closer to more uniformity. However, it seems like the DC community itself, with the DCTERMS namespace is already a bit further down a different path. 

Adding a new schema and making it optimal for people to convert/migrate existing metadata to this new schema might in the end make it less intrusive than performing changes to the current standard DC which might affect everyone. 

2. Definition of "locked" schema's 

We started off with the question whether a potential standard schema should be locked on either the element level, or as far as the qualifier level. 

Given the fact that DC allows extensions, it's my fear that if we don't allow people to add at least qualifiers, that we're being to severe. Therefor locking could mean that both standard elements and their qualifiers can't just be renamed or deleted from the user interface. 

In terms of the element level, there seemed to be consensus that elements in a "locked" schema should be added, removed or modified. 

3. Migration path 

The usecase of someone starting with a new installation of DSpace with a shiny new standardized namespace seems very different from existing DSpace users who might be confronted with a lot of migration efforts & pain. 

If we can't come up with a concept, either with or without help of the developers, to make migration painless & riskfree, there might be very little uptake (given that we would be able to get something in the code to start with). 

Therefor, it might be a good idea to investigate in detail how far the impact goes when we start changing things here. A very quick list could be: 

Any process that create new metadata in dspace

- submission forms

- spreadsheet importer

- command line import

- SWORD

- built in OAI-Harvester 

Any process that displays metadata in the web user interface

- item pages

- search, browse, DSpace discovery 

Any process that delivers the metadata (potentially via crosswalks) to other applications

- OAI server

- REST API

- ..

4) JIRA workflow - did not discuss

5) Overlap discussion

-check to see if developers need feedback on any features

6) Thurs/Fri discussion

News/info ?

• see helix84 email to DCAT list on the status of DS-531 and testing of unmerged issues 

2) Testathon help

• biggest changes in 3.0
  
  • Discovery changes - will be the default interface - regardless of using JSP or XML, although changes aren't identical there are common feature enhancements which will be documented
  • new version of OAI - should be backward comptable
• what features would be most helpful for DCAT to review?
  
  • Discovery - exercising all functions, try a bunch of searches or different passes through the interface - try to find specific content, exercising facets, noting any errors or behavior
  • documentation
    
    • check for completion, accuracy, - make note on JIRA ticket for that feature - or ask Tim Donohue for access to improve docs - flag problems
  • stats enhancements - (what is admin access on demo?)
  • "new features" and "improvements" on 3.0 Release Notes page
• how to / logistics
  
  • will start tomorrow or Thurs and run through Fri Oct 19
  • email out to the community, including instructions, links and demo DSpace account login and password 
  • backend changes can't be tested unless you download a test version yourself
  • if a new feature is confusing / don't understand it from the interface or documentation - then provide that feedback - ideally in the original JIRA issue or send an email to dspace-release@lists.sourceforge.net (Jim validated that this is what he usually does)
  • run through your (your team's) common tasks - make sure everything works as expected
  • Potentially getting general computer scientists involved from your institution (Amy says there is some discussion/intention about this at the University of Missouri)

3) Updating DC status

• Good discussion last month in DCAT mtg, but not much of an asynchronous follow up discussion - how can we best move this forward?
  
  • Amy: need to chat with cmtrs about limitations
  • Maureen: need more clarity of what direction we should go before taking w/cmtrs
  • Proposed process
    
    • 1) draft a proposal on updating DC from DC sub-team (Sarah P., Amy, Maureen, Maura)  - identify key areas to address for the update, identify proposed direction forward along with the benefits/drawbacks/outstanding questions for cmtrs and DCAT, should include:
      
      • Goal of update:
        
        • identify goal for the update - why is it important/why should it be done 
        • identify what specifically DSpace DC should be updated to - QDC vs DCTerms 
      • User Modifications: identify what if any modifications will be allowed 

      • Migration / Implementation: identify any areas/processes that will be affected (forms, imports/exports, etc.)

      • Other areas?
    • 2) hold targeted DCAT discussion - for December DCAT mtg have targeted discussion about the proposal - validating / revising DC sub-team's proposal - Val to poll DCAT to see if everyone is available on Dec 18 or if we need to re-schedule
    • 3) revise proposal based on DCAT discussion 
    • 4) discuss proposal with developers/cmtrs to understand limitations/pain points
    • 5) revise proposal based on developer/cmtrs feedback
    • 6) hold discussion / allow for feedback on proposal by DSpace community - and maybe the broader repository community

4) JIRA workflow improvements

• useful improvements that should make it easier to understand what needs to be done on JIRA issues
• more tweaks coming before implementing - more feedback welcomed (email Tim) - will discuss in detail at a later point

5) Topic for developer overlap mtg

• too early for DC discussion 
• priority for developers on 3.0 release, forgo overlap for Oct and possibly Nov unless something comes up

6) Topic for Thurs/Fri discussion

• nothing identified
• Val to contact each DCAT discussion leader to identify status on their issues on the 2013 DCAT Discussion Schedule

 -more on Updating Dublin Core 

Actions Items from this meeting