[Archivesspace_Users_Group] Problems with ASpace reports

Fri Aug 7 01:13:13 EDT 2015

Hi Chris

We have had the same issues as Robin with the reports. We have tried to implement your suggested solutions below but now received the following error message which I've copied below. Any advice on this?

In addition, I have asked previously but have never received an answer - I wonder if there is any documentation on what criteria the reports use to identify records that meet the nominated criteria. For example what fields is used to indicate an unprocessed Accession and what field is used to indicate an uncatalogued accession?

Many thanks

Emma

[cid:image007.png at 01D0D122.90592940]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick
Sent: Thursday, 6 August 2015 9:16 PM
To: Archivesspace Users Group
Cc: Zalduendo, Ines; Wendler, Robin King; Della Monica, Ilaria
Subject: Re: [Archivesspace_Users_Group] Problems with ASpace reports

Hi Robin,

So, first you need to make sure you compiled your jasper reports on startup. To do this, edit the config.rb file to have:

AppConfig[:compile_jasper] = true

and restart ASpace.

This will compile the jasper jxml files ( which is most likely what's causing the "can't convert nil to String" errors)

Also, you'll need to look at both your application and database server and make sure you're not running into a performance issue. Reports can hit the database really hard, so the timeout errors you're seeing could be the result of your server running out of RAM.

In regards to the CSV and Excel and HTML files, yes I would say those are formatted rather poorly by default. You can edit this by modifing your Jasper reports using something like iReport or Jasper studio<http://community.jaspersoft.com/project/jaspersoft-studio>. Just be sure to recompile your reports.

For the parameters, yes this feature is going to be included in a future release. I believe those labels are artifacts from AT.

best, Chris.

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

________________________________
From:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of McElheny, Robin G. <robin_mcelheny at harvard.edu<mailto:robin_mcelheny at harvard.edu>>
Sent: Wednesday, August 5, 2015 5:55 PM
To: Archivesspace Users Group
Cc: Zalduendo, Ines; Wendler, Robin King; Della Monica, Ilaria
Subject: [Archivesspace_Users_Group] Problems with ASpace reports

At Harvard, we are having major problems with the reporting functionality in the latest ArchivesSpace release. We have tested the reports in our own installation and in the ASpace sandbox with very little success. See below for more details.

We didn't see any issues in JIRA that reflects these problems. Has anyone else encountered them? If so, have you resolved them - and how?

Record selection issues:

  *   The Accessions Acquired and Accessions Production reports supposedly allow for specified time periods, but no date parameters show up in the report user interface.
[cid:image008.jpg at 01D0D122.90592940]

  *   In other cases it is unclear how/where to select records for the report (e.g. Digital Object Record). No selection parameters appear in the report interface. Are we supposed to browse records, then select them using the check boxes, then generate reports?

Report format issues:

  *   In cases where we were able to download CSV and Excel reports (Accessions Cataloged, Accessions Deaccessions List, Accessions Inventory), we were unable to sort these reports because the formatting appears to be frozen. The output of the report does not match the file type. It is like getting a static document layered on top of a spreadsheet, rather than an actual spreadsheet.

  *   Xlsx downloads don't export uniform cell sizes, so Excel sorting returns a warning saying "this operation requires the merged cells to be identically sized"

  *   In order for the Xlsx downloads to be useful, each field should be in a separate column to allow tallying and sorting, but the ASpace downloads don't do this. Some examples:

In the case of the Accession Deaccession List Report, opening the CSV download in Excel resulted in a very messy, single column spreadsheet that broke data about one deaccesion across multiple rows. (Example: row 48= "Additional records of the League of Women Voters (Cambridge, Mass.),,,,,,1376,,," and row 49 = ",Accession Date:,,05/01/1968,Extent:,1.00 Linear_feet,,,,:").

Here is a screen shot:

[cid:image009.jpg at 01D0D122.90592940]

  *   Here's another example:

[cid:image010.jpg at 01D0D122.90592940]

  *   In the case of an HTML report, it displays page footers - odd for online display.

[htmlreport]

Report failure/timeout:

  *   We encountered many failures.
Example:
When we attempted to download an XLSX AccessionsAcquired report in the ArchivesSpace sandbox, we got the following message:

Internal Server Error (500)
Request Method:            GET
Request URL:     http://localhost:8089/repositories/4/reports/accessionsacquiredreport?lock_version=&format=xlsx

(TypeError) can't convert nil into String

You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus.

Another example:

[cid:image012.jpg at 01D0D122.90592940]

  *   We were unable to generate any successful Resource reports. All attempts to download reports in any format resulted in "Waiting for (server)" messages with no results.

Robin McElheny

Associate University Archivist for Collections and Public Services

Harvard University Archives

Pusey Library

Cambridge, MA 02138

Email: robin_mcelheny at harvard.edu<mailto:robin_mcelheny at harvard.edu>

Phone: 617-495-2461

Fax: 617-495-8011

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150807/52fdce87/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 56144 bytes
Desc: image007.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150807/52fdce87/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 16855 bytes
Desc: image008.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150807/52fdce87/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.jpg
Type: image/jpeg
Size: 59883 bytes
Desc: image009.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150807/52fdce87/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.jpg
Type: image/jpeg
Size: 37229 bytes
Desc: image010.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150807/52fdce87/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.jpg
Type: image/jpeg
Size: 21318 bytes
Desc: image011.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150807/52fdce87/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.jpg
Type: image/jpeg
Size: 22259 bytes
Desc: image012.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150807/52fdce87/attachment-0004.jpg>