Add DIP object import task
|Target version:||Release 2.4.0|
|Google Code Legacy ID:||Tested version:|
Add task, based on David J's work, to import digital objects from an Archivematica DIP.
#3 Updated by Dan Gillean almost 4 years ago
- Status changed from QA/Review to Feedback
Hi Mike, can you add some testing instructions for this? I have figured out that the command is:
php symfony import:dip-objects dip
Help command outputs the following:
Usage: symfony import:dip-objects [--application[="..."]] [--env="..."] [--connection="..."] [--undo-log-dir[="..."]] [--audit] dip Arguments: dip The DIP directory. Options: --application The application name (default: 1) --env The environment (default: cli) --connection The connection name (default: propel) --undo-log-dir Directory to write undo logs to (default: ) --audit Audit mode Description: Process a CSV file to import digital objects from an Archivematica DIP to existing information objects in AtoM. The CSV file can be named anything, but must have the extension "csv" (lower-case). The CSV file must start with a header row specifying column order. A "filename" column must be included. Additionally, either an "identifier" or a "slug" column must be included (not both: one of these will be used to specify information objects to import to). The import script expects that Archivematica will have modified the filename so: a) The original object file has been converted to a derivative with a corresponding extension ("jpg" for example) b) A UUID has been pre-pended to the filename (for example: "815da5cf-f49f-41f5-aa5d-c40d9d4dec3c-MARBLES.jpg") Note: Filenames must be unique (without UUID) to avoid colliding on import. The undo-log-dir option can be used to log which information objects have digital objects added to them. This log can be used, in event of an incomplete import, to either establish where the import stopped or to manually remove the imported digital objects. Undo logs contain two columns: the ID of the information object to which objects have beem imported and the DIP directory the objects were imported from. The audit option can be used to verify that all objects specified in a DIP's CSV file were imported. If any are found to be missing the object filename will be output.
What I need clarified:
- the dip argument: is this a path to the directory where the dips live, or a path to the csv file that tells AtoM where to find the dips?
- Do the dips have to be unzipped then, so they are just dip objects not in a package? (e.g. a bunch of archivematica jpgs, mp3s, etc)
- If the path is the to csv, maybe we should update the help instructions to indicate this - e.g. path/to/import-dips.csv or something?
I think that should give me enough to test. Thanks!
#8 Updated by Dan Gillean almost 3 years ago
- Requires documentation deleted (
Documentation added to 2.4 branch in: https://github.com/artefactual/atom-docs/commit/cba0e45ff5d84b57d19d96a8237f5ed9afd65fe8