2015-10-29 Working Group Meeting
Date
Oct 29, 2015
Attendees
@Rain Michaels (Unlicensed)
@BradleyW (Unlicensed)
@Tommy Keswick (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)
Enable Brian to start working on some elements of the search wires
Answer numerous questions/have various discussions based on notes in wires
Review design elements: Design Feedback
Discuss Relevance in search results
Discuss next steps
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 |
|
2 min | Glossary | Tommy |
|
10 min | Review design concepts | Jungleen |
|
25 min | Wireframes | Rain |
|
15 min | Search relevance | Brian |
|
3 min | Wrap up & questions | Rain |
|
Meeting minutes
Recording:
Next steps:
Continued review of / questions on JIRA issues by CHC and WG
WG to review, comment, and answer questions on wires, CHC to refine them based on feedback
CHC continue working on aesthetic design elements, WG to review, comment, and answer questions
Next meeting Nov 12, 2015
will fill in any other items after call
Detailed notes:
Glossary:
Tommy reviewed what was done and why. This piece of the project is now complete for Phase I. Of course, nothing is ever set in stone.
Review of design concepts:
Acknowledged universal feedback to highlight search terms in a single color, rather than multiple, and to use one that is different from the colors used to indicate record types.
Discussed facets and sorting. Default is by count of items in the facet. Mark and Dara suggested that the user should be able to toggle between count and alphabetical. Added note from Rain based on something Brian brought up: Set to only show 10 by default, and then user can expand to show all? Will try this out in the wireframe for feedback.
We need to look into the language being used for the buttons under "display search results as" and choose natural language (e.g. all items, collections, digital items).
Wireframes:
Keywords in context: remove for subjects and people.
Subject: Mark brought up whether these should be a landing page or not. This might be a much bigger conversation.
Searching: would be great to include what library.unc.edu does in the search field, with suggestions and labels.
Mousing over the pager: like this only for date/title sorts (title needs to be added), but not for relevancy sort.
Image on collection: this brought up a big discussion. For phase 1, it will simply be a branding image that the archivist needs to select – by referencing an image URL -- in order to have it display. Keep the functionality showing the user how many digital items are available in the collection, and continue to have that link to the search results for digital objects in that collection. For later development: consider auto-pulling a digital object from the collection, and allowing it to be image/audio in player/video in player.
Request access: two is overkill, remove second one.
Archival object record: change to just use the word "record" so this isn't confusing.
Working group will spend the next few days (until EOD Tuesday Nov 3, 2015) reviewing the different displays, and looking for the questions in the blue panels. These discussions will happen on slack and confluence. Rain will begin working on wireframes again on Wednesday, and will review all of that feedback at that time.
Relevance in search results:
All testing and feedback needs to be done with a single data set, so please use the test corpus for this. Continue to provide Brian feedback as you go, and then Brian will pull all of the feedback together and determine what makes sense.
Action items