Versions Compared

Key

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

...

June 3 (date changed because of OR14)
July 8
August 12
September 9
October 14
November 11
December 9

Attendees

 

Discussion Items 

TimeItemWhoNotes
 1) Debrief on DSpace Steering Group mtgMaureen & Sarah
 2) Metadata panel at OR14Metadata team 
 3) JIRA discussion 
  • Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-1783
     & 
    Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyDS-1242
     
    • Identify parameters, types of config changes that would be helpful - uploading input forms, changing themes, things that you can switch on/off, (not everything).
    • Look through config file for DSpace 4 and identify what would be most helpful to include. Include discussion/question about JSPUI/XMLUI.
  • Pick other items to discuss: http://bit.ly/volunteer-details-needed


1) Debrief 1) Debrief on DSpace Steering Group Mtg

  • Maureen and Sarah attended SG mtg as part of the Tech Planning Group (group that took over work from Vision group - collected use cases that reflect feedback from survey)
  • SG mtg to talk through a plan for governance 
    • agreed on structure and what membership levels mean for governance 
    • determined who is is on will be in Leadership Group, Steering Group, etc.
    • also determined permanent working groups: DCAT (advisory group to SG, TPG, PPG) , Technology Planning Group (TPG), Product Planning Group (PPG), Implementation Group (IG)
      • roles to be formalized and  
      • membership not a reqmt to be on a working group - reqmts for DCAT membership shouldn't change - willingness to participate, DSpace membership not reqd
      • DCAT will serve as advisory group to SG, TPG, PPG, IG
      • chair of DCAT will sit as an exec ex officio member of the SG discussion
    • SG wants to hire project manager - who will chair PPG
    • Implications for development -  DSpace 5 will develop as normal - incremental changes/ad hoc changes contributed by individuals; but there will be a more directed process for DSpace 6 – with dedicated resources to work on directed development projects
    • SG also working on mission for DSpace - consistent with vision group work   
  • SG has made the following requests of DCAT for now
    • DCAT has been asked to gather use cases from community by Sept,  TPG currently the TPG only looked at use cases that came out from the survey
      • what is DSpace going forward - anything/everything on the table for consideration (do we need a 3rd user interface? brand new architecture?)
      • what are the end to end functionality needs (no prescribe prescribing HOW something should be implemented – but identify what needs there are in the community)
      • one of the key areas : all of use cases around metadata and plans for metadatawould be about metadata – identify use cases / how best to address metadata needs
      • use cases gathered should be gathering use cases consistent with the recent vision that was developed and agreed to - institutional repositories / open access / etc
      • what are core use cases integration cases vs. integration use cases
      • agree on which prominent use cases will NOT be addressed by core DSpace
        • i.e, not a collaboration tool for work in process / unfinished work (data or otherwise) 
    • project manager - to chair PPG 
    • DSpace 5 will develop as normal - incremental changes contributed ad hoc by individuals; but there will be a more directed process for DSpace 6 – with dedicated resources to work on directed development projects
    • SG also working on mission for DSpace - consistent with vision group work   
    • by OR14, rewrite the "charge" (mission/goal/activities) of DCAT to include the governance 

 

2) met

 

Action Items   

...

    • the governance - codify what is the charge of this working group
      • will DCAT be able to choose some of the work we do? yes, we should be able to help bring issues to the attention of SG - both respond to requests and initiate discussions 
      • DCAT represents the non-technical part of the community - acknowledged that there is a difficulty in involving those from Asia/other time zones - how can we integrate DCAT charge - state minimum effort for engaging in DCAT topical discussions 
      • get re-written charge finalized by May 30 and sent to SG, get SG feedback and finalize for OR by June 6
      • Bram has started Google doc for everyone to provide input onhttp://

...

...

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-570

...

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-1815

...

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-1783

...

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-1242

...

      • ly/dcat-charge
      • Val to send out Doodle for mtg week of 5/26 to discuss charge

 

2) Metadata panel at OR

  • Should we change focus to be more broadly about metadata use cases?
  • Should we have a mtg with panelists in advance? Yes, if we add another person to the panel
  • Val to send out Doodle to see if we can find time the week of June 2 to discuss - REVISION - propose we just use the next DCAT mtg on June 3 to discuss



Action Items