Discussion on DSpace's Two UIs : DuraSpace 2015 Summit
Download as PPT, PDF2 likes988 views
The document discusses the dual user interfaces (UIs) of DSpace, specifically the JSPUI and XMLUI, and their usage statistics across various countries. It highlights the outdated underlying codebases of both UIs and the challenges associated with maintaining two separate interfaces, including feature discrepancies and a lack of shared code. It poses questions about the future direction of DSpace, considering whether to converge into a single UI or continue with both.
Discussion on DSpace's Two UIs : DuraSpace 2015 Summit
- 1. Licensed under Creative Commons Attribution-Share Alike 3.0 Unported License DSpace has Two UIs: Should we converge? Tim Donohue DSpace Tech Lead tdonohue@duraspace.org 2015 DuraSpace Sponsor Summit
- 2. 2015 DSpace UI Usage • March 2015: crawled/searched for likely DSpace sites in.. – DSpace.org registry – OpenDOAR.org registry – ROAR.eprints.org Registry – OpenArchives.org OAI-PMH Registry – U of Illinois OAI-PMH Registry – Google (searches “unique” to DSpace) • Validated each site & deduplicated Scripts at: https://github.com/tdonohue/dspace-site-parser
- 3. Two UIs: Global Adoption NOTE: While each site URL was unique, it’s possible multiple URLs could point to the same DSpace installation.
- 4. JSPUI Locations Largest by country: Japan (127), USA (79), Brazil (60), Taiwan (58), India (55)
- 5. XMLUI Locations Largest by country: USA (255), Turkey (58), Norway (45), Spain (44), Brazil (43)
- 6. JSPUI Version Distribution ~30% (300) of JSPUI users are “up-to-date” (3.x, 4.x, 5.x)
- 7. XMLUI Version Distribution ~60% (537) of XMLUI users are “up-to-date” (3.x, 4.x, 5.x)
- 8. JSPUI vs XMLUI • JSPUI – Underlying codebase is 12.5 years old – Modern (Bootstrap) theme in 4.0 • XMLUI – Underlying codebase is 7 years old – UI based on a (nearly) obsolete platform (Apache Cocoon) – Modern (Bootstrap) theme in 5.0
- 9. Two Platforms in One • Committers rarely work on both UIs – Neither UI gets “full attention” • Very little of UI codebase is “shared” • Features come out in one UI first, get “ported” to the other later – UI feature lists are hard to track / document
- 10. Two UIs: Committer Split
- 11. Where do we go from here? • One UI or keep two UIs? • What is of interest to you in a UI? (use cases / features / needs) • What do we keep? What can we do better? • What would your ideal UI look like?