...
- 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 Leadership Group, Steering Group
- also determined permanent working groups: DCAT (advisory group to SG, TPG, PPG), Technology Planning Group, Product Planning Group, Implementation Group
- roles to be formalized and
- membership not a reqmt to be on a working group
- chair of DCAT will sit as an exec officio member of the SG discussion
- DCAT has been asked to gather use cases from community by Sept, TPG only looked at use cases that came out from the survey
- what is DSpace going forward - anything on the table (3rd user interface? new architecture?)
- end to end functionality needs (no prescribe HOW something should be implemented – but identify what needs there are in the community)
- key areas: all of use cases around metadata and plans for metadata
- gathering use cases consistent with the recent vision that was developed - institutional repositories / open access / etc
- core use cases
- integration use cases
- agree on which prominent use cases will NOT be addressed by core DSpace
- 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 of DCAT to include the governance 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 thing sto the attendtion of SG - respond to requests and initiate discussions
- reqmts for DCAT membership shouldn't change - willingness to participate, DSpace membership not reqd
- DCAT represents the non-technical part of the community - acknolweeged that there is a difficulty in involving those from Asia/other time zones - how can we integerate DCAT charge - state minimum effort for engaging in DCAT topical discussions
- re-writing the DCAT charge by June 6
2) metmeta data panel
change to be more focused on use cases
mtg with panelists in advance, if we add another person
Action Items
- Val to send Doodle to reschedule metadata mtg: http://doodle.com/udfkbipwsqc7mza4#table
- Elin to send msg to Stuart to ask him to send a msg to Vision group - notifying them that it's work is done and a bit of info about roadmap group
- Sarah to send detailed Vision survey results to DCAT
- Metadata team needs to update draft mapping
- Metadata team - need to find someone who knows about metadata in Europe to sit on OR14 panel - possibly Jessica Lindholm?
-
Lilly Texas A&M has patch, will submit in the next few weeks.Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-570 -
Lilly has talked with Texas A&M developers, looking at if they can contributeJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1815 -
&Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1783
To be discussed at the next DCAT mtg: identify parameters - types of config changes that would be helpful - uploading input forms, changing themes, things that you can switch on/off, (not everything). DCAT look through config file for DSpace 4 and identify what would be most helpful to include. Elin will download 4.0 config file - DONE. Include discussion/question about JSPUI/XMLUI.Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1242