Page History

...

Timeframe: 3rd and 4th Quarters of 2015. The UI platform will be selected before the end of 2015OR2016.

•  [August] Establish a DSpace UI Working Group, which will manage the process of establishing prototypes and helping us select a UI platform
•  [September] Establish UI piloting process / guidelines: see DSpace UI Prototype Challenge and announcement to all mailing lists
•  [September - NovemberDecember] : DSpace UI Prototype Challenge - Announce and run the Prototyping Challenge to test out a variety of UI platforms (ideally some non-Java and some Java-based)
  
  •  Each prototype much be kept transparent and public(on GitHub)
  •  Prototypes due by November 6 December 4
  •  Signup and full guidelines are at DSpace UI Prototype Challenge
•  [NovemberJanuary / February]  : The prototypes, their code, and initial notes/analysis will be made publicly available for community-wide feedback. See signup at DSpace UI Prototype Challenge
  
  •  Reviewed more formally by DSpace UI Working Group based on the DSpace UI Criteria
•  [DecemberMarch] Discussion of final candidates at DuraSpace Summit with Steering and Leadership groups
  
  •  DSpace UI Working Group Summary: https://docs.google.com/document/d/1bvJrRWEO2ZLTCLqNiaJ_KXGZKHNfXDjnqHWt_ZYGek4/edit
•  [April - June]  Extended prototype phase of an Angular 2 prototype as recommended at DuraSpace Summit. A team comprised of several institutions (Texas A&M, @mire, Cineca, DuraSpace) will collaborate on this prototype, and determine its plausibility (as a future UI)
  
•  [June / July] : A single UI platform will be selected from feedback and analysis of prototypes.  See OR16 presentation slides http://www.slideshare.net/tdonohue/introducing-the-new-dspace-user-interface
  
  •  The selection should be approved by Committers
  •  The selection should be approved by DCAT
  •  The selection must be approved by Steering Group
  •  The selection must be approved by Leadership Group

...

Timeframe: Organized development begins in January July 2016, and continues until 7.0 Release in late 20162017.

•  [December 2015July 2016] : Establish a development team (ideally with some overlap with the planning phase team). This team will likely consist of volunteer or "donated" development resources
  
•  [January July 2016 - May 2017] : Schedule a series of development "sprints" which will begin in early mid-2016. This will allow institutions to donate developers for specific sprints (or allow developers to balance local work with sprint work)
  
  •  Ideally, hold a "hackathon" to help kickstart some of these sprints and get everyone on the same page?
  •  Development process will be kept transparent (on GitHub) with ongoing status reports to Committers, etc.
    
  •  Ongoing "beta" or early releases will be made available for testing/feedback/analysis by developers and/or DCAT members
•  [June 20162017] : Early / Beta version of the new UI is presented at the OR2016 conference in Dublin. IdeallyOR2017. Ideally, we'd not only have a demo, but also a training session also hold training sessions on the new UI.
  
•  [Late 20162017] : Fully functional new UI in place for the DSpace 7.0 release (tentatively scheduled for Late 20162017).