2017-09-15 Meeting notes

Date

15 Sep 2017

Attendees

Goals

Zoom option and sub-teams, ideas for ad hoc working groups, and questions/comments from ArchivesSpace TAC Sub-Teams 2017-2018 form.

Discussion items

Time	Item	Who	Notes
5min	Roll call
5min	Recent contributions		Listserv: Jason Loeffler Rachel Maderik Kari Smith Trevor Thornton Code: Mark Cooper Bug reporting: Jason Loeffler Thank you, thank you!
5min	Program update	Christine Di Bella and Laney McGlohon (Unlicensed)	Significant bugs that people have found–working on addressing those. Coordinating the two big features–EAD3 exporter (Trevor) and the assessment module. HM is doing development, sponsored by Tufts. Community engagement: Webinar on the new PUI (October) by Kim. Also Mark and Susan. Also folks from GVSU. Kim will be putting more info out in the coming weeks. Core Committers (Laney): Has been meeting, been doing some PR reviews. Student from GA Tech working on migration tools. Will be working on Containers next. Migration tools: Haven't upgraded in a long time–Trying to make it so that AT migration will got straight from AT to most recent ArchivesSpace version. Need to keep that updated as data model changes in ArchivesSpace. Had some issues with Archon migration tool, so starting with AT migration first. Timeframe: Student going faster than expected. Containers will probably be more slow going. Should have something before December 22. Hoping to have something out there by end of October. Maggie Hughes would be interested in helping test the updated migrator.
5min	Zoom		"Zoom provides the benefits of video conferencing (such as being able to see each other, chat, and share documents or screens) with the backup of a phone number that people without access to a computer (or whose institutions do not allow access to video conferencing software) can use to call in to participate. Zoom can also accommodate open calls since you can publicize the link and/or phone number without requiring that people sign up ahead of time or be on an invite list." "Some of you are already using Zoom accounts provided by your institutions to host meetings. For those without access to an account, or who would prefer to use an ArchivesSpace-provided resource, we now have an ArchivesSpace Zoom Pro account." Bobbi used Zoom. Kari too. It's good.
10min	Sub-teams		Development Prioritization: Megan Blair Patrick Galligan Jason Loeffler (Leader) Cory Nimer Kari Smith Integrations: Megan Blair Patrick Galligan (Leader) Maggie Hughes Jason Loeffler Dustin Stokes Migration: Terry Catapano Maggie Hughes Julia McGinnis Dustin Stokes (Leader) Trevor Thornton Technical Documentation: Megan Blair Bobbi Fox Scott Hanrath (Leader) Rachel Maderik Julia McGinnis Dallas Pillen Trevor Thornton Testing: Ed Busch Scott Hanrath Cory Nimer Dallas Pillen Kari: Seems to be overlap between Migration sub-team and the migration work Laney was talking about. Sub-team does lots of consultation one-on-one. Migration sub-team could do testing. Need to make sure we're not overstretching ourselves by being on too many teams. Sub-team participation is pretty much expected. Sub-teams are the way work gets done. Sub-teams are in nominations. Will talk about Testing leadership during Coordinating Committee. Miloche is the lead though.
20min	Ideas for ad hoc working group		Ideas: Spawning resources from accessions (Ed Busch) Some discussion on listserv on the limitations of this. Different field or more fields. Migration resources portal (Maggie Hughes and Dallas Pillen) Maggie: Collating resources. Write some checklists, a link to best practices. List blog posts or resources that have been written all over the place. Dallas: Seconding this idea. All sounds good. Would be interested in joining. Pre- and post-processing JSON (Jason Loeffler (Unlicensed)) Jason: Could be considered together with updating API documentation. Motivation is to get more thorough example documentation and cookbooks for API queries. Thinking how JSON needs to be formed for input. Cookbooks for advanced queries. Trevor would 2nd this. Does a lot of work with API, this part is a mystery. Also Patrick. Laney agrees. Resolving linked records–no way of knowing without trying stuff. Run into issues with deleting DOs (didn't delete links to AOs, just invalidates them). Could complement Patrick's Python script working group. Could be some shared concerns/interests. More explicit documentation would help the group. Provisioning/System administration (Jason Loeffler (Unlicensed)) Comes out of spending time on the listserv–decent number of inquiries on slow indexing, exhausted memory resources. Sysadmin issues. Making sure ArchivesSpace is properly deployed. Mark Triggs put together a monitoring plug-in. Documentation/managing local development/recommendations. How to work with Docker/Vagrant. Especially for someone with "intermediate" technical skills. Bobbi: Two separate things. One is for installing ArchivesSpace, one is how to provision for development. Talking about both things. Bobbi think it should be focused more on the first. Is some Docker documentation. Update API documentation/screencasts (Jason Loeffler (Unlicensed) and Dallas Pillen) Dallas: Basically similar to pre- and post-processing JSON. Include more detail and be a little more user friendly. What parameters to send and what to expect back. Screencasts are from when ArchivesSpace first came out–videos are helpful but could be updated. Aimed more toward casual user. Kari agrees. Maggie seconds. Jason: Anything we can do to demystify and putting toolsets into people's hands. Plug-in portal (Dallas Pillen) Could be helpful. Documentation and screencasts. Gathering together information about blog posts, gather community plug-ins. Similar to the migration resources portal. Laney: GitHub reorganization. Better documentation about how to use plug-ins. There is the `archivesspace-labs` space is just there. What exactly is supposed to go in plug-ins repo. Would be nice to have some central location. Maybe if we gave people a place to put plug-ins then could be central location for this. Trying to figure out exactly what this means. Patrick: Agree, just not sure how it would look. Would need to be done in close coordination with Laney. EAD3 support (Dustin Stokes (Unlicensed)) Initial requirements and all the specifications for anything. Noah and Trevor had been working on the export. Anything like this could be OAI-PMH support (Dustin Stokes (Unlicensed)) Could use these groups for internal organization things as well. How to coordinate these groups and activities.
10min	Questions/comments		Questions: Recommended reading? Are we, as members of TAC, supposed to be responding to and attending User Advisory Council meetings? Comments: TAC members should join staff interface working group, especially someone with real world UI/UX experience. Reports: UAC group. Might be interest in the future for more of a cross relationship (need some techy people).

Action items

Max Eckard will set up Zoom meetings from now on.
Scott Hanrath (Unlicensed), Jason Loeffler (Unlicensed), Patrick Galligan (Unlicensed) and Dustin Stokes (Unlicensed) will reach out to respective sub-teams to schedule meetings and come up with a work plan (include me as well to start with).
Max Eckard will reach out to folks about ad hoc working groups.