You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should seek to enable the pipeline being queried to ask the storage service for the correct AIP Store location, for example if the following is configured in my storage service:
Then the location (I believe) needs to look like:
/var/archivematica/sharedDirectory/www/AIPsStore
However, the re-ingest process via the dashboard might need to be looked at in more detail to understand if its behaviour still works as originally intended. The docs need to be improved to make the functionality clearer, see here for an example where a request using a JSON body does not seem to be acknowledged as expected.
From @ross-spencer on June 18, 2018 15:15
An example re-ingest query looks like this:
When it is run however, the following 404 can be seen (with a Django test configuration):
The path Archivematica is looking in for the AIP is:
[Errno 2] No such file or directory: u'/var/archivematica/sharedDirectory/tmp/rein_1'
And it can be seen in the source code that it will always add
'tmp'
as part of the URL being queried.https://github.com/artefactual/archivematica/blob/0af67bee24acf19e62cbb3ada28356393bb9e400/src/dashboard/src/components/api/views.py#L547-L561
The workaround for this is to use the Storage Service Reingest method documented here:
NB. we can only automatically approve a full-reingest, not partial or meta, see: artefactual/archivematica#1145
We should seek to enable the pipeline being queried to ask the storage service for the correct AIP Store location, for example if the following is configured in my storage service:
Then the location (I believe) needs to look like:
/var/archivematica/sharedDirectory/www/AIPsStore
However, the re-ingest process via the dashboard might need to be looked at in more detail to understand if its behaviour still works as originally intended. The docs need to be improved to make the functionality clearer, see here for an example where a request using a JSON body does not seem to be acknowledged as expected.
Copied from original issue: artefactual/archivematica#1143
The text was updated successfully, but these errors were encountered: