Versions Compared

Old Version 13

changes.mady.by.user Valorie Hollister

Saved on

compared with

New Version Current

changes.mady.by.user Valorie Hollister

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Table of Contents
outlinetrue
stylenone

DCAT meeting recording (recording was started a bit late -- so the review of some of the news is missing)

  1. News
    1. Welcome to our 9 8 new members! (full team)
      1. Augustine Gitonga - Aga Khan University Hospital
      2. Michael Guthrie - BioMed Central
      3. Dibyendra Hyoju - Madan Puraskar Pustakalaya/eIFL.net
      4. Iryna Kuchma - eIFL.net
      5. Sue Kunda - Oregon State University
      6. Bram Luyten - @mire
      7. Alice Platt - Southern New Hampshire University
      8. Imma Subirats - OEKC, FAO of the United Nations
      9. Ciarán Walsh - Enovation Solutions, Ltd
    2. DSpace 1.7.1 release - bug fix release (no new features, just resolves issues found in 1.7.0)
      1. resolves a medium-level security issue found in 1.7.0 (see DS-858)
      2. fully supports Oracle databases
      3. resolves several SWORD-related bugs 
      4. some other minor issues were resolved - for a full list, please see the 1.7.1 Release Notes and Version History
    3. DSpace 1.8
      1. target date for Oct 2011
      2. Robin Taylor - release coordinator
      3. what might be included: 1.8.0 Release Notes
      e-Forum
      1. need a co-moderator, ideally in Europe, Asia or Australia/NZ
      2. future topic suggestions?
        1. statistics (particularly, being able to share stats with users)
        2. copyright procedures (how do you research copyright for things you put in your repository?)
        3. citation management (is there a need to provide a way to pull out citations out of your repository?)
        4. upgrade process - how do you upgrade, testing, bringing in customizations
      3. other suggestions
        1. summary page on wiki - links to discussion on mailing list - give overview - w/Twitter & FB links
        2. links on Twitter and FB - when it starting/ending, during discussion highlight interesting issues/feedback/participation
        3. start discussion by providing something to react to - a use case, example, strawman proposal, etc.
          1. use a discussion forum that can link to Twitter, Facebook, etc - using Kunena and Jomsocial that integrate with Joomla which the dspace.org site is using as its CMS  (Michael Guthrie can help)
    4. Open Repositories Conference, June 8-11, 2011
      1. DSpace user group mtg chair, Holly Mercer
      2. DSpace committer mtg on Mon June 6, all DCAT invited to the mtg, planning a informal cocktail hour after
    5. Other news?
      1. OAI7 DSpace User Mtg on June 21 - sponsored by @mire & DuraSpace
      2. Nepal, Thailand and Laos -- how did the FAO DSpace training - eIFL.net provided DSpace 1.5.2 training in Laos in March go?
  2. New feature review process
    1. Goal: primary goal of the DSpace Community Advisory Team (DCAT) is to help review and facilitate community-wide discussions about new feature requests in JIRA and to provide support to the DSpace developer/committer group in producing software releases.
      1. What it is:
        1. group representing the community which make assessments about new feature requests in JIRA - the relative value and urgency for the broader community 
        2. facilitate community wide discussions on the most useful and urgent new feature requests - the purpose of which is to validate DCAT assessment, flesh out req'mts, most importantly-->find stakeholder/developer resources
        3. possibly provide communication support (announcements, etc.) to developers/committers for software releases
        4. collaborate on other projects for the community - user group mtgs, networking, mailing list participation, e-forum, attend weekly developer/committer mtgs
      2. What it is not:
        1. a group that dictates work priorities for the developers/committers
        2. having discussions just to have discussions
    2. Process overview
    3. Future discussion schedule
      1. - went well
      2. Sarah -- through Mortensen Ctr at Univ of Illinois she is going to Univ of Ghana in July to consult on repository policies, metadata, etc (not technical)
  4. e-Forum
    1. participation low in last e-Forum
      1. Val to talk w/Alice about next steps
    2. SPARC's new e-forum on "subject repository development and success"
      1. subject repos a unique need, without a lot of resources - not a direct overlap w/the DSpace e-forum
  5. DCAT new feature review process - please see last month's meeting notes
  6. Update on previously reviewed items
    1. DS587 tombstone (Sarah): discussion forum, JIRA
      1. Proposed next steps:
        1. Jim to have Jose add note in JIRA indicating whether or not authorization groups / access controls (Mark Woods points) are/is included in his current JSPUI patch
        2. Sarah to talk w/Tim about someone reviewing Jose's latest JSPUI patch and whether or not there is someone available to help Jose create the XMLUI patch
    2. DS638 check file format/virus check (Elin): discussion forum , JIRA - (https://wiki.duraspace.org/display/dsforum/DSpace+*+DS-638++check+files+on+input+for+viruses%2C+and+verify+file+format), JIRA
      1. Proposed next steps:
        1. Elin currently working w/Robin to understanding the curation framework
      ,
        1. and investigating/
      figure
        1. figuring out a next steps
          1. virus check - is part of MIT curation tools planned for 1.8 (some in 1.7 already)
          2. file format - Elin to f/u w/Robin, possibly look at UofM implementation (done many releases ago - before other curation work done)
    3. DS164 deposit interface for modifying input forms.xml (Jim): discussion forum, JIRA - Jim says it is ready for community wide discussion, he will schedule
      1. Proposed next steps:
        1. Jim to build a strawman approach to breakdown the different ideas for how to improve input forms -- including a clear proposal of priority for each w/input from DCAT
        2. get community's response and feedback on strawman
        3. determine who has done / will do which work (sounds like a lot of interested parties)
        4. determine the gaps - are their improvements that we don't have a developer for?
    4. DS560 XMLUI news config/front page customization (Bram): discussion forum, JIRA 
      1. Proposed next steps:
        1. DCAT vote and assessment
  7. Meeting Attendees:
    1.  Bram Luyten, Michael Guthrie Elin, Sarah, Val, Iryna Kuchma, Tim Donohue, Ciarán Walsh, Valorie Hollister, Elin Stangeland, Jim Ottaviani, Imma Subraits

NEXT MEETING ON APRIL 5MAY 3, 2011 AT 3PM/20:00 GMT