ORCID data storage improvement

[taslangraham]

The issue highlighted the fact that we may need to add improvements to our ORCID feature to allow storage of additional ORCID information, e.g information about an individual ORCID item/deposit.

To enable this, I am suggesting the following adding to the database schema.

Introduce an orcid_records Table

We could introduce an orcid_records table that will store records for each ORCID entry. This table would have the following structure:

Column Name	Type	Description
orcid_records_id	int	primary key.
assoc_type	VARCHAR	ASSOC_TYPE_REVIEW_ASSIGNMENT or ASSOC_TYPE_AUTHOR.
assoc_id	int	The ID of the review assignment or author.
put_code	int	The ORCID put-code associated with the record.
user_id (optional)	int	User this record is related to.

P.S: Each item in ORCID has an assigned put-code which allows easy identification to perform an update/delete. See here & here for more info.

We could expand the table above to include columns for additional data. Additionally, we could introduce a settings table, orcid_records_settings, table to store more information about each ORCID deposit, if necessary.

At a minimum the settings table would have the following structure

Column Name	Type	Description
orcid_records_settings_id	int	primary key.
record_id	int	Foreign key reference to orcid_records table
setting_name	VARCHAR	Name of setting.
setting_value	TEXT	Settings value