2015-12-10 Working Group Meeting
Date
Dec 10, 2015
Attendees
@Rain Michaels (Unlicensed)
@BradleyW (Unlicensed)
@Brian Hoffman (Unlicensed)
@Mark Custer (Unlicensed)
@Jungleen Bae (Unlicensed)
@Susan Pyzynski (Unlicensed)
@Susan Luftschein (Unlicensed)
@Cate Putirskis (Unlicensed)
@Linda Hocking
@schwrtzse (Unlicensed)
@Cory Nimer
@Maura Carbone (Unlicensed)
@Matt Francis (Unlicensed)
@Claryn Spies (Unlicensed)
@Dara Flinn (Unlicensed)
@kferrante (Unlicensed)
@Jessica Crouch (Unlicensed)
Goals
Review Wireframes – (link to discussion area)
Answer questions that remain in the wireframes (go through all of them)
Review design elements: Design Feedback
Wrap up
Meeting details
Eastern time: 12:30 pm
Central time: 11:30 am
Mountain time: 10:30 am
Pacific time: 9:30 am
To join the meeting:
https://global.gotomeeting.com/join/504319125
Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.
Dial +1 (646) 749-3122
Access Code: 504-319-125
Audio PIN: Shown after joining the meeting
Meeting ID: 504-319-125
This meeting will be recorded.
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
5 min | Welcome | Rain |
|
30 min | Wireframes & final questions | Rain |
|
15 min | Review design concepts | Jungleen |
|
10 min | Wrap up | Rain |
|
Meeting minutes
Recording:
Next steps:
Cherry Hill to deliver revisions and other deliverables on Dec 18, 2015
@Brian Hoffman (Unlicensed) and ArchivesSpace to continue development
@Brian Hoffman (Unlicensed), @Mark Custer (Unlicensed), and @BradleyW (Unlicensed)will connect with Cherry Hill when ready for another cycle as needed (2 more cycles were planned for)
Detailed notes:
This call was primarily about reviewing the wireframes and getting in depth feedback. More feedback is needed, and the WG has been asked to review further and give all feedback by Monday morning (10am PT). That feedback can be given here as comments on the meeting agenda, or in Slack. Rain will be reviewing everything.
Highlights from the wireframe review:
Home page
Featured collections: keep them as manual so that they can be carefully controlled (Brian mentioned that from a technical standpoint it doesn't matter)
Whats in our collections area: allow which elements display here to be customizable
Advanced vs. simple search
Brian brought up before meeting that there is no simple search, and if we want to offer it we could do so with the foundation switch tool (start simple, switch to advanced)
We went straight to advanced because of the challenges people had with simple search on the user testing
Discussed whether or not the keyword search is basically the same as simple search, and Brian confirmed that it is not (he posted a link detailing the functionality that I did not copy over, so ask him if you have questions about how this works)
Matt and Mark both expressed a preference to keep as is in the wireframes and test, with the caveat that we might need to change it if it is not correct
Identifier needs to be added as a search option under the keyword list
Terms/Subdivisions on the subject landing page
Maura had questions about where this was coming from, which is from the staff UI (the form)
At this time, no change is needed to this element
Overall landing pages
Need to add a control for users to choose how many records display in the list (next to sort order)
Generally, each item needs to take up less space
Record Groups overall landing page
Needs to be completely revised, as CHC does not have a good understanding of what this is supposed to be
@Cate Putirskis (Unlicensed) and @schwrtzse (Unlicensed) will provide screenshots and basic mockups (can be just a text document) of what they really need out of this so that we can revise and understand the hierarchical needs better
This also plays into the individual record group landing pages, as well
Individual landing pages (repo/agent/subject/etc.)
Citation/bookmark/etc. utilities are not needed on these pages
Keep the breadcrumbs for consistency
Individual repository landing page
Add an opening hours field (which needs to also be added in the staff interface
Add the same types of icons available on the home page, with what the specific repository contains
Remove search, facets, and the list of collections
@Susan Luftschein (Unlicensed) wanted to confirm that if the data changes as new standards are incorporated, that new data can be added to the public UI (answer is yes)
@Brian Hoffman (Unlicensed) mentioned that customizing which data displays may be a Phase II consideration, but is also possible
Individual agent landing page
@schwrtzse (Unlicensed) mentioned that it would be good to have those collections where an agent is creator prioritized at the top and given a visual indicator
Search wires
@Mark Custer (Unlicensed) noted to change “keywords in context” to “search terms in context" for consistency
Contents & Arrangement on record dsiplays
Implement the tab idea, but keep the right sidebar (Cory and Linda both expressed a strong preference for the usefulness of seeing the Contents & Arrangement in the right sidebar)
Wrap up notes:
CHC will wait until Monday, 10am PT to continue with our work to give the WG time to provide feedback on Slack and confluence. Please do so! We will likely ask individuals questions directly based on the feedback we receive.
Once we start making changes, we'll keep everyone updated on Slack as pages change and are ready for review.
We are working to turn over the final deliverables by CoB 12/18. This includes our initial recommendations, wireframes, style guide and design comps. Some of the design comps may need additional tweaking following that date, but will be turned over very quickly after that if not on that date.
@BradleyW (Unlicensed), @Brian Hoffman (Unlicensed), and @Mark Custer (Unlicensed) will be meeting to determine which aspects are part of MVP/Phase I, and which need to wait for Phase II.
After Phase I is implemented, more user testing will be done on the test corpus, and CHC may be asked to jump in for additional revision cycles.
@Rain Michaels (Unlicensed) and @BradleyW (Unlicensed)will touch base on Monday or Tuesday of next week.