[Archivesspace_Users_Group] ArchivesSpace version 1.5.0 Release Candidate Available

Fri Apr 15 11:20:52 EDT 2016

Hi Brad,

First, thank you for the very impressive and highly anticipated new release. Harvard is eager to put it through its paces and to help find as many issues as possible before this becomes a production release.

Unfortunately, I do want to alert you that the time you have allocated for testing (5 working days) is inadequate and unworkable for Harvard. Among other things, next week is school vacation week in Massachusetts and key staff are out of the office most or all of the week.

As you know, the work involved in testing includes locating a server for installation, installing the software, loading it with useful data, and then involving archivists in testing, collecting results, and reporting them to you. I'm not sure about other institutions, but Harvard will need at least 3 weeks from today to install and test this new code, and provide feedback.

Is there any chance you could revise the timeline to this more manageable schedule?

-          Randy

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brad Westbrook
Sent: Friday, April 15, 2016 9:50 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Cc: Archivesspace_member_reps at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org; archivesspace at googlegroups.com
Subject: [Archivesspace_Users_Group] ArchivesSpace version 1.5.0 Release Candidate Available
Importance: High

[Reposting with corrected URL]

[Description: Macintosh HD:Users:samheartsart:Desktop:ArchivesSpace Logo.png]

ArchivesSpace is happy to announce the availability of a release candidate<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_releases_tag_v1.5.0-2Drc1&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=4JGa5VtTknXYK4u1_QXigeqoIeLZKZx44Vc_775eJ9Q&m=-swa07t9FQwsWbgpKxSPvnxwFOUOM7WKvEyPyy3J-_M&s=t_OcK0i1Q-y82SZlqstmb1RrEwjbB1ICB8JKW5GAzW0&e=> for the upcoming version 1.5.0 release.  This version will include the enhanced container management functionality that was originally developed as a plugin by Hudson Molonglo for Yale University. Adding this functionality to the core code of ArchivesSpace was the highest vote getter in the member voting on feature requests and bug fixes that was conducted last spring. Information on these enhancements is available here<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_blob_master_README-5FFEATURES-5F1.5.0.md&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=4JGa5VtTknXYK4u1_QXigeqoIeLZKZx44Vc_775eJ9Q&m=-swa07t9FQwsWbgpKxSPvnxwFOUOM7WKvEyPyy3J-_M&s=AMwKs7745JMoFlrYasBDMdj8JhwyQCZfVlseB1vEs_w&e=>. We are aiming to distribute a full production version, 1.5.0, once testing of the release candidate is successfully completed.

The timing of that release is highly dependent on community testing of this release candidate. Because integrating this functionality into the ArchivesSpace core code required changing the data model in certain areas, upgrading from a pre-1.5.0 version of ArchivesSpace requires repositories to plan for the upgrade, to conduct the upgrade and conversion to the new data model for containers, to review the  results, and, possibly, to remediate data either prior to or after the final conversion process. Because of all the variations in which container information can be recorded by repositories, it is impossible to know all the ways the data of repositories will be impacted. A number of members of the community have helped with testing incremental changes to this point. Now that we are nearing the production release, it is essential that we get solid testing data from a broader swath of the ArchivesSpace community to ensure that unanticipated adverse effects are eliminated as much as possible, or, on the other hand, to ensure us the conversion is working as designed.  Not only do we need to know if you encounter a problem or if your container data is not accurately converted, we also need to know if you were able to upgrade to the new version successfully.

Information on preparing for the conversion is available here<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_blob_master_UPGRADING-5F1.5.0.md&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=4JGa5VtTknXYK4u1_QXigeqoIeLZKZx44Vc_775eJ9Q&m=-swa07t9FQwsWbgpKxSPvnxwFOUOM7WKvEyPyy3J-_M&s=vTXy6CkK-v_vXna0zHWivXZb3EaVlI0P8ibkEYQuGWU&e=>. To gather testing data in a structured way, we have a feedback form<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spreadsheets_d_1HkPaLPZdXq0pmIFFDnGuWWlTfdBfAxnOkBSe4zFrWPk_edit-23gid-3D2016414678&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=4JGa5VtTknXYK4u1_QXigeqoIeLZKZx44Vc_775eJ9Q&m=-swa07t9FQwsWbgpKxSPvnxwFOUOM7WKvEyPyy3J-_M&s=K0WYNGWkzOBB6sUwdJ-1Z2kajXsIeFS3w6P7Rz6Tc2U&e=> at for you to record your results. We ask that all data be provided by April 25. This tight turnaround is essential to ensure that the production release can come out in a timely way, making both the enhanced container management functionality and other improvements to ArchivesSpace made since the last release in the fall available for use in institutions' production deployments of ArchivesSpace.

Thanks for your continued participation in making ArchivesSpace better. If you have any questions, or if you'd like help getting started with testing, please let us know.

The ArchivesSpace Program Team
Brad Westbrook
Christine Di Bella
Chris Fitzpatrick
Brian Hoffman
Laurie Arp

Bradley D. Westbrook
Program Manager
brad.westbrook at lyrasis.org<mailto:brad at archivesspace.org>
800.999.8558 x2910
678.235.2910
bradley_d_westbrook (Skype)
[cid:image003.png at 01CE734E.FD759D30]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160415/bc9c3fd0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9183 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160415/bc9c3fd0/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 7640 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160415/bc9c3fd0/attachment-0001.png>