2016-03-21

5 min

Intro

Actions from previous calls:

All

Thanks to TAC members for recent listserv contributions:

• Answering questions on the listserv
• Code, documentation and bug reporting contributions

Thanks to TAC members who have helped out colleagues and/or contributed to email list discussion since February TAC call:

• Esmé Cowles (Unlicensed)
• Noah Huffman (Deactivated)
• Max Eckard
• Patrick Galligan
• Kari S. (Unlicensed)
• Phillip Suda (Unlicensed)

And thank you to TAC members who have submitted pull requests:

•  Scott Hanrath (Unlicensed) 

• Development:  
  • Completed February 16 sprint: 18 stories accepted; 9 stories rejected 
  • Started March 16 sprint: 27 stories target; 11 for container management, 9 for public user interface (PUI), rest for miscellaneous. Have made significant progress with the container management blocker stories, but these still need to be tested. We are currently reviewing a first draft of the documentation for container management.
  • Still aiming for April release. Two challenges remain: 1) accommodate more parallel id sequences in the container management conversion process, and 2) ensure that the conversion process does not convert data already converted.
     
•  Training and Consulting: 
  •  Workshops have been held at: 
    • Harvard’s Countway Library of Medicine
    • University of California, Santa Cruz
    • Guggenheim Museum Archives
    • Tri-Colleges Consortium
    • George Eastman Museum
    • Webinars for Keystone Library Network clients, March 30-May 6

• Conferences / Presentations:
  • Code4Arc (preconference to Code4Lib):  Brad W. presented an ArchivesSpace update remotely; Chris Fitzpatrick attended. 
  • Code4Lib:  Chris Fitzpatrick attended and staffed ArchivesSpace table; led a breakout on the ArchivesSpace API.  
  • Digital Preservation Management workshop at Emory:  Brad attended, gave two presentations and sat on two panel discussions
    
    

• Governance board:

  • Met on March 11, first part of meeting dealt with updates (operations, Council updates), and session items on developing support philosophy (will be shared when ready), staffing for 2017 (to try to put more resources into development, icebox backlog, EAC-CPF compatibility, reports). No decisions as to how resources should be allocated. Ended meeting by appointing a nominations committee for 2016-2017, will be kicking off in a week or two. Need two new members of governance board (very-large and small). Gordon and Sally are part of that committee, and they will be canvassing rosters of TAC and UAC about serving on advisory committees.

  • Revised budget for 2016 needs to be submitted before decisions about staffing can be made, revised 2017 budget also needed.

Did not meet last month between calls, but working on a couple of things. Have been involved in testing for container management, others have been helping with list questions and Noah has received a couple of requests about migration support at West Virginia University and the Smithsonian. Posted a revised charge for the subcommittee to the wiki. Terry C. and Noah need to follow up on the Schematron stuff from the last call, and there is still some work in reviewing the import/export mapping documentation on the website.

Working on members listserv review for frequently asked questions. List of questions available on subcommittee site. Looking at possibilities for FAQ, afterward will be looking at how to address them and move forward.

February 23, met with Brad and developers to sort through the 39 stories in the backlog--13 on container management, 12 PUI, and other. Of those, 12 given highest priority during the next set of sprints. This is now updated on the JIRA boards. Realized that more time is needed to walk through the process of reviewing the stories--dropping and dragging within the boards.

Reviewed the 20 items listed in JIRA, are in the process of providing feedback.

No report.

No report.

Met on March 16, refined definition of integrations and worked on developing tiers (3 tiers--lowest level just pulls information into ArchivesSpace from another system or vice versa, no data model changes, nothing really created; mid-level where most of the work being done, requires a plug-in, but no change to core ArchivesSpace code (Archivematica, Preservica), can use API, data flows in and out; at highest level (which haven't seen yet) is something that would require a change in ArchivesSpace data model to accommodate. Tiers were meant to provide guidelines on level of participation by subcommittee. For the definition, established that it would be a "functional coupling" to create a coordinated whole.

Kari S. (Unlicensed): Radcliffe Institute for processing and digital archives will be at beginning of April. Will be looking at "what is a finding aid" in the age of digital archives, hoping that there will be notes or other materials available for the community. Will be passing along information from the conference relating to ArchivesSpace.

Sally Vermaaten (Unlicensed): At Code4Lib with other TAC members recently. Fair number of comments on ArchivesSpace, and Chris Fitzpatrick talk on API use. Interest in integrations between applications.