ArchivesSpace Reports Testing, Sept. 2015
- BradleyW (Unlicensed)
- Nancy Enneking
- Carolyn Runyon
- Alston Cobourn
In the table below, in the columns corresponding to your name, please indicate if the report worked or did not.
Include In the “Comments” column any information that explains how a report failed or how the user experience might be improved for a report that works.
Report Name | Testers | Comments | ||||||||||||
| Alston- all testing in test site on several repositories | Brad | Brenda | Carolyn (Testing on UTC's ArchivesSpace hosted by LYRASIS)
| Nancy
| Nicki |
| |||||||
| Works | Works Not | Works | Works Not | Works | Works Not | Works | Works Not | Comments | Works | Works Not | Works | Works Not |
|
| all export formats, internal server error |
|
|
|
| csv |
|
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun for over 30 minutes - gave up and logged out - no way to cancel |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun - 1 hour |
|
|
| ||||
| all export formats, internal server error |
|
|
|
| JSON | CSV export is not optimized to sort and analyze data. XLSX data is even more difficult to sort and analyze than the CSV export. The HTML export seems complex. I recommend stripping it down to a single table with the data so that it can be easily copy and pasted into an existing CMS. The PDF export is the best looking one, however, it would be nice to add some additional data to this on the cover page, e.g. Name of the Repository, Number of Results, Number of Linear Fee, etc. Otherwise, the cover page should simply be a header. |
| Afraid to try! |
|
| |||
| all export formats, internal server error |
|
|
|
|
| Spun |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun - 1 hour |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun - 1 hour |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun - 1 hour |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun - 1 hour |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error |
|
|
|
|
| Spun - 1 hour |
|
|
| ||||
| all export formats, internal server error |
|
|
|
| CSV XLSX HTML | JSON never results in a download. Receive the following error: SubjectListReport - #<Encoding::UndefinedConversionError: ""\xC3"" from ASCII-8BIT to UTF-8> | CSV works, but should get rid of page footer information, so that users can sort by Subject, Term Type, and Source without having to clean the data. It would also be nice to record the number of accessions, resources, and digital objects associated with each subject here so that repositories can report collection strengths. XLSX is a nice export if you want to print. In my opinion, it's unusable as spreadsheet that might be used to sort and count data for reporting. These HTML tables are a little too complicated. I suggest simplyfying for easy integration in existing CMS. I also think that the subjects should be links to the subject records on the public interface. Otherwise, the user still has to go back and manually link the content. The PDF is nice, but I'm not sure how the data is sorted. It's not alphabetically, which makes this document a little confusing to use. | csv |
|
|
|
| |
| all export formats, internal server error |
|
|
|
| CSV XLSX HTML | JSON never results in a download. Receive the following error message:
| CSV export demonstrates the need for parameters. I believe this report is most useful for individual subject headings, instead of a dump of all subject headings. If I'm using this report to generate a pathfinder, I also want a link to the collection record on the public interface. XLSX export is nice if you want to print. If I were printing this on demand for a patron in a research appointment, however, I'd only want to print a handful of applicable subjects, not all 31 pages of data for my repository. The HTML is nice, but, is terrible for plugging into a CMS like LibGuides. It would be nice to strip this down, somehow. PDF export will print well, but I think we should simply make the content on the title page a header or add some more information, including the name of the repository. Overall, this report doesn't offer any data, like the ability to rank subjects by number of attached resources, accessions, and digital objects in order to identify collection strengths and weaknesses. |
| Spun |
|
|
| |
| all export formats, internal server error |
|
|
|
|
| Spun for 30 minutes - gave up, logged out - no way to cancel; has spun overnight and timed out on a prior occasion |
|
|
| ||||
| all export formats, internal server error |
|
|
|
| pdf, csv |
|
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error |
|
|
|
|
| Error: AccessionsProcessingPlanReport - net.sf.jasperreports.engine.JRException: Error executing SQL statement for : accessionsProcessingPlan |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Error: AccessionsRightsTransferredReport - net.sf.jasperreports.engine.JRException: Error executing SQL statement for : accessionsRightsTransferred |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Error: AccessionsRecordReport - net.sf.jasperreports.engine.JRException: Error executing SQL statement for : accessionsRecord |
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
|
|
|
| |||||
| all export formats, internal server error | JSON
|
|
|
|
|
|
| The HTML format seems informationally useful. So too the PDF. | |||||
| all export formats, internal server error |
|
|
|
|
| Spun |
|
|
| ||||
| all export formats, internal server error |
|
|
|
| csv |
|
|
|
| ||||
| all export formats, internal server error | JSON |
|
|
|
| spun for 30 minutes -gave up - no way to cancel; has spun for over 4 hours with no result on a prior occasion |
|
|
| ||||
| all export formats, internal server error |
|
|
|
| pdf, csv |
|
|
|
| ||||
| all export formats, internal server error |
|
|
|
| pdf, csv |
|
|
|
| ||||
| all export formats, internal server error |
|
|
|
|
| Spun |
|
|
| ||||
csv, json, html, xlsx | pdf, java.lang.NullPointerException |
|
|
|
| ran a csv file but it incorrectly had no data | When generating PDF: error: CreatedAccessionsReport - java.lang.NullPointerException |
|
|
| ||||
csv, json, html, xlsx | pdf, java.lang.NullPointerException |
|
|
|
|
| Error running pdf: UnprocessedAccessionsReport - java.lang.NullPointerException |
|
|
| ||||
csv, json, html, xlsx | pdf, java.lang.NullPointerException |
|
|
|
|
| Error running PDF: UnprocessedAccessionsReport - java.lang.NullPointerException |
|
|
| ||||