Develop Inquiry Tracking Entity and Page View
Slate Instance | TUH |
Requestor | Marny Mitchell, Laura Felch, UCM |
Date | 5/10/2024 |
Status | PENDING |
Summary Description | develop tracking system for layers of inquiry data |
[ADD LINK TO BOX FOLDER]
Detailed description of desired deliverable:
Basically, they want what Helen has set up for TUSMGP
Research:
*delete all data in person-scoped PHPD Program of Interest and PHPD Program of Interest - Communication Plan fields, add 'x', and inactivate. The fields can be deleted at some future point.
Found almost 30,000 records in the 'Inquiry Details' entity. Deleted all records in Inquiry Details Entity with PHPD as school; this left 30 who appear to have been entered administratively.
Most of those were students entered by hand from SACNAS 2022. Most of the fields on the event registration form are person scoped, and add data to the traditional person-scoped inquiry fields.
Although the registration form has been updated since this event (probably in 2023), these are part of the entity data because that the entity Maine Interest field was mapped their by mistake, which created an entity row for them.
GSBS uses
entry year
degree of interest
subject of interest
program of interest
NUTR uses
entry term
Be careful about this weirdly
Remapped NUTR Hubspot feed to go back to 7/1/2024…issue! Some programs work:
This was a straight mismatch in the original mapping--she should be PHD, so that is easy to fix,
But this is the mapping for the field of interest!
The person-scoped field was looking to NU_inquiry data, so changed the inquiry field to look at it, and made sure the mapping was identical.
Am getting the same results as before, with only some of the programs mapping.
When looking at the individual records
Its was the multi-value field that was messing things up:
Outcome:
Will require using only single-value scoped fields in the Entity. For NUTR, not a big deal, and I should build them their own section of the