Child pages
  • Bear (Fall 2014) Release Workspace

Versions Compared

Key

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

...

Bear release plan

Target end date:

September 30, 2014

Goals: 

DAMS
  • Continue loading existing collections from the seed list, and possibly expand it depending on resource availability / projected rate of completion
  • Provide training and consultation to all campus DAMS users
  • Working with campus partners, identify and prioritize fixes and new features (known enhancements include Registry/DAMS interaction, bulk metadata edit, and advanced search)
  • Develop a broad-strokes plan for integration with Merritt, consulting with UC3 and campus partners as needed
  • Determine resource needs to support adding new collections to the DAMS and, accordingly, develop any needed policies and/or staging workflows
Aggregation (Harvest / Index / Collection Registry)
  • Develop a working harvest feeds for UCLA and UCSDGrab feed for at least one campus DAMS
  • Successfully obtain best possible copies of images for harvested objects and store in s3 with reference image-objects, for display in the public API
  • Run a full update on collections currently marked as harvestable, push all the way to the registry solr instance
  • Continue to build the harvest infrastructure to support contributing metadata in a single source to the Digital Public Library of America
  • Continue to develop the Collection Registry to support the needs of the systeminterface
  • Rebuild the Solr index with updated collection information and technical enhancements
  • Map out workflows for using the Collection Registry and, accordingly, needed development on it
Public Interface (API / HTML)
  • Complete remaining wireframes, conduct user testing, and complete all revisions
  • Complete the graphic design process (early October)
  • Conduct a gap analysis to determine features demanded by the wireframes that we do not yet have in place; start research and testing to determine technical solutions
  • Unpack, test, and continue to ready the API by creating a prototypeBasic documentation (tutorial?) for external (to CDL) ; develop initial documentation for use of the API , based on what learned by the prototype.by campus libraries
  • Determine a workflow and process for constructing the site after all wireframes and graphic design files are handed off 
  • Conduct transition planning from the old to new Calisphere sites to inform key technical decisions

...