ArchivesSpace v2.0.0 Release Candidate 1 Reports Testing
| Report/Export | JSON | CSV | XLSX | HTML | Notes | |
|---|---|---|---|---|---|---|
| Accession Production Report | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | JSON, CSV, XLXS bring back all accessions (whether or not processed or cataloged) and no summary information; HTML and PDF bring back ONLY summary info |
| Accession Receipt Report | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | All reports return only one extent (even when there are multiple) and the extent number in the JSON and CSV is in form "extentNumber": "0.18E2" which is unintelligible; |
| Accession Report | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | All reports failed with error Java::JavaSql::SQLException: Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_swedish_ci,IMPLICIT) for operation '=' ; a more explicit error message would be good - presumably one of the fields has a non-utf character, but what record is the problem in? I'll see if I can identify, fix and rerun |
| Accessions Acquired and Linked Deaccession Records | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | JSON; CSV, XLSX return brief info for all accessions and NO info about deaccessions - these versions of this report appear to exactly duplicate the accession receipt report, incuding wonky extent number; HTML, PDF reports actually work EXCEPT the summary total of deaccession material includes the total volume of accessioned material in addition to the volume of deaccessioned material - so the result is wildly wrong |
| Accessions and Linked Subjects, Names and Classifications | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | |
| Accessions with Inventories | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | |
| Accessions with rights transferred | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | |
| Cataloged Accessions | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | |
| Created Accessions | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | Results in a failed report message | |
| Digital Object table | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | used litchfield repository from pui test corpus for testing; conforms to description except missing title of linked resource |
| File Version List | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | used litchfield repository from pui test corpus for testing; json, csv, xlsx report contains only digitalobjectid, repoId, identifier, and digital object title; it doesn't actually provide any info about the different file version associated with a particular digital object; html and pdf contains identifier, do title, file version uri, file version use statement |
| Location Holdings | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | used yale repository from pui test corpus for testing |
| Location Report | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | used yale repository from pui test corpus for testing; technically this conforms but it includes only the identifiers of the linked accessions or resources not their titles |
| Name Records List | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Generates all name records, rather than "selected name record(s)." |
| Name Records and Non-preferred Forms | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | The HTML and PDF reports might be more useful if the name records were spit out in alphabetical order. JSON, CSV, and XLSX reports are not reporting non-preferred names. JSON is difficult to work with because of the number of records. The program I've been using to review the JSON file (Oxygen) keeps freezing when I open and scroll through the report, but when I load in a browser, it is much easier to view. |
| Processed Accessions | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | CSV and XLSC pull processed accessions across repositories, whereas the JSON, PDF, and HTML reports pull processed accessions from the repository from which I was generating reports. In our report description, we are ambiguous do not specify that reports would be coming from one repository or all, so for column D and E in this row, I've chosen "Results in a download-able file with intelligible data that DOES NOT conform to the report description" because I'm making an assumption that we want a report from the chosen repository. The data in the JSON file is for the most part intelligible, except for "extentNumber" which has added content that I'm not able to translate, e.g. "0.1E1." |
| Repository Report | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | We do not specify what fields users should expect in the repository report, but the fields in the report are consistent across report formats. |
| Resources and Deaccession(s) | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Only returns deaccessions generated in resource record |
| Resources and Instances List | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in crashing or stalling the service | Results in crashing or stalling the service | Resources and Instances List and Resources and Locations List have identifical descriptions. None of the reports that ran returned with location or instance information - looks like just a resources list. |
| Resources and Locations List | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Only HTML and PDF actually included location information |
| Restricted Resources | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | first 3 formats include all resources and level of restriction, not just collections with restrictions |
| Subject Records List | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | The description says "displays selected subject records" but all subject records display (I think). How would a user select certain subject records? |
| Uncataloged Accessions | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Displays all accession, not only unprocessed. HTML view very different than others. Extent need quantity at the top of the HTML report. PDF format for 1 accession per page is not good. It wastes too much paper. Sorry, not familiar with JSON format. |
| Unprocessed Accessions | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | It seems like these reports actually do list only the unprocessed collections. HTML has & show up. This report is very helpful because it shows unprocessed (I wished it showed processing status) AND cataloging status. CVS shows unprocessed and processed accessions but XLSX shows only unprocessed! |
| Unprocessed Accessions List | Results in a download-able file with intelligible data that DOES NOT conform to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Results in a download-able file with intelligible data that conforms to the report description | Unprocessed Accessions and Unprocessed Accessions List are totally redundant according to the description but this particular report is fantastic (an accessible amount of information and just the info I need) and I can see myself using this report very often! |