Welcome to the second meeting of the DSpace UI working group.
The purpose of the Working Group is to evaluate the technology for a new DSpace UI.
Will be meeting regularly (weekly or fortnightly) over the next 3 months.
Assumptions:
That the Working Group will invite volunteers to develop short pilot UI prototypes with similar features and functionality.
The Working Group will evaluate the prototypes.
Members of the Working Group can also be involved in the development of prototypes.
Two teams were established at the first meeting:
One team to establish the UI Prototype criteria for development.
The second to establish the criteria for judging the prototypes.
Committers and other interested parties will be asked for feedback by the Working Group so a recommendation can be made to the DSpace Steering Group on which technology should be chosen for the new DSpace UI. The Steering Group will make this decision as it is a strategic decision for the future of DSpace.
Discussion on the different use cases for the UI e.g. use for Library search tools, publication lists etc.
Action: Personas should be documented for the implementation of the new UI.
Currently the development of criteria for deliverable 2 is focusing on he scope of the prototypes to enable comparisons of the technology and not the design. Want to be able to compare like for like.
Update from the team for deliverable 2 - UI Prototype criteria for development - Lieven Droogmans
Lieven discussed the document currently being written to establish the requirements for the prototypes, noting that:
It is hard to separate criteria for the development to the criteria for judging.
The document is to allow the builders of prototypes to know what they need to cover in the development.
The focus is on the UI not the link with the core DSpace API. Therefore the prototypes should emulate the look and feel of the existing XMLUI Mirage 2.
Due to time limit of 80 hours development, features can be mocked-up or wireframes can be submitted.
Group discussed whether the UI prototypes should be confined to use of the REST API. It was decided this should not be the case but prototypes do need to use an API to utilise the DSpace Core code.
Pass on to the criteria for judging, technology selected needs to be one that Universities can recruit developers to use.
Scope:
Focus on key interactions/requirements within DSpace:
Item View
Navigation to an item
Browsing collection
Authentication and authorisation
A form for editing
General requirements:
Footer and header
Breadcrumb
Navigation
Should be within a web browser
Responsive (work on screens of all sizes)
Important features to be documented but not developed:
Internationalisation
Theming
Authentication methods
Modularisation:
To be demonstrated through a branch of the prototype. One mandatory requirement and one of four optional requirements must be implemented to demonstrate how the prototype can be modified for customisations.
**The development of prototypes is not a design challenge, it is to show existing features in a new technology**
Volunteers will be required to install the prototypes: Claire K and Tim D volunteered, more needed please. Installation instructions will need to be included in the public Github repository for the prototypes.
Action items
Amanda French to format the UI Prototype requirements and pass to DL2 Group and Tim.
Claire Knowles to put the DL3 criteria in Google Doc and link to it from the wiki page.
ALL please add to the document via comments
DL2 Group add to the document that the code needs to be in an open Github repository.
DL2 Group add to the document that installation instructions need to be included in the Github repository README.
DL3 Group include ease of installation
DL3 include technology selected needs to be one that Universities can recruit developers to use.
New members please contact Tim D if you wish to be included as a Working Group member.