9am
Elin
Jim
Ronee
Val
3pm
Alvin
Sarah
Leonie
Beth
Val
News/Updates1) New list is published! http://www.dspace.org/whos-using-dspace/Repository-List.html
-feedback from developers on labeling semantics - reference to "addons" not accurate and confusing for developers -- and in general we the community needs to agree on terminology definitions (particularly the developers)-->Val set up wiki page for a terminology discussion (http://wiki.dspace.org/confluence/display/DSPACE/Terminology)
-Elin suggests that we have some of this discussion/education in the RM session at OR10
2) OR10 DSUG planning
-22 official submissions, a few late additions - most accepted
-combined DuraSpace mtg - DuraSpace planary, 2 tracks (mostly split along Fedora/DSpace lines), a repository manager session (per DGOC recommendations: how DSpace works, how you can get involved, batch metadata editing tutorial)
-still ironing out schedule details
-the host has indicated that all sessions should be video taped and available on line w/in a few days of the conference
3) Sponsorship program launch
-DuraSpace is looking for institutions to help sustain DuraSpace efforts - snail mail packet out next wk, press release/announcements, etc.
-please look for the brochure and encourage your library director to become a DuraSpace sponsor
4) DSpace wiki clean up
-migration complete, still a lot of clean up to be done (http://fedora-commons.org/confluence/display/DSPACE/DSpace+Confluence+Migration)
-need to work on plan / strategy - particularly as it relates to the intern from Univ of Toronto - June DGOC mtg
-everyone invited to fix things (links, etc.) as they come across them
5) 1.6.1 update
-Kim Sheppard is the release coordinator
-will be a bug fix release - 25ish bug fixes, submissions deadline is this Friday, beta release cut on May 21
6) 1.7.0 update
-moving to timed release schedule, meaning that major release will occur on a regular schedule established by the committers (once a year?), release date will be picked and adhered to
-no one has stepped forward to be the release coordinator - leaves great opportunity for DGOC and for the Community Advisory Team (CAT)
DGOC tactics on the 1.7.0 release process - what we can do in the vacuum with no release coordinator?
-volunteer from DGOC to help w/release - be on CAT: 1st step, work on community survey (1.6.0 and beyond: review on features, what do you think of 1.6.0? what features are still missing? want to improve DSpace, would like to know what the needs are, open text answers like for 1.6?), use survey in part as a communication/educational tool (full fledge embargo, item screen)
-DGOC brainstorming on release features - a) what would your institution like, and b) what do you think has broadest appeal in the community?
-registry update push: encourage everyone to update their info in the new DSpace registry list, particularly what version and UI (XML/Manakin or JSP and who is using machine based UIs: LNI, OAI-PMH, SWORD) update version on registry (committers want to figure out at what point can they can stop maintaining all of the UIs) *** Ronee: I can start working on this.
Check in on TO DOs/Follow up from April:
-Jim: what is the latest with the open access contract language (Univ of Michigan, MIT, Duke, Columbia, Harvard, Cal Dig Library, OhioLink): "should see daylight in the next (or the next after that) ARL
newsletter. It is draft language, so it's not something that we imagine every institution will adopt immediately, or without modification, when it comes time to negotiate with publishers. It's also model language, so individual circumstances will no doubt lead to further modifications. But it's what we think our authors should have, and we hope the spirit of the language will start to produce expectations in author rights that have not always been
-RELEASE PLANNING: See item #6.
TO DOs for this month:
1) volunteers for CAT team and/or helping create a community survey and public wiki pages (JIM, LEONIE?, ALL for brainstorming on survey)
-use this page to begin: http://groups.google.com/group/dspace-global-outreach-committee/web/community-survey---spring-2010
2) volunteer to start working on pushing the community to get their registry info updated (RONEE)
3) everyone to give their personal ideas of what features they'd like to see 1.7 (ALL)
-use this page: http://groups.google.com/group/dspace-global-outreach-committee/web/dgoc-ideas-for-1-7-or-other-future-releases
4) Val to find alternative conference vehicle for future mtgs - too much echoing on the line the last few months
