Page History
...
- End User Use Cases
- Admin UI Use Cases
- Prototyping a Future UI
- Brainstorms on a Future UI(includes some notes on possible platforms for a UI)
Planning Phase - Selecting a Platform
...
- Establish one or more team(s) to prototype potential platforms for a UI. These team(s) will likely consist of volunteer or "donated" development resources
- [Late July?] (date TBD) : Prototyping a Future UI - Begin prototyping at least 2-3 different UI platforms. (Recommended that at least one of the prototyped UI platforms is Java-based, and at least one is non-Java based. Some possible options include those mentioned on Brainstorms on a Future UI))
- This early prototyping may be less structured, allowing teams to work at their own pace (within the given requirements and deadlines)
- A standard prototype will be defined in terms of simple feature sets it should try to achieve (e.g. be able to display an existing DSpace hierarchy, providing browse, search and basic editing capabilities). All prototypes will be scoped such that they are achievable in a short amount of time (i.e. weeks, ideally not months), in smaller teams.
- Each platform should also be analyzed for how we might achieve other UI features on the RoadMap (e.g. configs in Admin UI, easy theming, etc) which are not within the scope of the prototype
- Each prototype much be kept transparent (on GitHub)
- [October] (date TBD) : The prototypes, their code, and initial notes/analysis will be made publicly available for community-wide feedback
- Reviewed more formally by Committers (and optionally DCAT members)
- [December] : A single UI platform will be selected from feedback and analysis of prototypes
- The selection must 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
...
Overview
Content Tools