...
Meeting minutes
Recording:To
fill in after call.
| Widget Connector | ||
|---|---|---|
|
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
- will fill in any other items after call
Detailed notes: To fill in after call:
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 ) 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
- 03 - CHC (Rain Michaels (Unlicensed)) continued revisions to wireframes
- 03 - CHC (Jungleen Bae (Unlicensed)) continued work on design elements
- - Working Group review search relevance behaviors in http://pui.archivesspace.org and provide input here: Relevance in search results
- - CHC (Rain Michaels (Unlicensed)) provide Brian a list of technical requirements to meet the functionality in the wireframes, as well as a sense of what aspects of the wires are "Phase I" complete and what is still being worked on so that he knows what he can start building
- ASpace (Brian Hoffman (Unlicensed)) begins working on Phase I development items where possible
- CHC (Rain Michaels (Unlicensed)) post agenda for meeting
- will fill in any other items after call