Page History
...
- Week of April 13
- Early (very rough) draft of Strategic Plan for Technology
- Analyze and prioritize "UI-related / End User" Use Cases : Use Case Analysis
- NOTE: DCAT meeting on Tues, April 14 - Top DSpace features & most important future UI needs
- Early (very rough) draft of Strategic Plan for Technology
- Week of April 20
- Analyze & prioritize "Administrative" Use Cases : Use Case Analysis
- Analyze & prioritize "Administrative" Use Cases : Use Case Analysis
- Week of April 27
- (Continued) A nalyze & prioritize "Administrative" Use Cases : Use Case Analysis
- NOTE: Tim will be traveling much of this week
- (Continued) A nalyze & prioritize "Administrative" Use Cases : Use Case Analysis
- Week of May 4
- Draft of Strategic Plan ready for initial review/feedback (by Steering, DCAT, Committers)
- NOTE: Steering Group meeting on Weds, May 6
- Initial Use Case Analysis is NOW COMPLETE
- Week of May 11
- Early (very rough) draft of Technical Roadmap begun
- NOTE: DCAT meeting on Tues, May 12
- Early (very rough) draft of Technical Roadmap begun
- Week of May 18
- Continuing enhancing Technical Roadmap
- Continuing enhancing Technical Roadmap
- Week of May 25
- Draft of Technical Roadmap ready for initial review/feedback (by Steering, DCAT, Committers)
- Draft of Technical Roadmap ready for initial review/feedback (by Steering, DCAT, Committers)
- Week of June 1
- Write OR15 Presentation of Strategic Plan and Technical Roadmap. Finalize the OR15 session details.
- Strategic Plan and Technical Roadmap are both ready for community feedback
- NOTE: Steering Group meeting on Weds, June 3
- Open Repositories 2015 (June 8-11)
- Presentation of Strategic Plan and rough draft of Technology Roadmap during the DSpace Interest Group sessions on Thurs, June 11.
- Presentation of Strategic Plan and rough draft of Technology Roadmap during the DSpace Interest Group sessions on Thurs, June 11.
Deliverables
- 3 year Strategic Plan for DSpace (for 2015-2018)
- DSpace 2015-18 Strategic Plan - Technology: Based on the 2013 Vision Document and the 2014 Product Plan work, a formal (3-5 year) Strategic Plan for the DSpace platform technology will be developed for discussion at OR15. This Strategic Plan for Technology will lay out action items we will take to achieve the goals laid out in these two founding documents
- DSpace 2015-18 Strategic Plan - Community
- DSpace 2015-18 Strategic Plan - Sustainability
- 1-2 year Technical Roadmap for DSpace
Other
- Use Cases : Continuing from the 2014 work, the DSpace Community Advisory Team (DCAT) hosted further meetings to gather community Use Cases and began prioritization of these use cases.
- Use Case Analysis : Analysis and prioritization of the gathered Use Cases.
- DSpace 2015-18 Strategic Plan - Technology (in process): Based on the 2013 Vision Document and the 2014 Product Plan work, a formal (3-5 year) Strategic Plan for the DSpace platform technology will be developed for discussion at OR15. This Strategic Plan for Technology will lay out action items we will take to achieve the goals laid out in these two founding documents
- As a reference point, the VIVO 2015-16 Strategic Plan: http://vivoweb.org/files/VIVOStrategicPlan20150210.pdf
- Technical Roadmap (coming soon): Based on the actions and goals laid out in the Strategic Plan, a short term (1-2 year) Technical Roadmap will be developed for discussion at OR15. This Technical Roadmap will detail specific, high-priority implementation projects (i.e. code/UI improvements) which will help the DSpace platform to move in the direction laid out by the Strategic Plan.
- Rough notes on what a Technical Roadmap may include, and a beginning of a DSpace SWOT Analysis: http://bit.ly/dspace2015-roadmap
- Overarching goals:
- We are NOT aiming for a from scratch rewrite. As we have a very active developer community on that existing codebase, and a from scratch rewrite would require major funding for such a large, well established platform.
- We are aiming at a substantial leap in improving the user experience and the web user interface.
- We are NOT aiming for a from scratch rewrite. As we have a very active developer community on that existing codebase, and a from scratch rewrite would require major funding for such a large, well established platform.
...
Overview
Content Tools