Bug #6121

digitalobject:load task not working with identifier column

Added by Tim Hutchinson over 8 years ago. Updated almost 8 years ago.

Status:VerifiedStart date:12/13/2013
Priority:MediumDue date:
Assignee:Jesús García Crespo% Done:

0%

Category:Digital object
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:2.0.1, 2.1
Sponsored:No Requires documentation:

Description

Based on the code it looks like you should be able to use either information_object_id or identifier as the key for the digitalobject:load task.

But when the csv file has an identifier column, I get (in 2.x):
Invalid information_object id

The good news is that this functionality isn't currently documented. But it would be very useful :)

digi-object-sample-csv.png - Sample CSV file for digitalobject:load task using identifier (29.3 KB) Dan Gillean, 08/14/2014 11:34 AM

digital-object-load-options.png - options available on task - php symfony help digitalobject:load (45.8 KB) Dan Gillean, 08/14/2014 11:36 AM

digi-object-load-success.png - example of output message after successful digital object load (33.3 KB) Dan Gillean, 08/14/2014 11:36 AM


Related issues

Related to AtoM Wishlist - Feature #6291: digitalobject:load task - add support for description_ide... New 02/05/2014
Related to Access to Memory (AtoM) - Task #6524: Improve CSV import Won't fix 03/26/2014

History

#1 Updated by Dan Gillean over 8 years ago

  • Category set to Digital object
  • Assignee set to Jesús García Crespo
  • Target version set to Release 2.0.2

#2 Updated by Tim Hutchinson over 8 years ago

It seems this got fixed the day before I reported it, as part of other work (at least some 1.x changes got merged into 2.x then). In any case I successfully tested with the identifier column.

#3 Updated by Tim Hutchinson over 8 years ago

At least it's in the development branch - doesn't seem to be in the 2.x stable branch.

#4 Updated by Dan Gillean over 8 years ago

  • Status changed from New to QA/Review

Marking QA/Review so we can verify the fix here on our end, just to make sure. Thanks for updating this ticket, Tim!

#5 Updated by David Juhasz almost 8 years ago

Optimized script in commit:097dfdd640eeeb6ade303699515ee7413513305b

#6 Updated by David Juhasz almost 8 years ago

Fixed regression bug when importing by id in commit:586c680874d3f7139ffb3932693c2a6766c5248d

#7 Updated by Redmine Admin almost 8 years ago

  • Target version changed from Release 2.0.2 to Release 2.1.0

#8 Updated by Dan Gillean almost 8 years ago

Tested in qa/2.1.x.

Since this has not yet been well documented in AtoM 2 documentation, I will add simple notes here so we can refer to this when updating the docs, and for any public users coming across this issue.

Previous documentation for the digitalobject:load task could be found here: https://www.qubit-toolkit.org/wiki/CSV_import#Digital_object_load_task

This task allows a user to use a CSV to associate 1 digital object per 1 information object in AtoM. In the past the user had to know the information_object_id of the description to which they wanted to attach a digital object - which meant finding this information out through AtoM's GUI was not possible.

Now, instead of information_object_id, a user can use the identifier associated with the description instead (note: NOT the full reference code, even if reference code inheritance is turned on). You must ensure that the identifier is unique in your AtoM instance to ensure results - otherwise, we recommend using the information_object_id.

Works with a CSV formatted with 2 columns - identifer, and filename. Filename must include full path to the digital object. An image of a sample CSV file is attached, and appended visibly here:

By default in the task, indexing is turned OFF, so the user must re-index afterwards (php symfony search:populate)

Also available in: Atom PDF