Page History

...

• 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

Attendees

• xBram Luyten (@mire) - @mire
• xElin Stangeland - University of Oslo
• xSarah Potvin - Texas A&M University
• xValorie Hollister - DuraSpacePedro?
• Sue Kunda

Discussion Items 

Discussion Notes

Panel Structure 

 1) Structure of the panel goal - see ) Introduction (5 min): VAL 

• Goal of discussion: discover what problems people care about - what

...

• needs need to be addressed by a DSpace metadata improvement project
• Summary of the metadata improvement project history
  • project spawned from a discussion during the committers mtg at OR10 in Austin at OR11 – committers requested that DCAT help to align current DSpace Dublin Core with current std
    
  • DCAT worked on the specific project over the last few years, outlining a detailed proposal for the community, gathering feedback, thinking through some of the implementation issues 
  • seems like a fairly arbitrary/narrow task – in looking at how DC stds have evolved in recent years it is clear that there are many
  10-15 min: introduction highlight WHO?
  • what the work has looked like so far - update dublin core stds in DSpace - seems like an abitrary or narrow task; actuality in looking at how DC stds have evolved looking at more complex metadata needs in the community
  • started in Austin committer mtg - commttters wanted to align DSpace dublin core with current std
  • part of the goal for the panel dicussion is to begin to broaden discussion w/community 
  • metadata std not performing the way we want it to even if DSpace was updated with the current version of DC, metadata stds in DSpace would not perform the way the community needs it to - many local workarounds, customizations and some real practical challenges 
  • as we look at D6 look more at our reqmtsthe future roadmap of DSpace, want to discuss reqmts for metadata
    • most basically and importantly is the challenge around flexibility - must have flexibility around:
      • 1) ingest - if material coming into DSpace is in different std, you
    challenge aroudn flexibity: 1) ingest (material in diff std,
    • • need to map so fields import correctly
    ),
    • • 2) exports / harvesting - metadata needs to be flexible enough to enable crosswalks for exports
    - for point out problems 
    • not just stdardize to current dublin core
    • adding new metadata standards
    • clean ingests / or exporting -
      • , harvesting
    or other purposes - metadata should be flex enought; 3) what you want to do w/in your own dspace - how easy is it to manage local needs - separate from import/export needs
    • • and other purposes
        • • if funders have asked for clean ingests / harvesting - more plug and play / easy to use
          • getting data in and out is very important for CRIS - ORCHID - ecosystem is much more complex - need to coordinate metadata on national level
         
      • dspace was built to be metadata agnostic - some fields are hard coded - like date 
      • • 3) local needs - needs to be easy to manage your metadata and content locally (i.e., not req'd to go into XML to make changes)
      • identify current challenges 
        • we don't just need to stdardize to current dublin core, need to add new metadata standards
        • clean ingests / or exporting
        • more easy to use - plug and play addtions/changes
          • creating separate namespace should be easy - for CRIS, etc. friendly metadata   
          • no hard coded fields (like date) - originally Dspace was built to be metadata agnostic 
        creating CRIS friendly metadata - creating separate namespace 
        • • creating custom fields - requires you to login to XML in order to do so or sometimes a Java programer to do and rebuild 
    • why we are having panel, what we want to get out of it
    • validate ideas/plans - not missing a reqmt from the community or reqmt by external standards

  2) Brief Panelist Self-Intro (5 min or less

  ...

  • specific examples of current challenges and some approaches/solutions
  • summary of problems all dealing with
  • set up to explain backgroud - how and why we are invovled in this panel - show audience which person they might most closely relate to 

  ): ELIN, BRAM, PEDRO, SARAH

  • each panelists introduces themselves and provides a brief summary of where they are from and what their interests are in metadata

  3) Panel Discussion

  • • In advance of panel discussion, panelists will develop a list of the key issues/challenges that DSpace needs to address to meet current (and maybe future) reqmts/needs
    • In advance of panel discussion, each panelist will select a specific issue/challenge that they would like to provide a brief specific example about to help spark discussion
    • Moderator will limit time for each discussion so that each panelists gets an opportunity to speak
    • List of challenges - what are the biggest metadata issues that need to be addressed on DSpace roadmap? what are the things you 'hack' or have work arounds (addressing an unmet need) for locally? what are the implications of workrounds? what should be taken in consideration with future DSpace - so that you don't lose your local customization? what mistakes have you made with DSpace metadata? what would you prefer to do differently? what/how far have you stretched the metadata in DSpace? 
      • • adapting metadata to meet external reqmts (OpenAIRE, etc.)
        • exporting metadata to diff schemas DC to METS
      • linked data

   

  Val to create a Google Doc for the panel to use to brainstorm: https://docs.google.com/a/fedora-commons.org/document/d/1x1xt5dq3NiYPVcdYPPPkj57cazJ_YSH4bgJk7IBFCBU/edit

  ...

  • how does this plan sync up or create conflicts with your current work?
  • linked data - what benefits are there in linked data?
  • how to serve common use cases - as everyone repositories evolve? 
  • how have people hacked DSpace to get it to do what they want - make sure current plan addresses some of those needs
    • linking articles and journals in DSpace, ability to define relationships
    • CRIS heiararchal metadata needs to be flattened in order to bring into DSpace
  • what are the priorities and more imminent problems to tackle 

   

   

  Notes on Metadata Panel from April 30 discussion 

  ...