UI Rewrite for Hydra-Head

WARNING: This content has been deprecated!

Please browse or search the main wiki for more up-to-date content.

This page is intended to show the work involved in the UI rewrite of the hydra-head plugin.

This work is being done by Joe Gilbert (UVa), Jessie Keck (Stanford), Julie Meloni (UVa) and Naomi Dushay (Stanford)

Work By Active-Fedora Model, by Page/Action

AF Model

fixture object

page/action

UI design

html only

tests:
html5 valid, etc.

basic js

full AJAX

mods_asset

(tick)

search results

 

 

html5 valid

 

 

 

 

create/edit

(html only)

(tick)

html5 valid

 

 

 

 

view

 

 

html5 valid

 

 

 

 

delete

 

 

 

 

 

file_asset

(tick)

listed in an object

 

 

(test currently in file_assets_list)

 

 

 

 

create/edit

 

 

(tests in file_upload;
file_asset_creation page and edit_document page)

 

 

 

 

view

 

 

(tests currently in file_assets_list, sort of)

 

 

 

 

delete

 

 

(tests currently in file_assets_list, sort of)

 

 

generic_content

(tick)

search results

 

 

 

 

 

 

 

create/edit

 

 

 

 

 

 

 

view

 

 

 

 

 

 

 

delete

 

 

 

 

 

generic_image

(tick)

search results

 

 

 

 

 

 

 

create/edit

 

 

 

 

 

 

 

view

 

 

 

 

 

 

 

delete

 

 

 

 

 

default partials

(tick)

search results

 

 

 

 

 

 

 

create/edit

 

 

 

 

 

 

 

view

 

 

 

 

 

 

 

delete

 

 

 

 

 

no model

(tick)

search results

 

 

 

 

 

 

 

create/edit

 

 

 

 

 

 

 

view

 

 

 

 

 

 

 

delete

 

 

 

 

 

NOTES:

  • Search results should be more basic blacklight
  • Delete action should be basic Rails
  • Different levels of Authentication (discover, read, edit ...) exercise different code.
  • The current tests are inadequate, so we will improve that as time permits.
  • Home Page needs similar love

Other Work

  • Rails Logic for the above,
    • e.g. where to create pieces of multi-page forms, how should the controller logic work
  • Rails 3 integration
    • currently Rails 3 work is a branch, and Media Shelf is responsible for keeping that branch in sync with master
    • when master is Rails 3, will there be additional work not reflected here? Jessie and Matt will confab.
  • Testing Basic JS - how?
  • Testing AJAX - how?