DSpace UI Criteria

Deliverable 3 of the working group is to create the criteria for evaluation of the pilots. Everyone is welcome to help draw up the criteria, if you would like to do so please contact the DSpace UI Working Group members or come along to the next meeting.

This page is a work in progress.

Tasks recommended to pilot evaluators

• Execute tasks on pilot server (all evaluators)
• Download and deploy pilot application (sys admin, developers)
• Add branding to pilot application (developers)
• Add custom feature/modification to pilot application (developer)

Functional Criteria

Evaluate how well the the pilot met the [link to pilot application expectations and requirements]. This section will be informed by the work of the pilot application expectations team.

Check on multiple browsers and devices in varying resolutions.

• Navigation
  • Browse hierarchy
  • Browse by facet
• Search
• View item page, including bitstreams
• Present edit page
• Login/Logout

UI Customization Criteria

The design of the pilot application is not intended to be a criteria for evaluation.

• Ability to rearrange application components on a page
• Ability to apply custom branding
• Complexity required to brand a site (with colours, logos, text)
• Complexity required to style a community/collection

Framework Criteria

• Deployment/build/configuration complexity
• Documentation/tutorial availability
• Ease of learning framework
• Simplicity of template/theme framework for non-developers (low barrier to entry)
• Size of framework community
• Perceived trajectory (growth) of framework community
• Ease of integration with core DSpace API

• Ability to run all of DSpace on one server
• Ease to add plugins for content types

Migration Criteria