2018-05-18 Meeting notes

Listserv:

• Christine Di Bella
• Megan Blair
• Bobbi Fox
• Trevor Thornton

Code:

• Mark Cooper
• Christine Di Bella
• Bobbi Fox
• Rachel Maderik
• Laney McGlohon
• Dallas Pillen
• Trevor Thornton

Bug reporting:

• Ed Busch
• Christine Di Bella
• Patrick Galligan
• Laney McGlohon

I think that's everyone...

• Next release expected at the end of the month - mostly an infrastructure-focused release, but more visible improvements include refinements to the OAI-PMH and built-in exporters for MARCXML (including the option to exclude unpublished notes/agents from a MARCXML export), a new feature to add context to search results in the staff interface, some bug fixes, and updates to French translations
• We've had some casual discussions with people from Archive-It and ePADD about simple integrations and collaboration. If these are of interest to you, we'd love to hear from you about what you'd like to see in our respective applications and activities.
• We held our first regional forum in Boston at the beginning of May and have a southern California one coming up at the end of June.
• We've announced the date for the next annual Forum - August 14 in Washington DC. Planning group has started meeting and calls for speakers will go out soon.

Laney adds

that Boston forum went well; good attendance.

New release at end of month, code freeze today or Monday: exporters, OAI, search, reports

not sure about the status of the "casual discussions"

annual forum: announcements will go out soon.

People are rotating off at end of the term next month. People have expressed interest, will come up with lists.

Group has compiled initial list of resources.  Here's a link to the Google Doc: https://docs.google.com/document/d/1B3aIBZ5OIBGs0mDdGdtBEc1ozuHR4-UAge9CE154cGw/edit#

Created categories: implementation, training and documentation, APIs and scripts. Hope to encourage community to nominate within these categories.

Maggie has questions:

1. Needs to go on github; where?  To Maggie, makes more sense to put in main Aspace repo.

Laney: we have an archivesspace organization on github; we should create a new repo under that.  Maggie & Laney will talk off-line.

2. Ongoing maintenance: who does it?  Maggie thinks it's best to have one owner, but who? (TAC?)

Needs someone to respond to pull requests, etc.  Dividing it up by category might cause more things to fall into the cracks.  Just a list of resources; don't necessarily need expertise.  Patrick asks: how much time is a single owner willing to devote to keep it updated; how do you pass ownership to a new owner?  Would argue for multiple owners.  Maggie: a defined entity (subteam?), not one person, as "owner".  Are there any subteams interested?

The working group will put it live in June, and we can think about it for a couple of months, with Maggie as Vice Chair taking responsibility in the meantime.

Max proposes:

• a June (end of fiscal year) retrospective from sub-teams and working groups as to what went well, what could be improved.  Have another page in your wikispace. 
• Also go through this with TAC as a whole.
• evaluate how working groups went as a new idea this term.

Max will set up a June meeting.

• April: Patrick Galligan  – went up at end of April, following in Laney and Max's footsteps
• May: Scott Hanrath – going to do similar to Patrick
• June: Maggie Hughes