Completed Feb 16 sprint: 18 stories accepted; 9 stories rejected
Started March 16 sprint: 27 stories target; 11 for container mgmt., 9 for PUI, rest for miscellaneous
Still aiming for April release. Two challenges remain: 1) accommodate more parallel id sequences in the container mgmt. conversion process and 2) ensure conversion process does not convert data already converted
Training:
Workshops at:
Harvard’s Countway Library of Medicine
UC Santa Cruz
Guggenheim Museum Archives
Tri-colleges
Conferences / Presentations:
Code4Arc (preconference to Code4Lib): Brad W. presented an ASpace update remotely; Chris Fitzpatrick attended.
Code4Lib: Chris Fitzpatrick attended and staffed ASpace table; led a breakout on the ASpace API.
Digital Preservation Management workshop at Emory: Brad attended, gave two presentations and sat on two panel discussions
TAC:
Migration sub-team has been continuing work on batch EAD import, specification for Schematron validation solution to validate EADs against known ArchivesSpace constraints and requirements, providing assistance to implementers on listserv. They also revised their charge to clarify: the group can assist peers with migration questions but will not perform migrations on their behalf; and the group may also draft specs to make updates to migration scripts or make updates to the scripts themselves if and when relevant expertise is available in the group.
Integrations sub-team is reviewing results of survey re. integration projects and will update make a baseline update to integrations wiki page and have a process for ongoing maintenance of that info.
Technical documentation sub-team is reviewing which topics come up most often on the listserv as a basis for an FAQ.
Testing and Development Prioritization sub-teams have been undertaking work in prep for v. 1.5
UAC:
Testing sub-team has been working diligently to test issues for the 1.5 release
Development Prioritization sub-team has met once and queued up work for the developers
next UAC meeting is March 30, 2016
20 min
Update from Governance Board meeting
Brad W.
Lynda Kachurek
Jay Gaidmore
Updates:
Staffing
Development
Documentation
Membership
Training
Hosting at LYRASIS
Extended discussion:
Support philosophy
Staffing needs
Budgets for FY16 and FY17
Communication / Engagement plan
LYRASIS update
Appointments to Nominations Committee
Additional Items?:
Sally was contacted by a member who asked if there was a designated member advocate role for ArchivesSpace, i.e. someone(s) to whom ArchivesSpace members can escalate concerns about planned or current development to the application or other issues? If a user feels their concern is not adequately addressed / heard in the member forum, is there someone to whom they can escalate their concerns? Sally did not know the answer to this and did not see such a role in the bylaws so emailed Jay with the question (received an out of office) and is also raising here.
The discussion confirmed that this specific role did not currently exist / there wasn't a defined escalation tree. It was suggested that member concerns about the program could be reported to an organization's member representative and reported to program staff in that way. Beyond program staff, there is no defined escalation path or member advocate role so this is perhaps something to discuss and consider further.