...
- Yale & Duke are both using a Fedora 3 Hydra stack; both unable to transition smoothly to Fedora 4 / Hyrax right now.
- Yale's inability to upgrade is primarily due to volume; 3M images, adding 100K/yr. Stored in Fedora (not external datastream as Duke has done); Yale awaiting an upcoming Fedora API to aid upgrade.
- Both Yale & Duke mid-transition for DCs: moving legacy digital collections into Samvera.
- Yale's legacy DC platform is VuFind (homepage; example item); will retire it once migration complete; target Jan 2018 b/c campus IT taking away their VuFind Solr index.
- Yale's new DC platform: Samvera/Blacklight (homepage)
- Yale uses Samvera software only for discovery/access; they use Preservica to meet digital preservation needs.
- Yale grappling with how to get FindIT Samvera app to appear as a cohesive platform for digital collections.
- Yale: no image server / viewer architecture yet for FindIT but they're interested in Open Seadragon / Universal Viewer.
- AV & accessibility: Yale does use OHMS but concerned not sufficient for accessibility; grappling with expense of vendor-provided captions, interested in how we do this work.
- Kissinger digital collection landing page is in Drupal
- Yale's Samvera/Blacklight has three kinds of objects, e.g. IA bookreader; Basic image view; Kissinger-type folder
- Yale metadata profiles determine up-front; process EAD → MODS → ingest into FindIT
...