Hi Erin, As Rick mentioned today in standup, we presented an early version of the structured date popup to Susan Stone and Glen Jackson yesterday, which is a somewhat rough initial implementation of the popup shown in the wireframe at: http://wiki.collectionspace.org/x/KYDiAw They had several interesting user experience observations which might pertain to any popups in CollectionSpace, not just this one. Among these: 1. Tabbing through a popup's fields can be problematic As Rick mentioned in a note to the Work list today, when tabbing forward between fields, Glen and Susan found they needed to tab through all of the fields in the popup - there are currently 11 fields - before reaching the next field in the record. One possible approach to mitigating this inconvenience: perhaps we can explore how we might give the user, via UI behavior, the ability to dismiss the popup from the keyboard and move on? One possibility: * tab (into the popup) * esc (to dismiss the popup, if the user doesn't want to edit any of its fields) * tab (to move to the next field) (Backwards tabbing passes through only a single field in the popup, BTW, which isn't a big inconvenience. Only forward tabbing has this issue.) 2. It can be inconvenient to refer to values in the popup While popups go a good job of preserving space on a data entry form, especially where the same set of fields appears in multiple places/contexts within a record, they also hide data when closed. At least some structured date fields are envisioned to be multivalued (aka repeatable). In those cases, it'll be inconvenient for the user to refer to the data in the other values when adding a new value, or editing one of these values. They might literally have to visit each popup, and jot down or screen-capture its data. The primary reason for wanting to refer to other values is to avoid inadvertently entering duplicate (or mostly duplicate) data in a new value, but one can envision other use cases. There are also cases where a user may want to refer to the data in the popup while editing an unrelated field. However, if the popup closes when the user puts focus elsewhere, such as when clicking in a second field, that can also present difficulties. That can partly be mitigated by having two or more fields from the popup present in the underlying record - such as Date Text and Date Association, in the case of structured dates - even if the popup is closed, so you would have somewhat more data displayed outside the popup, but that isn't a perfect solution. We also discussed more far-reaching alternatives: presenting read-only tabular views of data (not just in popups, BTW) that supplement the GUI forms view of the data; as well as having the ability to keep open ("pin") popups, or have their data appear in a sidebar. Aron