Versions Compared

Old Version 11

changes.mady.by.user Cory Nimer

Saved on

compared with

New Version Current

changes.mady.by.user Johanna Carll

Saved on

Key

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

...

Time

Item

Presenter/Facilitator

Notes

5 mins

Ice Breaker

Suzanne Reller

Something you are looking forward to in the coming weeks

5 mins

UAC Updates

Suzanne Reller

ASpace Board approved change to by-laws to include Vice Chairs on Council Nominating Committee

New Ad Hoc Working Group in works:

  • Metadata Sub-team is going to form a group to create a data model of ArchivesSpace. More info to come in early 2023

Council technical training and professional development (follow up to previous Council-wide and recent TAC conversations):

  • Goals: Assist Council members with sub-team work by helping them understand the application better. Provide professional development takeaway for Council members in the form of ASpace training/guidance

  • Feedback needed:

    • Are there any existing technical barriers that stop you from doing your work on Council?

    • Are there skills you think are helpful for Council members to know?

  • Current ideas:

    • Host Tech Hour gathering

    • Surface existing documentation/presentations/resources and link them in Handbook

    • Valerie A. has offered to (co)create specific training resources that are directly relevant to Council work, such as spinning a Test instance on Docker (relevant to Testing sub-team specifically)

5 mins

Program Update

Christine Di Bella

  • Discussion on future development of the digital objects module scheduled for December 14 - registration at https://lyrasis.zoom.us/meeting/register/tZEpce-trjkoGdSGvc2uCimrn5zVU0UM-027 . We’ll be distributing a pre-discussion survey closer to the event. There is also some current development going on around some low hanging fruit digital objects issues like making it clearer in the public interface when there is digital content for a given resource.

5 mins

Sub-team Reports

Development Prioritization

Daniel Michelson

Matthew Neely

Reviewed 16 tickets (12 passed, 2 closed, 1 awaiting more information, 1 referred to Metadata Standards)

Users Documentation

Margaret Kidd Rebecca Baugnon

  • We were supposed to meet with TechDocs on 11/2 but have to reschedule the meeting.

  • We have not had our monthly meeting (scheduled for next week) so nothing new to report.

Testing

Cory Nimer

  • October testing of 14 tickets, comments added in Jira

Usability

Althea Topek Cory Nimer

  • Met in October and finalized two tickets for DevPri review (1 referred to Metadata Standards)

  • Started reviewing the bulk updater plug-in

Member Engagement

Bailey Hoffner Patrick Milhoan

  • December Member Match Event confirmed and promoted:

    • Sharing Tips & Tricks, Part 2!

    • December 8th, 1:00 EST

  • March Member Match Event w/ Dan Michelson on Jira ticketing TBD

  • Reviewed/Revised Member Match Half-Year Survey

  • Continued monthly discussion posts on Member Match listserv

  • Plans for Blog promoting “Making the Case for ArchivesSpace Membership” materials in January

5 mins

Open Mic/Questions for sub-teams

25 mins

Sub-team Led Discussion

Testing Sub-team

Questions: Is the current workflow between DevPri, developers, and Testing correct? Are there other application testing needs or collaborations that would be beneficial?

  • Does every developer update go through DevPri?  No, small changes and obvious bugs go straight to developers, then to testing without being reviewed by DevPri

  • DevPri process indicates their approval in comment on tickets.  Is that clear to developers and testing?   Is that working?

    • Testing replied by asking whether there should be a loop back to DevPri to see if ticket resolved as expected.  Christine noted that any changes to DevPri recommendation/approval are explained by developers and are usually due to technical barriers in resolving issue as outlined.  She added a reminder that DevPri function is to decide that something should be worked on with suggested priority ranking, but that what gets worked on when is decided by the development team.

  • Testing noted they have identified collaboration opportunities with User Docs to recommend changes or identify the need for changes to documentation, but the issue of how to communicate and where that fits in the team’s workflow remain under discussion

  • Testing is also exploring ways to open more direct communication with DevPri to get more clarity on the problem identified in a ticket and the desired outcome

5 mins

Final thoughts/questions

Suzanne Reller

Next Meeting Reminder

Suzanne Reller

There is no scheduled monthly meeting in December. Enjoy the holidays. Note: there is a TAC monthly meeting.

Next UAC meeting is January 17, 2023. Discussion will be led by User Documentation.

...