| | | |
|---|
10 min | Welcome and roll call | @Maggie Hughes | Roll call question: What is your favorite breakfast cereal? Notetaker: @Wiedeman, Gregory Next time: @Trevor Thornton
|
5 min | Recent contributions | @Maggie Hughes | Shoutouts for contributions since the last time we did this (it was April!). Listserv: Alicia Detelich Edgar Garcia Sarit Hand Dave Mayo Trevor Thornton
Code: Maggie Hughes Dave Mayo Bria Parker Trevor Thornton Greg Wiedeman
Bugs/new issues: |
5 min | Program update | @Laney McGlohon (Unlicensed) | Working on ArchivesSpace 2.7.0, which is out for testing right now. Hoping for a release candidate later this week. New Webinar series on ArchivesSpace integrations will feature a new use case each month. First one will highlight Preservica. Contact Jessica if you have ideas Merger of Lyrasis and Duraspace is complete as of July 1. See lots of opportunities for closer collaboration. ArchivesSpace has been added to the Duraspace registry (https://duraspace.org/registry/).
|
5 min
| Review 2018-2019 TAC Retrospective | @Maggie Hughes
| Wanted to review our recent retrospective for new members, to keep in mind for the upcoming year, and because it relates to a few different things in this meeting. Start doing: Stop doing: Execution of working groups need fine tuning. Perhaps people are stretched thin in sub-teams and working groups and there should be limits. Perhaps reevaluate sub-teams like Migrations and Integrations, Integrations sub-team might not need to meet monthly and Migrations might not necessarily be needed since migration paths exist.
Keep doing: Cross-council meeting was super interesting. Conversation about how to encourage the community of coders as a group. Identifying issues was helpful in what we are doing (in sub-teams) Having a Vice Chair. Helps with transition.
|
10 min | TAC Sub-team memberships Integrations: Dallas Pillen, leader Valerie Addonizio Edgar Garcia James Griffin III Sarit Hand Randy Kuehn Joshua Shaw (UAC)
Metadata Standards: Jared Campbell James Griffin III Dan Michelson (UAC) Bria Parker Dallas Pillen Kevin Schlottmann Greg Wiedeman
Tech Docs: Alicia Detelich, leader Kevin Clair (UAC) Dave Mayo Trevor Thorton
Dev. Prioritization: Testing: | @Maggie Hughes + sub-team leaders | Review of members of TAC sub-teams Schedule time to meet with sub teams and develop work plan for things to accomplish before the end of fiscal year Metadata Standards needs a team leader – volunteer(s)? Tech Docs could use another member if anyone is interested No interest in continuing Reports Working Group. Reports efforts - from a usability standpoint - are intended to be picked up by the Usability subteam depending on member interest. Need TAC Vice Chair – volunteer(s)?
|
10min | Discussion of ad hoc working groups and other form feedback API Ad Hoc Working Group: Dave Mayo, leader Valerie Addonizio Alicia Detelich Kevin Schlottmann Trevor Thorton
| | Concerns with working groups and time commitments in the past, think we should be cautious when creating new ad hoc working groups. Created the API Ad Hoc Working Group. Good interest levels. Work plan with timeline Tight scoping
Other working group ideas: Interest in seeing whether a working group could be chartered with the goal of evaluating local ArchivesSpace customizations. Of primary concern to me personally would be detailing precisely how organizations have developed and maintained plug-ins. Further, another area of focus I would propose would be to evaluate how user interface customizations have been ported between upgrades of ArchivesSpace. I'd like to suggest an Aeon integration improvement working group. This suggestion is based on the results of the Integration Sub-team survey (shared at the Member Forum in Austin) + internal interest at Atlas in getting community feedback for improving the extant integration. Noticed more questions popping up regarding configuration and/or functions not working as expected. Perhaps some direction in that realm might be useful... Thought was that these are all great ideas, but we’re hesitant to start additional working groups now until we know TAC has the bandwidth for it.
Other comments: Ask TAC Metadata Standards to comment on Records in Contexts Ontology (RiC-O) when it comes out for public comments in October More basic education around the purpose and use of the API (through API Working Group) would be great.
|
10min | Brainstorming TAC meeting discussion topics | All | Thinking about how to make the most of our TAC meetings and building on our “how to encourage an active community of developers” conversations from last year. Keep space in our TAC meetings for program updates, sub-team reports, and other things, but add a discussion topic. Ideas: Each sub-team takes a meeting. Could be used to get feedback, discuss new ideas, etc. One TAC member suggested time for onboarding new members
|
5 min | Open mic | All | One TAC member suggested that discussions could focus on an individual system component (the AIP, containers, etc.) where we could talk about the pain points specific to them Another TAC member mentioned that they were surprised that certain notes were unpublished in a recent release and suggested some time to discuss how to better read release notes. A third TAC member suggested sending out a summary of Vice Chair duties to the group to encourage a volunteer
|