Meeting ID: 812 2402 7948 Passcode: 798950 One tap mobile +13126266799,,81224027948#,,,,*798950# US (Chicago) +19292056099,,81224027948#,,,,*798950# US (New York)
Dial by your location +1 312 626 6799 US (Chicago) +1 929 205 6099 US (New York) +1 301 715 8592 US (Washington DC) +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US (Tacoma) 877 853 5257 US Toll-free 888 475 4499 US Toll-free Meeting ID: 812 2402 7948 Passcode: 798950 Find your local number: https://lyrasis.zoom.us/u/kcski1mVb
Next release is planned for late December/early January. This will be a significant change in how ArchivesSpace is deployed and requires an external Solr database. Training and documentation will be coming out.
Currently doing training for diversity partners. Community wide training is coming up in October.
ArchivesSpace will be participating in Hacktoberfest
Update and review user documentation on a systematic basis
Create documentation for new features (i.e., custom reports)
question from group about how user documentation communicates updates and changes to community. Could there be something placed on landing page for User Docs to let people know about work. Committee will consider and discuss suggestions.
TAC is looking at workflows, visibility, and training as themes for the year.
Live leadership training videos are now available in Lyrasis learning.
Question about the logic behind arrangement of confluence pages. ArchivesSpace is for general documentation; for community members to collaborate, information distribution and community collaboration
Advisory council: collaboration for Advisory council but it is public. There are few spaces that are private for just council members
Help center is a member only space; private space; benefit of membership
Randy and Dan are preparing to a proposal to make organize Advisory Council in a more streamlined way.
Question raised on behalf of organizations in the UK: What is the long term support for new releases. With upcoming release might be many small/medium institutions that won’t be able to make that adjustment quickly and want to stay on previous versions. Is there any scope for previous releases to be patched/fixed (vital) for a set period of time?
ArchivesSpace has a small team that is not sustainable to patch previous releases
Will be focusing on providing a lot of training and support to make transition to external Solr/will be trying to make this transition as easy as possible
Code will still be up-so community members might patch any critical flaws
Could we bring it up at the community day in April? How many people could this affect? Is there a way for the community to help out?