...
Thursday, March 14, morning sessions
DSpace Session
Initial Discussion Questions:
- What does the project need to be successful?
- financial contributions
- developer contributions
- articulation of requirements
- How to increase engagement with the community?
- new models of funding (membership?)
- stronger project governance?
- other forms of communication?
Main challenges group discussion identified:
- No roadmap.
- Committers are more maintainers.
- Started focus groups, but still not a roadmap.
Is the roadmap / increased functionality a pressing issue?
Greatest needs in the community:
- 1) Need a roadmap - need a vision of what DSpace should be in the next 3 to 5 years
- 2) Need governance for stakeholders to go along with additional funding and long term roadmap
- DSpace Futures discussions
- what does project need to be successful
- who wants something enough so that they will put something in to make it happen? (developer resources/funding)
- DSpace Futures came down to three main pointsprojects
- hope was that DSpace futures would turn into something like Fedora Futuresturned , turned into other smaller functionality projects, not necessarily a roadmap
- REST API
- DSpace + Hydra
- Metadata Improvements
- not a lot of people very many volunteers so far
- hope was that DSpace futures would turn into something like Fedora Futuresturned , turned into other smaller functionality projects, not necessarily a roadmap
- Fedora folks may have more developer resources, many DSpace institutions may not have developer resources
- How do we energize the DSpace community?
- Is DSpace a product or project?
- no sense of DSpace user's community
- should be more of a push to develop a DSpace user community more at conferences - set up BoF at your next conference
- more participation in DCAT and ambassador group
- centralized resources going through users
- How to get more participation in DCAT?
- DuraSpace suggesting how this could work
- e.g., set up BoF at your next conference
- need to have a vision of what DSpace will be in the next 5 - 10 years
- how to figure out
- what if DSpace becomes a Hydra-head?
- DSpace is not an enterprise-level system
- if you had a clear migration path, then you might get funding
- Are there any projects already close to DSpace on Fedora?
- analysis hasn't been done yet
- scholarSphere (PSU) and hydris (Stanford)
- lot of interest in creating DSpace hydra-head
- analysis hasn't been done yet
- need specifics to ask for money
- need community to be in charge of what changes need to be made, actionable items and identify people charged with doing it
- have a membershiop model for smaller institutions to fund DSpace improvements
- tying a deliverable to $$
- Fedora 4 will still not be an out-of-the box system until UI is on there
- DSpace could be UI that sits on top of Fedora
- Committers are busy with bug fixes, releases and reviewing the many contributions – making sure they play well together - don't really have time to focus on the evolution of DSpace architecture and long term road map
- Started DSpace Future focus groups w/small projects, but still not a long term roadmap
- should this include Hydra Head or some other type of Fedora integration?
- not an enterprise system, doesn't scale
- DSpace-like Hydra head: scholarSphere (PSU) and hydris (Stanford)
- is it a grant project to merge DSpace with Fedora?
- DuraSpace should scope the project
- need specifics on what needs to be done/how to contribute
- Issues
- Roadmap
- includes migration to Fedora
- energizing the user community
- need specifics to ask for development money
- need community to specify what needs to be done
- everyone looking at DuraSpace to create roadmap, but DuraSpace wants community to lead
- DSpace community
- maybe different funding model, e.g., membership
- tie requisition to deliverable
- adoption, patch, upgrade
- "bill me"
- size of institution
- maybe different funding model, e.g., membership
- Roadmap
...