-
**Expected behaviour**
No component in our system should maintain database transactions open for too long because it degrades the overall performance of the database.
**Current behaviour**
E.g. `…
-
**Expected behaviour**
The ingest continues without the need of any human to approve the jobs.
**Current behaviour**
When an AIP and DIP are part of the normalization procedure; and the Processin…
-
**Please describe the problem you'd like to be solved.**
We have an instance of ArchivesDirect and are accessing the DIPs that are being stored in Duracloud via our digital collections website. Hav…
-
**Expected behaviour**
Users should be able to execute partial reingest and have it complete successfully.
**Current behaviour**
It fails on Move metadata to objects directory job, in the Pro…
-
**Expected behaviour**
The Characterize & Extract microservice should run successfully on each file, performing each specified extraction tool.
**Current behaviour**
Raw JPEG files with a lot…
ablwr updated
5 years ago
-
**Please describe the problem you'd like to be solved.**
It's hard to know if a post store callback succeeded for a package in the SS and there isn't a mechanism to re-execute a callback if needed.
…
-
On Archivematica systems, the MySQL `Tasks` table can grow very big (several million records). When the MCP service is restarted the records with the null exitCode field are updated with the following…
-
**Version of the documentation**
All versions.
**Description of the issue**
There is a feature in the storage service, for protocol types that implement this, to [update_package_status](http…
-
**Describe the bug**
When a transfer that is a directory of files is uploaded to the MinIO "sips" bucket for processing, Enduro creates a separate processing workflow for each file in the directory…
-
In the Store AIP microservice, users may be given the choice of which location to store their AIP. The same choice is also available in the Admin / Processing configuration screen.
![screen shot 201…