Task #6524: Improve CSV import
Add CSV column for digital object URL to description import templates
|Assignee:||Dan Gillean||% Done:|
|Target version:||Release 2.1.0|
|Google Code Legacy ID:||Tested version:|
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.
#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:
#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.
#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.