Feature #6525

Task #6524: Improve CSV import

Add CSV column for digital object URL to description import templates

Added by Dan Gillean over 6 years ago. Updated about 6 years ago.

Status:VerifiedStart date:03/26/2014
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

80%

Category:CSV import
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

Adds ability to link descriptions on import without a second task.

could this accept either a filepath or a URL, or would those need different column?

Remember that changes such as this will require the work to be done on both the RAD and ISAD templates, and that any useful documentation should be added somewhere.

bacon-digiObject-URL.csv Magnifier (5.1 KB) Dan Gillean, 09/16/2014 11:28 AM

example_information_objects_rad_digitalObject.csv Magnifier (6.02 KB) Dan Gillean, 09/16/2014 11:28 AM

History

#1 Updated by Dan Gillean over 6 years ago

  • Assignee deleted (Mike Cantelon)

#2 Updated by Mike Gale over 6 years ago

Allow digital object URI download ability is present in the XML import, but not currently in CSV. The method is found at the following locations, and could be reused in the CSV import:

#3 Updated by Misty De Meo over 6 years ago

could this accept either a filepath or a URL, or would those need different column?

I would rather avoid the extra magic and do it as separate columns.

#4 Updated by Misty De Meo over 6 years ago

  • Status changed from New to QA/Review
  • % Done changed from 0 to 80

This is complete in the dev branch dev/issue-6525-digi_object_csv.

While the digital object load task supports multiple digital objects per given information object, by duplicating info objects (to maintain a 1:1 mapping between info objects and digital objects), I didn't do that here. I decided it made more sense to maintain a 1:1 relationship between rows in the CSV and information objects created.

This has columns for both import via URI and import via path, but they're mutually exclusive, and only the former is used if both are present.

#5 Updated by Misty De Meo over 6 years ago

  • Target version changed from Release 2.2.0 to Release 2.1.0

#6 Updated by Jesús García Crespo about 6 years ago

  • Target version changed from Release 2.1.0 to Release 2.2.0

#7 Updated by Jesús García Crespo about 6 years ago

  • Target version changed from Release 2.2.0 to Release 2.1.0

#8 Updated by Jesús García Crespo about 6 years ago

  • Assignee set to Dan Gillean

#9 Updated by Dan Gillean about 6 years ago

A regression in #6989 is keeping me from testing this for the digitalObjectURI, but I have tested it locally for the digitalObjectPath, and it works great. Once the regression is fixed, will test again one more time for path to confirm.

#10 Updated by Dan Gillean about 6 years ago

  • Status changed from QA/Review to Verified

Rigorously tested - works great! As Misty says, if both a URL and Path is included, the import will prefer the URL, rather than stopping the import and throwing an error.

#11 Updated by Dan Gillean about 6 years ago

Attaching a blank RAD template CSV that has the 2 new columns added (you can insert them just after publicationStatus), as well as a silly sample CSV for a cute bacon fonds.

Also available in: Atom PDF