View Source

https://github.com/ndliblis/hydra_exhibit
https://jira.duraspace.org/browse/HYGALL
Done some work on creating exhibit framework for EAD-described collections using Hydra
Created OM terminology
Drill-down to item view
Exhibit browse framework - view separate from basic search for "boutique"-style exhibits - browse by facets, etc., e.g. filter by PID namespace
Informal roadmap: preview state,
Easy to chop up EAD into fragments - retained within each child; expressed as Fedora relationships
Some work to extract work on EAD processing into separate plugin; see the project's models for current status of EAD processing stuff
Status: 75~80% complete; definitely interested in working this into the larger Hydra codebase
Nothing holding ND to use EAD as such long term

We need to get an understanding of data modeling, and if and how current work will work to us.
EAD isn't necessity in terms of how data is stored (UVA thinking MODS for desc MD and RDF for structure)
Remember that archival description is describes aggregations - lowest levels of aggregations don't necessarily reflect traditional "items"
Mark M. wrote some notes last October about metadata model: https://gist.github.com/670061