[Archivesspace_Users_Group] Non-Jasper Reports in latest dev release - broken?
Chris.Fitzpatrick at lyrasis.org
Thu Jan 28 10:47:29 EST 2016
Yes, you're right..these aren't working.
In the -dev release, reports are move to run as jobs rather than being streamed out. Would be fine, except the job is just dumping the output object using to_s rather than actually iterating over the data. Hence, the output files having something like "#<StringIO:0x693a9316>" (the object) rather than the correct data.
I've made a ticket here :
Should have a fix in the next release. Thanks! b,chris.
Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat | Phone: 918.236.6048
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Thursday, January 28, 2016 3:46 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Non-Jasper Reports in latest dev release - broken?
I'm testing the latest dev release but one (1.4.5-dev19) and am running into a problem with the built in, non-Jasper reports. Can anyone else confirm that the CSV and XLSX flavors are broken? The JSON and HTML flavors appear to work correctly. I've tested the built in repository_report and the created_accessions_report.
This is running without any plugins enabled to remove that potential complication.
The reason I found this is that we have a custom report that is not Jasper based (its a plugin) and the preferred format for export is xlsx. I can work around this by exporting JSON and converting, but that's a bit of a pain obviously. Jasper is also out at the moment as the report includes a user defined value to pass to the report and that appears to be a bit of a pain to implement at the moment.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group