2021-10-18 Meeting Notes

Date

October 18, 2021

Meeting link:

Join Zoom Meeting
https://umd.zoom.us/j/3910366448

Meeting ID: 391 036 6448
One tap mobile
+13017158592,,3910366448# US (Washington DC)
+13126266799,,3910366448# US (Chicago)

Dial by your location
        +1 301 715 8592 US (Washington DC)
        +1 312 626 6799 US (Chicago)
        +1 929 436 2866 US (New York)
        +1 346 248 7799 US (Houston)
        +1 669 900 6833 US (San Jose)
        +1 253 215 8782 US (Tacoma)
Meeting ID: 391 036 6448
Find your local number: https://umd.zoom.us/u/aqlRATsH6

Participants

  • @Joanne Archer (Unlicensed)

  • Kate Blalack

  • @Kellen Carpenter

  • @Cory Nimer

  • @Althea Topek

  • Guest: @Christine Di Bella

  • Notetaker: Joanne

Agenda

  1. Welcome and Introdcuctions

    1. Icebreaker: Favorite Fall activity

  2. Development Roadmap (Christine)

  3. Guidance for usability team on specifications etc

  4. Wrap-up/next steps

Discussion topics/Notes

Topic

Items

Notes

Topic

Items

Notes

Welcome and Introductions

 

 

Development roadmap

Christine discussed the technical roadmap and how it is developed.

  • based on sense of what is a priority in the community/what are known and/or urgent priorities

  • What are long standing projects that can be wrapped

  • Takes into account the resources/skills available and that things happen (like pandemics)

2 issues that Usability could look at that are upcoming/related to roadmap for Fall 2021 and early 2022

  • Spawning specification (doc linked in items). Usability can vet and provided feedback. How should this function and work. Edit and provide feedback directly in google doc

  • Staff and PUI pdf-what should the pdfs look like. Should they the be the same or differently. End product should be to create a pdf we think should be generated from system including formatting and fields.

Later down the road it would be helpful for Usability to look at the reports area. How should people navigation that area.

Discussion

 

ArchivesSpace happy to hear if there are issues/concerns being raised. Gather information in a variety of informal/formal ways including surveys, community forums, Jira tickets etc. Don’t want to raise hopes too much about time frames when work can be completed as they are a small team.

Specifications should clearly state what should happen within system and try to avoid making everything flexible.

Usability will continue to look at tickets that are assigned to the team via jira. There are often opportunities to work on tickets outside the development roadmap. If they are ready to go with clear specifications it more likely than can be addressed.

Usability will wrap up work on the visual cues for digital objects that we worked on last year but didn’t update in JIRA

 

Next steps

 

For November meeting

  • Finish initial review of spawning specification

  • Finish visual cues for digital objects:

Action items