...
Name | Role | Institution |
|---|---|---|
Michael Olson | Project Manager | Stanford |
Mark Matienzo | Functional lead Lead | Yale |
Naomi Dushay | Lead Developer | Stanford |
Bess Sadler | Consultant Consulting Developer | Stanford Fitz |
Chris Fitzpatrick | Consultant Consulting Developer | Stanford |
Jennifer Vine | UI Design Designer | Stanford |
Jessie Keck | UI developer | Stanford |
Lynn McRae | Data architect | Stanford |
Tom Cramer | Project Director | Stanford |
Adam Soroka | Data architect (consulting developer) | UVa |
Julie Meloni | UVa Lead, UI (consulting developer) | UVa |
Joe Gilbert | UI (consulting developer) | UVa |
Molly Pickral | consulting developer | UVa |
Media Shelf | Developers
| Vendor |
Adam Soroka TBD | Fedora Consultant: Data modeling Loading | UVa |
Julie Meloni | UVa Lead and UI developer consultant | UVa |
Molly Pickral | Developer consultant | UVa |
Joe Gilbert | UI developer consultant | UVa |
...
TBD |
- Stanford will draft development plan, including SOW for contract development, and share with UVa and AIMS partners
- With UVa sign off, UVa will issue contract and serve as contract manager with MediaShelf
Fedora Instances and content loading
- Fedora instances envisioned
- Stanford will host dev and public demo application w/ a representative sample of publicly accessible, demo objects across multiple (or all?) AIMS collections
- parallel demo application at UVa?
- Stanford will host Stanford collections long term
- UVa will hosting of UVa, and likely Yale collections, long term
- Hull will host Hull collections, long term
- Stanford will host dev and public demo application w/ a representative sample of publicly accessible, demo objects across multiple (or all?) AIMS collections
Development Process
- Monthly iterations
- Weekly deploys, continuous builds
- Weekly calls of -dev team (Tuesdays)
- Iterative development process
- load first set of objects into Fedoras, index in solr, expose via BL
- assess presentation, modify data model and software accordingly
- reload data
- rinse, repeat
Reference Note: on SALT, we loaded, reloaded and modifed in place the Feigenbaum content roughly two dozen times to get it to its current form.
...
Synching efforts across Hydra projects / institutions
...
High Level Roadmap
Key Tasks & New Work
- Merge Libra and Hydrangea into stable Hydra trunk
- Set up Hypatia / Fedora stacks (-dev and -demo at Stanford, others?)
- Data ingest, solr indexing, exposure via Hypatia's BL
- Data modelling: AIMS archival items, components and collections in Hydra
Development Tasks: New Components & Deliverables
- Item discovery and views (object specific behaviors for archival objects, including definition of possibly compound or complex objects, display of appropriate descMD, techMD, including both individual "files" and disk images)
- Archival collection discovery and views (object specific behaviors, reflecting appropriate descMD, techMD, adminMD, provenanceMD, and reflective of and/or complementary to EAD)
- Application of APOs (AdminPolicyObjects) at a collection level
- Development of Hydra set objects (aka "discovery collections") to support arrangement and description of collections into archival components
- Use of set objects within Hydra Hypatia
- creating set objects (aka archival components)
- description of set objects
- addition of items to set objects
- individually (must have)
- bulk (desirable)
- discovery of set objects
- display of set objects
- Enhancements (TBD) to ActiveFedora, OpinionatedMetadata, Hydra infrastructure tickets (e.g., migration to Rails3)
- Archivists' Dashboard, for arranging and describing items and components