Questions from Cherry Hill

Owned by Tommy Keswick (Unlicensed)
Last updated: Sept 02, 2015 by Rain Michaels (Unlicensed)

We will be posting questions and observations here. Sometimes they may become tickets, or they may be addressed in this document or on the group calls.

Audience Questions

Many of these questions will be addressed when user personas are developed. They represent the sort of information we'll need going forward.

  • Who are the main audiences for the public sites?
  • What information do users typically come seeking?
  • Are users often looking for specific items?
  • Do users just want to know what is available?
  • What will serve users information needs better, searching or browsing?
  • Where do users get stuck when looking for resources?

Test Scenarios

On the last call it was suggested that we might be able to run some testing scenarios with real users.

  • What are some test scenarios that would make sense?
  • What would users typically do when coming to the site?

 

Many of the above questions have been answered by the User Tests and Personas. Additional questions are being posted as comments on these documents and will be discussed on the 9/3/15 call: 

 

Questions from JIRA that we will be bringing up on the 9/3/15 call: 

 

  • AR-942 - Getting issue details... STATUS  Would like overall thoughts from WG on this. We already have ideas based on testing, personas and desired UIs, but it would be good to know more about your thoughts.
    Related: https://archivesspace.atlassian.net/browse/AR-1031 and https://archivesspace.atlassian.net/browse/AR-838
  • AR-943 - Getting issue details... STATUS
    Would like to discuss the real goals here, since “above the fold” is not going to work with responsive.
  • AR-947 - Getting issue details... STATUS
    Would like more of an explanation of what is envisioned here. 
  • AR-948 - Getting issue details... STATUS
    Is this referring to the component record itself, or to search result listings? Or both? Should probably discuss since there are slightly conflicting views mentioned in the ticket itself.
  • AR-949 - Getting issue details... STATUS
    Can you clarify what this refers to?
  • AR-952 - Getting issue details... STATUS
    Can we merge this ticket with https://archivesspace.atlassian.net/browse/AR-1294? Also, what is CDL technique?
  • AR-958 - Getting issue details... STATUS
  • AR-960 - Getting issue details... STATUS
    Don’t understand this or further explanation. Discuss with WG.
  • AR-982 - Getting issue details... STATUS
    Can the WG expand on this more and give us an idea of the UI that you might be looking for? Examples?
  • AR-1004 - Getting issue details... STATUS
    Can you tell us more about the selection of columns? Is this referring to bootstrap columns? This may be more of a conversation for us to have separately with Brian.
  • AR-1025 - Getting issue details... STATUS
    Rank resources higher than components in search results? Perhaps there is a better approach (we have some ideas, like what Victoria Museum does).
  • AR-1033 - Getting issue details... STATUS
    Login link for staff? Should this be part of the public UI?
  • AR-1041 - Getting issue details... STATUS
    We are unclear on what is being requested here.
  • AR-1064 - Getting issue details... STATUS
    Request items feature.