2023-06-13 TAC meeting notes

 Date

Jun 13, 2023

Zoom Info

In meeting invite

 Participants

  • @Valerie Addonizio , TAC Chair

  • @Rachel Searcy , TAC Vice Chair

  • @Regina Carra, UAC Chair, ex-officio

  • @Christine Di Bella, ASpace Program Manager (regrets)

  • @Sarit Hand

  • @Regine Heberlein- Regrets

  • @Brian Hoffman

  • @Randy Kuehn

  • @Austin Munsell

  • @Elizabeth Roke

  • @Kevin Schlottmann

  • @Elizabeth Dunham

  • @Jenna Silver

  • @Tom Steele - regrets

  • @Matt Strauss- regrets

  • @Elizabeth M. Caringola

  • @Paige Monlux

  • @Kate Bowers

  • @Kevin Clair

  • @Cheylon Woods - regrets

  • @Suzanne Reller

  • @Daniel Michelson (Guest: Dev/Pri lead)

  • @Blake Carver (Guest)

https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3137961986

https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3137994811

https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3137994933

 Discussion topics

Notetaker: @Valerie Addonizio

Attendance: @Rachel Searcy

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

3 min

Welcome

@Valerie Addonizio

 

5 min

Program Update

@Brian Hoffman

 

10 min

Sub-team Retrospectives

Development Prioritization:
@Daniel Michelson

Integrations:
@Sarit Hand

Metadata Standards:
@Kevin Clair

Technical Documentation:
@Rachel Searcy

Testing:
@Austin Munsell

Please place a link to your Subteam’s Retrospective and include 2-3 significant takeaways.

  • DevPri:

    • Eliminated remaining backlog of unassessed tickets, which may allow more detailed work in future

    • Sharing agenda and issuing open invitation to TAC/UAC members to join the meetings was successful

  • Integrations:

    • Takeaways

      • There comes a time when you have to recognize that changes need to be made, i.e. sunsetting a sub-team.

  • Metadata Standards:

    • Provided a spec for reporting of elements not handled by a metadata importer as part of ANW-1558

    • Conducted field-by-field testing of the EAD2002 importer and provided documentation (still finalizing before end of term)

    • Compiled a test file for every EAD node, as well as tools to make your own, available here

    • Documented common EAD 2002 import issues here

    • Conducted an EAC-CPF survey of the community

    • Conducted a needs-gathering session on Subjects during the User Forum

    • Piloted sitting in on DevPri meetings

  • Technical Documentation:

    • Rebuilding year: focused on clarifying and documenting internal processes and workflows

    • GitHub repository maintenance: merged 10 pull requests and closed 3 issues. Training (within subteam and through Lyrasis GitHub for Everyone class) ensured that all members understand repository maintenance workflows.

    • Outreach and engagement: Promoted use of technical documentation at Virtual Member Forum and began conversations with User Docs.

    • Next year: More active evaluation and maintenance of documentation; identify ways to distribute work across subteam.

  • Testing:

    • Completed testing for 61 Jira tickets and one full regression (3.4.0), plus a bonus round of testing for the make representative function.

    • Continued virtual work sessions for both Jira and regression testing. This seems to help, especially for incoming members.

5 min

Valerie’s Retrospective

@Valerie Addonizio

  • Document and encourage cross-team collaboration

  • Acknowledge and reduce technical barriers and devise training

  • Reorganization and additions to internal documentation

  • More direct and personal support to Leads (Lead meetings, reduce context switching in emails)

  • Support and document the creation of ad hoc teams

30 min

TAC Retrospective

@Valerie Addonizio

@Rachel Searcy

It’s Retrospective time!
[link to TAC working document has been removed, comments will be synthesized into a formal TAC retrospective, which will be linked here]

5 min

End of Term Notes

@Valerie Addonizio

What happens next?

  1. You all get a break!

  2. Subteam leads contribute to one last quarterly report for this term

  3. Rachel will be in touch to let new team leads know about new member assignments.

  4. The next term’s workplan is due in September. You can decide to start work in July or August as long as you keep that deadline in mind.

Next Term

It’s never too early to start thinking about next term!

Incoming Leads in particular may want to review and

Consider keeping the same meeting times next term, since that slot is already taken up in your current schedule and it would only be new members that you’d need to poll for availability.

5 min

Open Mic

 

 

2 min

Closing Notes and Thanks



One last round of applause of Sarit, Randy, and Kevin S.!

It has been an honor to serve, you all know where to find me and I’ll certainly be around!

Super jazzed to turn it over to Rachel and Austin as Chair and Vice Chair!

HAVE A GOOD SUMMER!

 Action items

 Decisions