Agenda

• Review Inquiry Details fields for Beth to add to Vet

Meeting Notes

Reviewed the inquiry details fields below.

Yellow = “core” fields that should be in all instances

Pink = fields that were created specific to TUSMGP that are old/no longer needed

Blue = “core marketing” fields that should be in all instances

• If research indicates that “Program Interest ID” can be replaced by Slate-delivered “External ID” then deprecate it in TUSMGP and do not add to “core” fields in other insiitances
• Beth will use TUF to create “core” inquiry details fields in a “clean” database
• Beth will add/update the inquiry details entity (fields and prompts) in TUH, TUV and TUF using TUP and notes from this meeting as a model
• We will have three categories of fields for inquiry details entities: core “basic” fields (e.g., program), core “marketing” fields (e.g. Vendor), and “special case” fields that are unique to one instance but might be useful in future use
• Helen will write documentation for how to use inquiry details fields and marketing reporting (“user guide” for clients, etc. to implement properly

Assigned Tasks

• Research if Slate-generated “External ID” field in the inquiry details entity table can be used in the same way the custom “Program Interest ID” field is currently being used by TUSMGP Elizabeth Storrs Nope--is not unique for merging.
• Email Matt G. to determine if Denodo feeds should be brand new queries or rebuild existing ones Elizabeth Storrs