Versions Compared

Old Version 8

changes.mady.by.user Andrea Bollini (4Science)

Saved on

compared with

New Version Current

changes.mady.by.user Claire Knowles

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

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 with faceting
  • 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
  • Support for changes at runtime
  • Easy extendibility and support for not yet defined components (like Wordpress plugin, etc.)

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 file content types
  • Support for changes at runtime
  • Easy extendibility and support for not yet defined components (like Wordpress plugin, etc.)
  • Cluster support
  • Caching capability
  • Server load and throughput
  • Support for automatic testing

 

Migration Criteria

Not sure if we need to include criteria on the ease of adopting the new technology/migrate features from existing to new

  • Ability to support transiction to new URL if there are any changes at item, community, colllection or bitstream level

    • and is currently in draft format at https://docs.google.com/document/d/1FpJ3H9H7u9fjD6MC_UYmvyvGEjsrsa-l76jNkF1PdtQ/edit?usp=sharing