...
- Why are we shipping DSpace with two UIs (JSPUI & XMLUI)? Are there any advantages to doing so?
- Should we consolidate into a single UI?
- If the answer to consolidation is "yes", what UI should we consolidate under? Should we just ship with the JSPUI? Should we just ship with the XMLUI? Or should we build a new, modern replacement UI and ship with that?
| Info | ||
|---|---|---|
| ||
These questions were also discussed during Day 2 of the 2015 DuraSpace Summit. The general consensus during those discussions was that we should consider consolidation into a single UI. The following slidedeck was presented during the discussions, detailing some of the breakdown of the current (as of March 2015) DSpace user base: http://www.slideshare.net/tdonohue/discussion-on-dspaces-two-uis-duraspace-summit-2015 |
Resources & Timeline
- Assuming we did decide to rebuild/rewrite one of our existing UIs, or even build a new UI, how would we get enough resources (i.e. developers) to do this in a timely manner?
- If we decided to revamp or build a new UI, the Committers can recommend that to DSpace Steering. Assuming Steering approves, they would ask the Leadership group to vote on the idea.
- If the Leadership group votes to approve the idea, then the Steering & Leadership would seek out the necessary resources to make this happen.
- As some of the institutions represented on Steering & Leadership have DSpace developers (or even Committers) on staff, the hope would be that they would donate some developer time to help achieve our goals in a timely manner.
- When would this happen? What is the timeline?
- There are NO set timelines for this decision as of yet. It's merely a brainstorm to get a sense of what the developers and Committers feel may be the best direction forward.
- Tim Donohue will be updating the Steering Group on this discussion as it progresses, and if any timelines are set, the entire community will be informed.
...