Skip to content

AIPscan v0.8.0 beta

Latest
Compare
Choose a tag to compare
@mcantelon mcantelon released this 07 Feb 00:10
· 30 commits to main since this release
2f57c4c

This release includes a number of improvements and fixes:

  • #209: Fixed AIPs page performance issue

    Previously, results paging on the AIPs page was being handled client-side, by the web browser using Javascript. This required data for every AIP (matching the currently selected storage service and location criteria) to be retrieved from the database and included in the web page’s HTML. This made AIPs page potentially take a long time to load in web browsers.

  • #216: Fixed AIP page performance issue

    Previously, results paging on the AIP detail page, of an AIP’s files, was being handled client-side, by the web browser using Javascript. AIPscan now uses server-side results paging on the AIP detail page. Given that results paging on the AIPs page only displays up to 10 AIPs at a time the application now only sends data for these specific AIPs rather than all AIPs. This makes the AIP page load much faster in web browsers when a lot of AIPs exist in AIPscan’s database.

  • #13: Show active tab in navigation bar

    This is an ease of use feature that visually highlights, in the navigation bar, which section a user is currently working in. For example, if a user is on the detail page for a storage service then “Archivematica Storage Services” is highlighted, shown with white text rather than gray, in the navigation bar.

  • #217: Create tool to generate test content for AIPScan testing

    A CLI tool was added to allow developers to generate sample database content to make it easier to do performance testing and development in general.

  • #234: Fixed “Internal Server Error”, in the AIPs and Reports pages, when the database is unpopulated

    Previous versions of AIPScan had a silent failure when the database was unpopulated and so users were unaware that the database was unpopulated. This fix alerts users to the fact that information is either not being pulled from the storage space or that other potential issues are preventing AIPScan from capturing and displaying information.

  • #77: Added GUI element to largest files report to control number of files shown

    Previously, the largest AIPs and largest files reports would, by default, show only up to five results. The only way to alter this was to manually alter report URL parameters. This fix adds a web UI input component that lets users change the number of results shown more easily and obviously.

  • #23: Fixed issue with window.location.origin-derived paths nott working on sites where AIPScan is not hosted at the root url

    The window.location.origin values were used in Javascript URL generation for the reporter/reports and reporter/view_aips pages. The URLs generated would fail if AIPscan was being hosted at subpaths of a root url, e.g. example.com/dir/AIPscan instead of example.com/AIPscan. This issue has been fixed and will allow for AIPScan to be hosted at subpaths of a root URL.

  • #241: Add lock file functionality to fetch tool

    A CLI option was added to the CLI fetch tool to enable use of a lockfile. Usage of this option makes it easier to use a lockfile to avoid accidental, overlapping runs of the fetch tool (if scheduled to run automatically via cron, for example).

  • #149: Fixed issue with CSV exports not being easily sortable by size column

    Some CSV exports have human-readable size columns, but the values in these aren’t easy to use for sorting purposes. These CSV exports will now also include an additional size column where the size is expressed simply as a number of bytes, a more easily sortable value.