Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

3pm ET/2 CT/1 MT/12

...

Find your local number: https://zoom.us/u/acA7Qf48Ej

Participants

Goal

Explore optimizing the Collection Organization tab on the PUI

Issue(s) (feel free to add more)

The Collection Organization tab is not user friendly in a number of ways. Some repositories have renamed the tab “Finding Aid View” but in general this is a confusing and underwhelming way to access finding aids.

Issues:

  • Continuous scroll is problematic for accessibility and keyword searching across the collection. There are two continuous scroll areas in the same area. There has been an ongoing bug about some finding aids stopping loading the entire finding aid. Some people has describing the scrolling view as “nauseating.”

  • There are Jira tickets because repositories want some or all data fields for archival objects visible in the finding aid view, similar to scrolling through the PDF export. Having to click on each archival object is not acceptable (is it? Or should the repository manager be able to set up a default of certain fields that should display but not all fields?)

  • The collection tree (currently on the right side) tends to be a preferable “clean” view. A lot of users (documented in a couple of Jira tickets) want to expand and pull over the collection tree. This could be because the view might seem more “clean”

  • For extremely long finding aids, the combination of the finding aid view and collection organization tree is not helpful because both are buried in the middle of very long series, essentially duplicating the view while also not preserving orientation within the hierarchy. At least in the tree view, it should always be possible to see what collection, what series, you are in. (Should all series be visible, only the series “above” the current location” or only the most immediate series?)

  • The style sheet for the collection organization tab is problematic (hence possibly why people want to view the tree instead). There are three different font sizes, which might make it more difficult to see.

...

Link to search Jira tickets

view-file
nameCollection Organization comments.pdf

Discussion topics

Tickets

Notes

all tickets w/ “Collection organization” in keyword

  1. https://archivesspace.atlassian.net/browse/ANW-998

  2. https://archivesspace.atlassian.net/browse/ANW-968

  3. https://archivesspace.atlassian.net/browse/ANW-960

  4. https://archivesspace.atlassian.net/browse/ANW-833

  5. https://archivesspace.atlassian.net/browse/ANW-769

  6. https://archivesspace.atlassian.net/browse/ANW-765

  7. https://archivesspace.atlassian.net/browse/ANW-759

  8. https://archivesspace.atlassian.net/browse/ANW-748

  9. https://archivesspace.atlassian.net/browse/ANW-682

  10. https://archivesspace.atlassian.net/browse/ANW-425

  11. https://archivesspace.atlassian.net/browse/ANW-306

  12. https://archivesspace.atlassian.net/browse/ANW-283

  13. https://archivesspace.atlassian.net/browse/ANW-517

  14. https://archivesspace.atlassian.net/browse/AR-370

  • 12 is closed and I believe 13 is for staff interface. Will make comments on our google doc; also added a comment below with mockup of compiled requests/comments. -Lori

4. recommend moving the instance info above the fold.

6. Contingent on a lot of currently parts. Complicated if there’s multiple instance info.

7. Configurable through the staff interface, that would be nice. Lydia will comment.

8. Complex. Recommend closing because the ticket isn’t extremely clear. We will address this as part of a larger project!

Next steps:

  1. Focus on adding screenshots and mock ups to the Google doc.

  2. Organize the google doc on themes

    1. Have examples of current scenario

    2. Have mocks up of desired views

  3. Aim to share the google doc on member list

  4. Gather feedback

    1. Create a google form to capture feedback?

      1. Rank and rate their priorities

Action items

  •  

Decisions