Date
Attendees
- Christine Di Bella
- Laney McGlohon
- Peter Carini
- Megan Blair (regrets)
- Ed Busch
- Terry Catapano (regrets)
- Mark Cooper
- Patrick Galligan
- Scott Hanrath
- Maggie Hughes
- Jason Loeffler
- Rachel Maderik
- Julia McGinnis (regrets)
- Cory Nimer
- Dallas Pillen
- Terry Reese (regrets)
- Kari Smith
- Dustin Stokes
- Trevor Thornton
Goals
- Review sub-team work plans, introduce ad hoc working groups and discuss outreach idea.
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
5min | Roll call and note taker | Bobbi, notetaker | |
5min | Recent contributions | Listserv:
Code:
Bug reporting:
| |
5min | Program update | Christine Di Bella or Laney McGlohon | Christine: put out today: release 2.2.1, mostly bug fixes and community pull requests. Working on documents relating to making it clearer and more transparent on how contributions are evaluated; different kinds of development one can do and ways that plugins can be converted into the main code body. Engagement things going to be happening, including the webinar on testing next month. Laney: migration tools: co-op student, Sarah, from Geo. Tech working on upgrading migration tools; have a test version of the migration tool, getting good feedback from some users. Hoping to get release out early December, first AT, then Archon. Would like more Archon databases to test. Promise to destroy it! after testing. co-op student also working on documenting datamaps, plus some pointers to make migration go faster (like turning off PUI indexing |
5min | "Reporting line" for cross council sub-teams | ||
10min | Sub-team (other other) updates | Laney McGlohon, Jason Loeffler, Patrick Galligan, Dustin Stokes, Scott Hanrath | Core committers group Development prioritization sub-team (cross council with UAC) Integrations sub-team Migration sub-team
Technical documentation sub-team Testing sub-team (cross council with UAC) |
5min | Ad hoc working groups | Dallas Pillen and Maggie Hughes | API Documentation Working Group Purpose: Create documentation and/or screencasts for using the ArchivesSpace API, including JSON examples for post bodies/responses. The need for this kind of information came up on the listserv as recently as (11/13). This working group would be responsible for determining the scope and timeline of this work (because it could be a huge amount of work!), its relationship to the existing API autodocs, its format, where it would live, etc., as well as how it it would be promoted and maintained going forward. Awesome ArchivesSpace Working Group Create an Awesome List repository (or similar), to live in the ArchivesSpace or ArchivesSpace-Labs GitHub organization. The list would start with two categories (which could be expanded later) based on the interests of the current cohort of TAC members: migrations and plug-ins. It would point to items that are and aren't maintained by the ArchivesSpace program team, and that are inside and outside of the existing ArchivesSpace repos. Inclusion on the list wouldn't represent an endorsement of any kind. The working group would be responsible for the initial population of the list and provide a plan for promoting and adding to and maintaining it going forward. For an example of what this might look like, see the IIIF Awesome List. |
10min | Discussion: ArchivesSpace process for evaluating potential feature contributions to the core code | ArchivesSpace Process for Evaluating Potential Feature Contributions to the Core Code | |
5min | Discussion: Blog posts for TAC and sub-teams | ||
5min | Discussion: "Best practices" for descriptive metadata in Archival Objects and Digital Objects | ||
5min | Open Mic |
Action items
- Max Eckard will clean up TAC space.