There are a number of columns for which we should try to update types in the "merged" tables that drive CCKP. In most cases, the conversion is from a single value type to a _LIST type (which would also involve splitting a delimited string into a JSON array) — e.g.:
There are also a number of cases where we'd ideally use lists of entity IDs (ENTITYID_LIST), but this might not be possible through any of the clients right now. I was hoping this would be a simple fix, but I had it ended up being a more time consuming task (for me at least). @thomasyu888 or @andrewelamb (or anyone) — could you take a look at this?
There are a number of columns for which we should try to update types in the "merged" tables that drive CCKP. In most cases, the conversion is from a single value type to a
_LIST
type (which would also involve splitting a delimited string into a JSON array) — e.g.:.delim_str_to_json()
There are also a number of cases where we'd ideally use lists of entity IDs (
ENTITYID_LIST
), but this might not be possible through any of the clients right now. I was hoping this would be a simple fix, but I had it ended up being a more time consuming task (for me at least). @thomasyu888 or @andrewelamb (or anyone) — could you take a look at this?themeId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)consortiumId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)datasetId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)dataset
:STRING
->STRING_LIST
themeId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)consortiumId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)consortium
:STRING
->STRING_LIST
grantId
:STRING_LIST
->ENTITYID_LIST
(if possible)publicationId
:STRING_LIST
->ENTITYID_LIST
(if possible)themeId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)consortiumId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)grantId
:STRING_LIST
->ENTITYID_LIST
(if possible)publicationId
:STRING_LIST
->ENTITYID_LIST
(if possible)themeId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)consortiumId
:STRING
->ENTITYID_LIST
(STRING_LIST
OK)consortium
:STRING
->STRING_LIST