ucsdlib / damsmanager

DAMS Manager

Other

3 stars 1 forks source link

Batch metadata overlay: deliverable 1 #321

Closed ghost closed 5 years ago

ghost commented 5 years ago

Descriptive summary

Existing objects can be edited using a spreadsheet in a batch process form DAMS Manager

Rationale

We should be able to edit a spreadsheet generated by the batch export tool, then use it to overlay existing object metadata.

The spreadsheet should support all columns generated by batch export #301
Properties and values in the object are replaced with those in the spreadsheet
Multiple values in a cell are supported (“ | “ separator)
Pre-process validation: same as current Excel import
Reporting similar to current import reporting

Batch edit specification

Related work

322

323

324

Part of Batch edit functionality (epic) #309

lsitu commented 5 years ago

@mcritchlow I've added the following PRs to support batch metadata overlay for simple objects: https://github.com/ucsdlib/damsmanager/pull/338 https://github.com/ucsdlib/private_config/pull/17

Both PRs above are ready for review now. Thanks.

remerjohnson commented 5 years ago

Wanted to report something I encountered... the export from Batch Export contains columns that then fail pre-processing on Batch Import. The error is:

Execution failed:

Pre-processing failed: 

Excel source batchExport--401619965.xlsx - failed - 2019-07-12T15:20:16: 
* Found the following invalid column names: Note:local attribution; collection(s)

I realize this ticket said the validation should be the same as the Excel Ingest, so not sure how to address this. What do you think?

lsitu commented 5 years ago

@remerjohnson The headings validation is different for Excel Ingest and Batch Overlay, which contains additional fields above like Note:local attribution, collection(s) etc. @mcritchlow I have a private_config PR https://github.com/ucsdlib/private_config/pull/17 that will handle the additional fields. Could you review it when you get a chance? Thanks.