The Future of DSpace Jonathan Markow Dura Space

  • Slides: 10
Download presentation
The Future of DSpace Jonathan Markow, Dura. Space Tim Donohue, Dura. Space Lieven Droogmans,

The Future of DSpace Jonathan Markow, Dura. Space Tim Donohue, Dura. Space Lieven Droogmans, @mire Debra Hanken Kurtz, Texas Digital Library Licensed under Creative Commons Attribution-Share. Alike 4. 0 International License

Reminder: Vision DSpace will: 1. Focus on IR fundamentals, modern use cases 2. Be

Reminder: Vision DSpace will: 1. Focus on IR fundamentals, modern use cases 2. Be lean & flexible 3. Include “core IR” functionality which can be extended 4. Be designed to integrate well 5. Support low-cost, hosted solutions

Survey Analysis & Planning

Survey Analysis & Planning

Draft Product Plan(ning) • Team: 6 Committers & DCAT • Analysis: DSpace Vision Survey

Draft Product Plan(ning) • Team: 6 Committers & DCAT • Analysis: DSpace Vision Survey “features importance ranking” – Feature categorization – Rough draft of use cases – Where do we stand on popular features? • “Non-Functional” platform goals http: //tinyurl. com/dspaceplan

Survey Feature Gaps By Average Ranking ALL FEATURES (34 total) Very Highly Ranked (19

Survey Feature Gaps By Average Ranking ALL FEATURES (34 total) Very Highly Ranked (19 features) >7. 5 avg out of 10 NOTE: Survey purposefully listed features & needs which we knew were not yet met. Moderately High (15 features) 5. 0 -7. 5 avg out of 10 Mostly Met Partially Met Not Met

Highly Ranked Gaps… • 4 most highly ranked, unmet needs: – Batch upload via

Highly Ranked Gaps… • 4 most highly ranked, unmet needs: – Batch upload via UI – Relationships between objects* – Configuration via Admin UI – Template driven UI for easy branding Very Highly Ranked (19 features)

Structural/Arch (7 features) Survey Feature Gaps by Category End User UI (9 features) Stats/Metrics

Structural/Arch (7 features) Survey Feature Gaps by Category End User UI (9 features) Stats/Metrics (4 features) Admin UI (7 features) Integrations (7 features)

Non-Functional Goals • DSpace should strive to: – Be Easy to Install – Be

Non-Functional Goals • DSpace should strive to: – Be Easy to Install – Be Easy to Upgrade – Be Scalable and have Good Performance – Be Attractive to New Developers – Be Attractive to New Repo Mgrs – Avoid maintaining duplicative codebases Group felt these are important in maintaining a sustainable community product

Likely Project Scope • Need *single* UI and to decrease duplicative code / functions

Likely Project Scope • Need *single* UI and to decrease duplicative code / functions – Current maintenance effort is high – Ongoing development effort is double • Refactoring or rebuilding of codebase – Codebase & architecture is aging, needs cleanup / enhancement – Again, decrease duplicative code

Group Recommendations • Our “organic” development model is not good for significant work •

Group Recommendations • Our “organic” development model is not good for significant work • Organized/funded project needed – Hire a Product Manager – Full time Tech Lead • Model to make Product decisions • Process to achieve our Product goals