Questions and practicalities
(temporarily moved to google docs)
General notes
Reindex everything into Solr from Fedora!
- ActiveFedora::Base.reindex_everything
opaquenamespaces: a community registry / namespace for RDF properties. Probably best practice to try to put locally-required properties there or somewhere similar. This was started by Karen and Tom at U Oregon.
Page numbers: can use this as literal sequence and put marked pagenumbers in page label property.
Book.where(title:"hat") # note this returns an array, not a single book object
re: IDs. consider using the default id as an internal identifier and another field as a local id for human use.
http://demo.curationexperts.com/
one challenge of hosting on amazon is moving large files around. sufia uses ffmpeg and converts them to playable proxies. anything that can be handled by imagemagick, openoffice / libreoffice (creates a thumbnail from the first page of the doc)
travis-ci.org/curationexperts/alexandria-v2/builds
https://travis-ci.org/projecthydra/sufia
rspec only? selinium with rspec?
or capybara with cucumber?
Example fedora instances:
scholarsphere
dl.tufts.edu - tufts digital library - put a hydra head on top of existing fedora repo. awesome transcription / TEI w/ embedded timecode / audio player
levysheetmusic - changes / customizations to interface
hullhistorycentre.org.uk - hull city archives - example of EADs. (nice search box page!)
hydra.hull.ac.uk - has a backend with workflow stuff. would likely be happy to give a short demo. (also note interesting icons)
alexandria digital research
spotlight (stanford) - library.stanford.edu/projects/spotlight - for exhibit building. - note: blacklight gallery gem gives you different views of results lists.
another gem: date slider
digital.case.edu (built on worthwhile, rdf-driven) - open seadragon + iiif-compliant server for amazing image viewing. view metadata / different formats.
dl.tufts.edu - MIRA (management of institutional repository assets. more workflow-type, controlled deposit.
Currently recommending different heads for different types of collections. use a shared gem for the data models. Then create a separate admin head for managing them all in one place.