1 / 20

DSpace Technology Roadmap (2015-16)

DSpace Technology Roadmap (2015-16). Tim Donohue, DuraSpace Tech Lead for DSpace tdonohue@duraspace.org. Roadmap Notes. Based on Use Case Analysis NOT rewriting DSpace from scratch Highly active Developer Community Centralized resources would be needed Time-consuming / potentially risky

ksheehan
Download Presentation

DSpace Technology Roadmap (2015-16)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DSpace Technology Roadmap(2015-16) Tim Donohue, DuraSpace Tech Lead for DSpace tdonohue@duraspace.org

  2. Roadmap Notes • Based on Use Case Analysis • NOT rewriting DSpace from scratch • Highly active Developer Community • Centralized resources would be needed • Time-consuming / potentially risky • ARE aiming for a leap forward in user experience / User Interface

  3. 2015-16 Roadmap(final draft)

  4. Roadmap Overview • 6.0 Release (2015) • 7.0 Release (2016) • Priority 1 • Priority 2 • Post-7.0 (2017 or later) • Integrations https://wiki.duraspace.org/display/DSPACE/RoadMap

  5. DSpace 6.0 • Late 2015 • A “bring us what you have” release • Like 5.0 (55 contributors) • Like 4.0 (59 contributors) • Like 3.0 (45 contributors) • 6.0 New Features should compliment the Roadmap • Refactoring code to support Roadmap

  6. DSpace 7.0 • Late 2016 / Early 2017 • Organized development towards prioritized roadmap features • More volunteers needed! • Community contributions still welcome • But, should align with Roadmap

  7. DSpace 7.0 – Priority 1 • Single User Interface • Configurations in Admin UI • “Module” Framework / Registry • Simplified Collection Hierarchy • Integrations to lower effort to deposit Highest priority for 7.0 (in order)

  8. DSpace 7.0 – Priority 2 • Hierarchical Metadata Support • Relationships between Objects • Enhanced, Basic Statistical Reports • Enhanced, Basic Preservation • Easy & Intuitive Deposit UI Recommended for 7.0, but contingent on contributors

  9. DSpace Post-7.0 Priorities • Easier Installation • Easier Upgrade • Advanced Statistical Reports • Theme Management in UI • Enhanced Versioning • Replace “Bundle” with Metadata • Advanced Preservation Tools • Enhanced Search/Browse • Enhanced Access Control

  10. Prioritized Integrations • Authentication / Authorization • Increased exposure in external systems • Additional persistent identifiers (e.g. DOI) • Enhanced personal identifiers (e.g. ORCID) • Streaming Video / Audio • Streaming Images / Documents • Search Engine Optimization Unscheduled as of yet. Dependent on higher priority features.

  11. How will we achieve this?

  12. How will we achieve this? • Managed projects (starting for 7.0) • Part time, donated developers • Scheduled (1-2 wk) development sprints • Need more volunteers / contributors! • Donate a developer part-time to help with a feature of interest • We’ll work with you to schedule dev for sprints

  13. “Signed Up” Contributors • @mire • Cineca • DuraSpace • University of Edinburgh • University of Illinois • IUPUI • Texas Digital Library • [your institution here]

  14. What comes first?

  15. Converge on Single UI DSpace UI JSPUI XMLUI

  16. DSpace UI • Prototype (at least) 2-3 UI platforms • At least one Java-based • At least one non-Java • By end of 2015 • Approve a single platform / prototype • Finalize developer team / schedule • Early 2016 : dev sprints begin • Demos / Early Training at OR16 • Release in 7.0

  17. Other 7.0 priorities • Projects will be established with a similar development model • 1-2 week development sprints • Open development (ongoing feedback) • The more collaborators, the more we can achieve for 7.0 • Conversely, if less, we achieve less

  18. How you can help • Become a DuraSpace Member! • Help us hire a DSpace Product Manager • Voice in DSpace governance & roadmap • Donate a developer (part time) • Choose a project • Get in touch • We’ll schedule sprints

  19. Q & A • Questions or concerns? • What do you like? • What is missing or prioritized too low? • What would you be willing to contribute to? http://tinyurl.com/dspacefeedback2015 Twitter hashtag: #dspaceplan

  20. Image Credits • Roadmap: https://flic.kr/p/6AX7aq • 6 bug: https://flic.kr/p/2pwJt3 • 7 dice: https://flic.kr/p/62EfXS • Priority: https://flic.kr/p/dGyfqe • Help wanted: http://www.vectorhq.com/psd/help-wanted-sign-psd-467881 • Futures: https://flic.kr/p/iU3qg9 • To Do: https://flic.kr/p/3f49wJ • Egg breakout: https://flic.kr/p/7TtEoY • Converging Road lines: https://flic.kr/p/59eZ2g • Simple UI: https://flic.kr/p/bDMn4

More Related