Page Comparison

Alexandra presented work of the group. Navigation team went through the existing JIRAs, categorized them, created some additional, and put information into a Google Docs folder/document.

Focused on background jobs navigation and linked records for this meeting. Created a mini-spec with wireframes.

Advice for creating wireframes: took screenshots and then used Powerpoint to reconfigure/annotate. (Can also use some free tools.)

Some items need input from other groups - for example, on AR-1773

Sara has also started looking at reports, and the Background Jobs area in general. Placement of reports in that area and name itself are some of the issues.

• More explanation of what a background job is in the application
• Question of whether individual types of jobs might be listed separately, or at least linked separately
• Brainstorm some intuitive titles
• Confusion when job fails
• When working in an instance with multiple repositories, big background jobs can impact others/create logjams
• More options of the background jobs page itself?

Discussion of issue

Miloche presented. Group created a Google Docs folder and document. Identifed three issues to start with.

• Question about sidebar when browsing accession records

  Jira Legacy
  server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key AR-1655

  - want to check about whether anyone using the ordering currently provided, or should there be a unilateral change. Most people prefer a browse by date, but are interested in providing a toggle and ability to manipulate facets.
• Default repository for login:

  Jira Legacy
  server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key AR-1621

  - JHU has a local workaround - they have default repositories by individual login. Lydia asked that Users Accounts and Permissions group look at this issue as well.

Word doc by screen - will be adding more to this.