UI Planning

[bnlawrence]

We have resolved to mimic the basic structure that underpins the historical ESGF interface, as it is familiar, and very functional.
That is, the default view will be three panes:

• navigation/search (let's put the search button on that side, I hate the search button being somewhere else)
• atomic dataset view
• location view

In the navigation view we anticipate two pieces, an upper piece, dynamic, driven by collections, which will allow nested selection from a starter view which is "the user's collection"; and a lower piece, static, driven by data, and any external knowledge of semantics we might want to apply (e.g. some CANARI structure around experiments and simulations) and at least:

• a name piece allowing selection via drop down of standard names and of long names
• a temporal piece allowing selection by averaging and cell method
• resolution and domain

In the atomic dataset view we will want people to be able to select directly, or select by fuzzy match (stretch goal), to create their own collections. We also want them to be able to click on a particular atomic dataset and see all the metadata, and if any of that metadata looks like a hyperlink, make it navigable.

In the location view we want to show where the data are in multiple columns (potentially including "other" if they want, for example, to move data elsewhere). We want people to be able to eventually selection an action from this menu (if they want).

[georgeoobrienNCAS]

cfstorewebsitemockup.pdf
Something like this