Download presentation
Presentation is loading. Please wait.
Published byBrandon Gilmore Modified over 9 years ago
1
Licensed under Creative Commons Attribution-ShareAlike 4.0 International License The Future of DSpace Jonathan Markow, DuraSpace Tim Donohue, DuraSpace Lieven Droogmans, @mire Debra Hanken Kurtz, Texas Digital Library
2
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
3
Survey Analysis & Planning
4
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
5
Survey Feature Gaps By Average Ranking Mostly Met Partially Met Not Met ALL FEATURES (34 total) Very Highly Ranked (19 features) Moderately High (15 features) >7.5 avg out of 10 NOTE: Survey purposefully listed features & needs which we knew were not yet met. 5.0-7.5 avg out of 10
6
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)
7
Structural/Arch (7 features) Stats/Metrics (4 features) End User UI (9 features) Admin UI (7 features) Integrations (7 features) Survey Feature Gaps by Category
8
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
9
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
10
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
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.