Shifting Replicate Research Fields into Entity
- Elizabeth Storrs
complete [nb: TUH faculty research interest fields are still app-scoped replicates ]
Slate Instance | TUH |
Requestor | Elizabeth Storrs |
Date | 7/1/2023 |
Status | COMPLETE |
Summary Description | move application-scoped research replicate field into Entity |
TUH Research Data
Based on this article, https://knowledge.technolutions.com/hc/en-us/community/posts/360056255411-Replicate-Blocks-and-Configurable-Joins I built this Research Form Export with Custom SQL query that returns one row per person, with all of their research experiences:
A variation on this query powers the research table in the old dashboard, which is built on the GSBS Reader Dashboard Portal:
The ultimate goal will be to replace the current dashboard with something that has liquid looping; the current step is to take a handful of data from the spreadsheet and make it something that can be uploaded into the entity fields.
This is all OLD DATA--there is no rush to move the older stuff over--we just need enough data for proof of concept for now.
Will need to clear all of the data and do a single upload once I am sure it works to avoid duplication--there is no unique id to match on, [and no need to create one, if we do them all at once.]
Thought: is there any reason to move them over? I can just inactivate the old fields, and move forward with these. The data will be there, should anyone ever want it, and eventually should be removed. Principle: do not go looking for work, plenty will find you anyway!
Note: TUH: Faculty of Interest field remains as three separate fields: