[Archivesspace_Users_Group] ArchivesSpace v1.0.9 released

Tue May 13 09:39:14 EDT 2014

Hi again,

Also just got a couple of questions about there not being a v1.0.8 release. There actually was a v1.0.8 release, but it was an internal release that was issued to the public.

The reasoning is that is was a relatively minor release and some feedback indicated some users were not comfortable with the quick release cycle, since it required some technical work to perform the upgrade.

Regardless, you can go from v1.0.4 or v1.0.7.1 to v1.0.9 directly. Just be sure to run the setup-database script, as per the upgrade documentation.

best, chris.

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: Chris Fitzpatrick
Sent: Tuesday, May 13, 2014 3:25 PM
To: Archivesspace Users Group; archivesspace at googlegroups.com
Subject: RE: [archivesspace]

Hi All,

Just a quick update..

After doing an install on the v1.0.9 release, I noticed the build that was originally posted on the github site had a few dependencies that were packaging in multiple versions of the same library. All the tests were passing, but this can theoretically cause issues if the frontend, backend, public, and indexer apps are using different versions of the same library. It also unnecessarily bloats the distribution package.

I went back and nailed down most of the library versions, rebuilt the code,  and posted it to the github page.

Sorry this is a little unorthodox, but I wanted to nip this one quickly.

Let me know if you have any questions.

best, chris.

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: archivesspace at googlegroups.com <archivesspace at googlegroups.com> on behalf of Chris Fitzpatrick <Chris.Fitzpatrick at lyrasis.org>
Sent: Tuesday, May 13, 2014 12:47 PM
To: Archivesspace Users Group; archivesspace at googlegroups.com; archives at forums.archivists.org; atart at forms.archivists.org; archivesspace_tac_members at lyralists.lyrasis.org
Subject: [archivesspace]

(apologies about any cross postings)

The ArchivesSpace team is happy to release version 1.0.9<https://github.com/archivesspace/archivesspace/releases/tag/v1.0.9>.

Please see the documention<https://github.com/archivesspace/archivesspace/blob/master/UPGRADING.md> for information on how to upgrade your ArchivesSpace installs.

This release includes upgrading Rails to 3.2.18, which addresses an important security patch<http://weblog.rubyonrails.org/2014/5/6/Rails_3_2_18_4_0_5_and_4_1_1_have_been_released/>.  It is recommended that users update ArchivesSpace in order to apply this patch.

This release marks a transition from the work performed by Hudson Molongo <http://www.hudsonmolonglo.com/> on the project to the ArchivesSpace community. It was a pleasure working with James Bullen, Mark Triggs, Payten Giles, and Brian Hoffman, and we hope to continue to collobrate with them in the future.

There was a slight delay in this release, as we found there to be some performance bottlenecks affecting use of the Archivist Toolkit and Archon migration tools against large datasets. We believe we have mitigated these issues to a level that ensures that the data is transferred properly in a reasonable amount of time.

This release also supports use of the Archon to ArchivesSpace migration tool and includes the following features and fixes:

  *   FEATURE #70922880<https://www.pivotaltracker.com/story/show/70922880>: Update Rails to address CVE-2014-0130
  *   FEATURE #64190548<http://www.pivotaltracker.com/story/show/64190548>: As an archivist, I want the system to enforce a uniqueness constraint on the authorized name of an agent
  *   BUG #67092028<http://www.pivotaltracker.com/story/show/67092028>: EAD Converter chokes on some EAD tags being blank.
  *   BUG #54942792<http://www.pivotaltracker.com/story/show/54942792>: EAD import: some content being imported in two locations
  *   FEATURE #47693893<http://www.pivotaltracker.com/story/show/47693893>: As an Archivist I want Publish? to be set as false on everything when I first create a record
  *   FEATURE #65211392<http://www.pivotaltracker.com/story/show/65211392>: As a repository manager, I would like to export an EAD with numbered s.
  *   FEATURE #64905804<http://www.pivotaltracker.com/story/show/64905804>: As a repository manager, I would like display of title information to be consistent for all archival objects in the Public UI
  *   FEATURE #62805480<http://www.pivotaltracker.com/story/show/62805480>: As a repository manager, I would like to make "create / update subject and agent records" explicit in the group permission options
  *   FEATURE #65826898<http://www.pivotaltracker.com/story/show/65826898>: As a repository manager, I would like to have the option of including digital objects s in my EAD export.
  *   FEATURE #67289478<http://www.pivotaltracker.com/story/show/67289478>: Resources do not delete on cascade in MySQL
  *   FEATURE #47583999<http://www.pivotaltracker.com/story/show/47583999>: As an archivist, I want clearly-labeled buttons for adding events to Chronologies
  *   FEATURE #44934349<http://www.pivotaltracker.com/story/show/44934349>: EAC-CPF export: maintenanceAgency mappings / pulling repo context into exports
  *   BUG #64176304<http://www.pivotaltracker.com/story/show/64176304>: Unpublished component are being displayed component list in public UI.
  *   FEATURE #65829508<http://www.pivotaltracker.com/story/show/65829508>: As a repository manager, when I indicate a record (parent or component) should not be published, then all components contained within that record context (all children of the record marked "not published") should not be published or retrievable via searching.
  *   FEATURE #65211048<http://www.pivotaltracker.com/story/show/65211048>: As a repository manager, I would like the finding aid title to be required when providing a description of a finding aid.
  *   BUG #64828088<http://www.pivotaltracker.com/story/show/64828088>: MARCXML Import should allow a MARCXML record with date type = "s" to have a null second date.
  *   FEATURE #61361744<http://www.pivotaltracker.com/story/show/61361744>: Support importing of large sets of MARCXML records
  *   FEATURE #64190600<http://www.pivotaltracker.com/story/show/64190600>: As an archivist, I want the importer to match incoming records to existing agents if possible, creating new agent records if no match is found
  *   BUG #64175554<http://www.pivotaltracker.com/story/show/64175554>: Staff side searches are not constrained to selected scope
  *   FEATURE #51597537<http://www.pivotaltracker.com/story/show/51597537>: As an Repository Manager or Administrator, I want to be able to configure what appears in browse screens
  *   FEATURE #65588076<http://www.pivotaltracker.com/story/show/65588076>: Add REST endpoint to get ASpace Backend Information
  *   FEATURE #65587716<http://www.pivotaltracker.com/story/show/65587716>: Add REST endpoint to suspend indexer
  *   BUG #59985522<http://www.pivotaltracker.com/story/show/59985522>: Windows: application cannot resolve gem paths if pathname has any spaces in it
  *   FEATURE #64190840<http://www.pivotaltracker.com/story/show/64190840>: As an archivist, I don't want an agent to have two identical alternative name records.
  *   BUG #68437254<http://www.pivotaltracker.com/story/show/68437254>: Cannot save resource component that has attached digital objects.
  *   BUG #64855666<http://www.pivotaltracker.com/story/show/64855666>: Importing a set of MARCXML records results in the date statement for each MARC record being recorded in all of the MARC records imported from the set.
  *   BUG #66596734<http://www.pivotaltracker.com/story/show/66596734>: As a repository manager, I do not want suppressed records (accession, resource, resource component, digital object, and digital object components) to be "cast" to the public UI.
  *   FEATURE #65477970<http://www.pivotaltracker.com/story/show/65477970>: As a repository manager, I would like to change to "Indirect " the term "Inverted" now present in the Name Order enum list in the Name Form template
  *   FEATURE #65475942<http://www.pivotaltracker.com/story/show/65475942>: As a repository manager, I want personal names to import in Indirect order when occurring as such in the source record.
  *   FEATURE #64336538<http://www.pivotaltracker.com/story/show/64336538>: As an archivist. I want to be able to view digital objects in staff UI the same way they render in public UI.
  *   FEATURE #62787364<http://www.pivotaltracker.com/story/show/62787364>: Public UI should render index items in a way that allows users to navigate to the designated note
  *   BUG #68450066<http://www.pivotaltracker.com/story/show/68450066>: Event records are unlinked from context record when context record is updated.
  *   FEATURE #68863136<http://www.pivotaltracker.com/story/show/68863136>: Add Shutdown Hook that can be invoked in JVM
  *   BUG #65282410<http://www.pivotaltracker.com/story/show/65282410>: Am not able to suppress an accession record that contains either a linked agent or a linked location.
  *   FEATURE #65515468<http://www.pivotaltracker.com/story/show/65515468>: As a repository manager, I want to remove the "Dates" field from the Name Form template for Persons, Families, and Corporations.
  *   FEATURE #68989280<http://www.pivotaltracker.com/story/show/68989280>: Only display "dates" in agent records if data is present. If there is not data already existing, don't display the field.
  *   BUG #68543726<http://www.pivotaltracker.com/story/show/68543726>: Column control-group values are not correct (for rows 2 and higher) after a user has used the "Reorder Columns" feature
  *   BUG #69259490<http://www.pivotaltracker.com/story/show/69259490>: ARCHIVESSPACE_VERSION not found in Tomcat deployments
  *   FEATURE #65515152<http://www.pivotaltracker.com/story/show/65515152>: As a repository manager, I want to restrict date type in the Exist and Usage date templates to 1) Single date and 2) Date Range.
  *   FEATURE #68863168<http://www.pivotaltracker.com/story/show/68863168>: Improved LCNAF query
  *   BUG #70784798<http://www.pivotaltracker.com/story/show/70784798>: Fix performance issues with migration
  *   CHORE #66974808<http://www.pivotaltracker.com/story/show/66974808>: For digital object file display, remove the link between xlink attributes and display in public UI.
  *   CHORE #63339564<http://www.pivotaltracker.com/story/show/63339564>: Update JRuby
  *   CHORE #66533444<http://www.pivotaltracker.com/story/show/66533444>: Look at using saxerator for EAD converter

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/

--
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivesspace+unsubscribe at googlegroups.com<mailto:archivesspace+unsubscribe at googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20140513/b159e469/attachment.html>