Page Comparison

Overview of what we do and how we operate – refer to bylaws info on TAC.

• Work occurs through cross-councils, sub-teams, encourage and support integrations, providing guidance to users (particularly migrations), technical documentation, collaboration with UAC on testing. 
• Refer to roster of names and email addresses of TAC members, if needed.
• Wiki space has our meeting notes and sub-teams have space to track notes and working docs.

Did retrospective last year. Can see what we thought we did well, what we could have improved on, what we had momentum with.

• Found that communicating scope and expectations helped a lot.
• Large group zoom meetings go well.

Please review TAC Responsibilities and Expectations.

This is a new document so please let us know if you have any feedback. Anything that should be added, clarified, or changed – we want to hear about it!

Overview of TAC sub-teams

• Integrations

• Migration
• Technical Documentation (TechDocs)

Overview of cross-council sub-teams:

• Development Prioritization (DevPri)
• Testing

Integrations:

• We deal with the data flow between outside systems and ASpace. Example: Archivematica-ASpace integration (Bentley, RAC, etc). 
• We're interested in integrations both ways (data into or out of ASpace).
• Primarily finding out about that integrations that exist, learning about new ones, be a resource to those working on integrations, or help them find other resources, working on documentation, how to advocate for integrations.
• Sometimes have guests in our meetings to talk about the integration work they're doing – lessons learned, etc.
• Looking for new members! Meetings are about once a month.

Migrations:

• Deals with initial import of data from other systems (Archon, AT, other legacy systems, EAD, etc) to ASpace.
• Being a first resource for those migration questions, did some work with EAD3.
• If you have ideas o

Technical Documentation:

• Last year's leaders have rotated off of TAC. 
• Focused on ASpace github pages