This feature creates a new endpoint for the storage service API. It will allow a client to make a request to the API to move an AIP from one storage location to another storage location (of the same type). The storage service is aware of the move so there is no need to re-index (compared to moving AIPs manually).

Archivematica 1.7 included user interface translation support (see PR 506). This work covered a majority of the user interface but did not include the text describing jobs executed as part of the microservices. Those text descriptions are held in the application database making it difficult to maintain multiple translations.

This change moves these text descriptions out of the database and into JSON files. This makes it much easier to add new translations and maintain them over time.

To address an issue with file identification we have implemented a change in how file identification tools are chosen in this release. Users now enable their chosen command (Fido, Siegfried or file extension) in Preservation Planning, and the processing configuration decision in the dashboard is now a simple Yes/No on whether or not to identify the files. This brings file identification more in line with other FPR rules and processing configuration decisions.

Instructions on how to change the identification command in the FPR are available in the Identification section of the Preservation Planning documentation.

Please note - if you have the file identification decision point set in your processing configuration, you need to reset it to "Yes" or "No" as it will default to "None" after upgrade.

Elasticsearch has been upgraded from version 1.x to version 6.x. This should improve performance and ease security concerns with the previous version of Elasticsearch. If you are upgrading Archivematica from a previous version, please be sure to follow the upgrade instructions in the documentation.