These slides were presented as part of a breakout session at the DuraSpace 2015 Summit. See:
https://wiki.duraspace.org/display/DSP/2015+Membership+Summit+Meeting%2C+March+11-12%2C+2015
Since then, more discussion has taken place both on the DSpace wiki and within the DSpace Steering Group. See this DSpace wiki page for more details:
https://wiki.duraspace.org/display/DSPACE/Brainstorms+on+a+Future+UI
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
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.
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
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?