Page History

...

1. The item view has to function as a landing page that may be reached via Google as well as through Hypatia. 
2. Its primary purpose is to present the content and context of the "item", which may be a single file or a collection of files. I feel pretty strongly that the sidebar should not be made into a navigation view for the entire collection. 
3. Many of the items have a small amount of metadata that doesn't warrant a "show one section at a time" accordion style layout. (This may change as collections become heavily analyzed and annotated, but expand/collapse is easy enough to add later.)
4. I've removed Search from the equation for now. But we need to be explicit about whether the user is navigating the content of a container or the results of a search.
5. When we display metadata, we should not display labels for empty fields. If a value doesn't exist, its label doesn't display. 
6. The thumbnail appears to be supplemental rather than core content, and may not always be present, so I've moved it out of the center of the page.

...

{mockup:hypatia mockup item view|2}

...

Hull - Stephen Gallagher Collection

{mockup

...

:Stephen_Gallagher_fileview

...

|4}

Yale - MSSA_MS_1746

Archival description view

{mockup

...

:mssa_ms_1746_fileview

...

|7}

Technical metadata view

{mockup

...

:mssa_ms_1746_fileview_technical

...

|2}

*Tags and annotations view(

{mockup

...

:mssa_ms_1746_fileview_tags

...

|2}

Two Alternate Representations of Hierarchies

{mockup

...

:Two Alternate Representations of

...

 Hierarchy|1}