[Archivesspace_Users_Group] ArchivesSpace v1.1.1 release

Tue Jan 13 14:14:49 EST 2015

Hi Kevin,

If you are able to complete one of the slow exports and send one of us
(Chris, me) the exported file, it will make it easier to diagnose the
problem.

Thanks,

Brian

On Tue, Jan 13, 2015 at 1:18 PM, Kevin Clair <Kevin.Clair at du.edu> wrote:

>  The collections that are problematic for us are the ones with extreme
> (many thousands) of archival objects attached to them, especially when
> those archival objects have a lot of subject headings.
>
>
>
> Our problems were on v1.1.0; I actually didn’t upgrade my local test
> machine until this morning, and so far the upgrade has been better about
> allowing me to work while an export is running, though the exports are
> still very slow.  -k
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Chris
> Fitzpatrick
> *Sent:* Tuesday, January 13, 2015 6:01 AM
>
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace v1.1.1 release
>
>
>
>
>
> Hi Kevin,
>
>
>
> Thanks, yes if you could give us something to look at that would be
> helpful.
>
> Does this one resource you're trying to export have an extreme number
> related objects ( instances, subject, etc) associated to a single object (
> like the resource or archival_object)? Also, is this still happening on the
> v1.1.1?
>
>
>
> b,chris.
>
>
>
> Chris Fitzpatrick | Developer, ArchivesSpace
> Skype: chrisfitzpat  | Phone: 918.236.6048
> http://archivesspace.org/
>     ------------------------------
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Kevin Clair <Kevin.Clair at du.edu>
> *Sent:* Tuesday, January 13, 2015 2:17 AM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace v1.1.1 release
>
>
>
> Hello,
>
> To jump in here, we've had at least one instance of an XML export for a
> large finding aid result in ArchivesSpace becoming totally unresponsive and
> us having to call to have it restarted. I don't know if we've had timeouts,
> as such, but it definitely results in very poor system performance if I
> request an XML EAD, either through the front-end or the API.
>
> I'm away from the office at the moment so I can't start one running to see
> the logs, but I can provide examples tomorrow if it helps. In any case I've
> been waiting for the background job solution before I do much more with EAD
> exports here.  -k
>   ------------------------------
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of
> Chris Fitzpatrick [Chris.Fitzpatrick at lyrasis.org]
> *Sent:* Monday, January 12, 2015 5:37 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace v1.1.1 release
>
>
>
> Hi Ben,
>
>
>
> Queuing export jobs has not been implemented yet.  However, the issue
> timeout of exporting large EAD files, I think, has only been for PDF
> exports of EAD files. Are you seeing timeout in XML EAD exports?
>
>
>
> b,chris.
>
>
>
> Chris Fitzpatrick | Developer, ArchivesSpace
> Skype: chrisfitzpat  | Phone: 918.236.6048
> http://archivesspace.org/
>     ------------------------------
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ben
> Goldman <bmg17 at psu.edu>
> *Sent:* Monday, January 12, 2015 4:04 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace v1.1.1 release
>
>
>
> Chris,
>
>
>
> I don't see it listed on the release page, so can you clarify whether
> issues with the EAD export via API that were raised in this listserv have
> been addressed with 1.1.1?
>
>
>
> Specifically, I believe there were noted some issues with mass export of
> EAD timing out because of records with huge amounts of instances attached,
> and some discussion of having the EAD export run as a background job as a
> solution.
>
>
>
> Thanks,
> Ben
>
>
>
>
>
> *Ben Goldman*
> Digital Records Archivist
> Penn State University Libraries
> University Park, PA
> 814-863-8333
> http://www.libraries.psu.edu/psul/speccolls.html
>
>
>  ------------------------------
>
> *From: *"Chris Fitzpatrick" <Chris.Fitzpatrick at lyrasis.org>
> *To: *"Archivesspace Users Group" <
> archivesspace_users_group at lyralists.lyrasis.org>,
> archivesspace at googlegroups.com
> *Sent: *Tuesday, January 6, 2015 2:36:11 PM
> *Subject: *[Archivesspace_Users_Group] ArchivesSpace v1.1.1 release
>
>
>
> Hi All,
>
>
>
> Below is a version of the release notification with correct link to the
> v1.1.1 release ( original was pointing to the previous release by
> accident). Sorry about any confusion.
>
>
>
>
>
> The ArchivesSpace team is happy to release version v1.1.1
> <https://github.com/archivesspace/archivesspace/releases/tag/v1.1.1>
>
> Please see the documention
> <https://github.com/archivesspace/archivesspace/blob/master/UPGRADING.md>
> for information on how to upgrade your ArchivesSpace installs.
>
> Please see the release page for a listing of all the features, bugs, etc
> for this release.
>
> Among the bug fixes is one that resolves issues involving Archival Object
> and Digital Object tree structures. If you've had issues with tree
> ordering and editing, please read the v1.1.1 specific upgrade
> documentation
> <https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.1.1.md> for
> information about re-sequencing components as startup process.
>
> Also please have a look at the documentation for the Public Formats
> plugin written <https://github.com/archivesspace/aspace-public-formats>
> by Mark Cooper at LYRASIS for exposing metadata formats in the public
> interface. This plugin is included in this release, but users will have to
> configure it to enable the supported formats.  This plugin will be most useful
> to organizations with small-sized resources that want to provide access
> to different assets in the public UI. However, it is not optimized for
> larger resources, such as EADs having many nested components. We are
> currently in the process of designing a queue system that will optimize
> exports of larger, more complex resources from both the staff and public
> interfaces, and we expect to include it in the next release.
>
> Thanks to all the volunteers on the ArchivesSpace User Advisory and
> Technical Advisory Committees, who have been vital to keeping ArchivesSpace
> development on track.
>   <http://archivesspace.org/governance>
>
> Let us know if you have any questions, comments, or concerns!
>
>
>
> Regards, Chris Fitzpatrick.
>
>
>
>
>
> Chris Fitzpatrick | Developer, ArchivesSpace
> Skype: chrisfitzpat  | Phone: 918.236.6048
> http://archivesspace.org/
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>

-- 
Brian Hoffman
brianjhoffman at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150113/560c1762/attachment.html>