Page Comparison

...

Files are then stored in the transfer source, which can be thought of as a staging location for all files waiting to be processed through Archivematica and have been prepared for long term storage and access copy deposit into Avalon. This transfer source will be connected to Archivematica, and files can be discovered via the Archivematica dashboard.

Validation service call

Avalon Media System users who want to validate their Manifest files prior to moving through the Archivematica preservation process can test their Manifest CSVs by sending the CSV to an endpoint in the Archivematica API. 

Usage example: (assuming that path/to/Manifest.csv exists)

curl http://127.0.0.1:62080/api/v2beta/validate/avalon \
  --data-binary "@path/to/Manifest.csv" \
  --header "Authorization: ApiKey test:test" \
  --header "Content-Type: text/csv; charset=utf-8"

Note on above example: do not use --data, use --data-binary instead.

Response examples:

200 OK
(Response was valid)
{
  "valid": true
}

400 Bad Request
(Expect reason to include different validation errors, or that the file could not be found)
{
  "valid": false,
  "reason": "Administrative data must include reference name and author."
}

404 Not Found
(Validator was not found.)
{
  "error": true,
  "message": "Unknown validator. Accepted values: avalon"
}

This request can be performed manually, per manifest, or set to run regularly on all files in a folder using the cron service or another script scheduler.

Archivematica transfer and ingest initiation 

This step can be initiated via automation_tools or manually via the Archivematica dashboard, depending on how Archivematica is configured and the level of control users seek in the process. This begins the process of creating submission information packages (SIPs) and, later, archival packages (AIPs).