Move rights and access controls into spreadsheet

[arwenhutt]

Descriptive summary

Materials within a single collection increasingly have different rights or access settings. Currently, since these are set in the Excel ingest form, they must be ingested in different (sometimes many different) batches. Instead of setting these at the batch level in the form, we would like to set them at the item/object level in the spreadsheet.

Rationale

Save time. Yay!

Related work

#264 (If approved) should precede this ticket, if not approved this enhancement can still be made

[lsitu]

@arwenhutt While looking into the Excel InputStream template xls_standard_input_template.xlsx, I see the following columns that haven't been implemented yet:
Access granted | Copyright status | Copyright holder | CC license

And we have the following additional fields for rights and access in the Excel ingest form:
Copyright Jurisdiction | License Begin Date | License End Date

And we also have the following licenses in addition to the CC license:
Public - granted by rights holder
UCSD - granted by rights holder
Restricted - by rights holder

Should we use a more general column name like License instead of the CC license header, which includes the license values above? Do we need to include columns Copyright Jurisdiction | License Begin Date | License End Date as well in the Excel InputStream template?

From the point of implementation, do you want to keep all the fields in the ingest form as default, while the values captured from the Excel file are to override those default values? If no corresponding header values found in the Excel source file, we'll simply apply the default value from the Excel ingest form. It seems like that may work better and it'll be consistent with the current implementation. What do you think?

@lsitu this is related to #264 (Decouple/simplify rights and access controls ). This might be a good opportunity to simplify the access control logic and move them into the spreadsheet. Let us think through your question above and get back to you (soon).

[lsitu]

@GregReser Thanks. Yes. It's related to #264 and I think we can think about them all together. And the implementation can be separate for these two tickets if we want to have the default values from the Excel ingest form.

@lsitu let's focus on #264 first then figure out how to implement that in the spreadsheet

[gamontoya]

@GregReser Is this waiting on you, or ticket #264

@gamontoya both tickets are related to the questions about metadata only policy, so when we get clarity on that I can move forward.

[gamontoya]

@GregReser Okay. You might want to inform Arwen of this since she was asking why there was no movement on these tickets.