...
In an effort to improve entry level user experience and make new users immediately productive, DuraSpace, the not-for-profit organization supporting the DSpace and Fedora technologies, proposes the creation of KnowledgeBase. KnowledgeBase would be a set of on-line materials modeled after the Ruby on Rail's RailGuides (http://guides.rubyonrails.org/) and would include screencasts, text-based guide, Powerpoint slides, and, if available links to relevant video/webinar. The resources in KnowledgeBase would be collaboratively developed by DuraSpace, our Registered Service Providersthe user community, developers, service providers, committers , developers and user communitiesand the DuraSpace organization.
What are the goals of KnowledgeBase?
- KnowledgeBase is a framework designed to make users immediately productive with either DSpace or Fedora and help users understand how to set up and run and repository using either technology.
- KnowledgeBase aims to provide a framework and encourage community collaboration to produce a set of tools that will improve entry level DSpace and Fedora user experience.
- KnowledgeBase will describe/display what a DSpace or Fedora repository is, what challenges they can solve and how to get started.
- KnowledgeBase is not a duplication or replacement for the official software documentation for either DSpace or Fedora. Rather, it is intended to be a supplemental resource, including dynamic content delivered through various methods (written text, screencasts, presentation slides, webinar recordings, etc.) which describe specific examples to make the material as accessible as possible.
What is the strategy
...
?
- Solicit feedback from the community on the value of KnowledgeBase
- Establish a framework for all forms of KnowledgeBase content
- Develop an outline / table of contents of proposed topics to include
- Develop sample content for a variety of delivery vehicles (text guide, screencast, etc.)
- Develop guidelines for content contributors - encourage bit sized contribution
- Create a proposed table of content outline and solicit feedback
- Create a unique wiki space
- Design content in such a way that contributions can be made in small sections (not necessary to contribute all delivery methods pieces on a given topic, contributions can be made as time/expertise is available -- i.e., if contributors can only provide a text-based guide on a topic that can be done without needing to contribute a screencast or slides)
- Create examples for each delivery vehicle: (a) Screencast, (b) Text-based Guide, (c) Powerpoint based
- Solicit and integrate feedback from the community about the framework
- Launch KnowledgeBase and solicit content contributions
- Develop a contributor processDevelop a contributor process
- all materials need to be reviewed/approved - ensure information is accurate, copy is permanently stored in a repository all contributors to sign license agreements - Apache 2 both ICLA (individual) and CCLA (corporate) licences, as well as Creative Commons on the content
What delivery tools are proposed?
...