Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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

 

...

  1. Webinars/Podcasts/Courses:
    1. Upcoming
      1. Series Three: Get a Head on Your Repository with Hydra End-to-End Solutions

...

      1. - Sept/Oct 
      2. DuraCloud Brown Bag - Oct 31

 

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

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

    1. Coalition for Networked Information Fall Membership Meeting in Washington DC Dec 10-11

Minutes

 -more on Updating Dublin Core 

Actions Items from this meeting

...