[Archivesspace_Users_Group] report on ArchivesSpace development work in November 2015

[Christine Di Bella]

Dear ArchivesSpace Members,

In response to feedback from the community, I present the first of what will be monthly development updates to the member listservs. These summarize the work on the technical side of ArchivesSpace in a somewhat less technical way, and give a sense of what's coming up next. If there's anything else you'd like to see in these updates, please let us know.

As always, the full blow-by-blow on development is available via our Development JIRA at http://development.archivesspace.org and the sprint reports on http://wiki.archivesspace.org.

Best,
Christine

Christine Di Bella
Community Outreach and Support Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)
[cid:image003.png at 01CE734E.FD759D30]




ArchivesSpace Development Update for November 2015

Testing for sprint 17<https://archivesspace.atlassian.net/browse/AR-1331?jql=project%20%3D%20AR%20and%20labels%3Dsprint_seventeen%20and%20type!%3Dsub-task%20and%20labels!%3Dsprint_backlog> was completed, testing on Sprint 18<https://archivesspace.atlassian.net/browse/AR-1331?jql=project%20%3D%20AR%20and%20labels%3Dsprint_eighteen%20and%20type!%3Dsub-task%20and%20labels!%3Dsprint_backlog> is underway and development for sprint 19<https://archivesspace.atlassian.net/browse/AR-1331?jql=project%20%3D%20AR%20and%20labels%3Dsprint_nineteen%20and%20type!%3Dsub-task%20and%20labels!%3Dsprint_backlog> has begun. In accordance with its high ranking in the member voting last spring, development focused on integrating the code for the Yale container management plugin into the code base (https://archivesspace.atlassian.net/browse/AR-1182). Issues worked on other than container management included releasing the refactored Archon migration tool (https://archivesspace.atlassian.net/browse/AR-1278), moving reports to the Background Jobs area (https://archivesspace.atlassian.net/browse/AR-1280), providing the option to use a database populated with demo data on startup (https://archivesspace.atlassian.net/browse/AR-780), fixing some new and recurring bugs (see https://archivesspace.atlassian.net/browse/AR-1333 and https://archivesspace.atlassian.net/browse/AR-1284 for examples), and addressing some small items related to imports and exports (see https://archivesspace.atlassian.net/browse/AR-1189 and https://archivesspace.atlassian.net/browse/AR-1352 for examples). Reports on completed sprints are available on the wiki at https://archivesspace.atlassian.net/wiki/pages/viewpage.action?pageId=18710534.

A release that includes the integrated container management functionality was projected for mid-December, though that was dependent on there being enough volunteer testers from the community to ensure that the new functionality works as expected and has not unexpectedly impacted any aspects of the current application. Testing will be the focus of the weeks leading up to the release. If there is limited availability for testing - a likely occurrence due to the time of the year - the release will come out in January instead. The latest release candidate is always available on http://test.archivesspace.org for those who would like a sneak peek. We will also be releasing a testing protocol soon for those that would like to test in a more structured way.

Work continues on the enhancement of the public interface, led by the many contributions of our member working group. You can follow the progress of this collaborative effort at https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project. The Cherry Hill Company will complete its consulting work later this month, and Brian has already stood up a basic framework and is working on implementing some of the wireframes.

Brad, Chris, and Brian participated in a developers meeting/hackathon hosted by NYU. About 20 participants in the ArchivesSpace community, including developers, system administrators, and archival staff from member and non-member institutions, convened for two days to discuss a variety of issues related to development and work on particular problems and goals. Representatives of the group and the ArchivesSpace Technical Advisory Council will be sending out more information on the initiatives that came out of the meeting.

Looking ahead, the Features Prioritization subteam of the Advisory Councils (https://archivesspace.atlassian.net/wiki/display/AC/2015-16+Features+Prioritization+and+Testing+sub-team) will be meeting on December 11 to determine priorities for the sprints in December and January. Focus continues to be on the highest priority issues voted on last June and new bug reports. All issues under consideration for this process are listed in the sprint backlog queue at https://archivesspace.atlassian.net/browse/AR-1209?jql=labels%20%3D%20sprint_backlog.

In 2016, ArchivesSpace development will move to a new sprint/release schedule. The highlights are:

*         A new sprint each month

*         A new feature release every four months

*         Maintenance releases throughout the year as necessary
The aims of this new process are to enable sharper focus on the issues worked on in each sprint, to provide enough time for issues to be fully addressed within individual sprints, and to provide adequate testing time before each feature release. The release process described on the wiki (https://archivesspace.atlassian.net/wiki/display/ADC/Release+Process) will be updated when we move over to the new process.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151201/c6739088/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7645 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151201/c6739088/attachment.png>