Guide to Contact Types in TrackMaster

Summary

The People list is at the heart of TrackMaster. It contains contact records for everyone with whom the center interacts - via events, consultations, communities, etc. Each contact has a specific type that encapsulates the relationship with that person. Thus, each contact can only have one contact type at a time, but they can change as people's relationship with the University of Michigan or with the center changes. This is a short guide to each contact type.

 

Contact Types

Contact types categorize entries in the People list. They can be assigned manually. There are also automated processes that can update the contact type for a person, for example, when they become members or when they are no longer employed at the university.

 

Internal vs. External

Contacts that have a valid UniqName are considered internal contacts for purposes of automations. Contacts that use a non-umich email address in place of a UniqName are external contacts, typically not affiliated with the university.

 

List of Contact Types

  • Member. A​​​​​​n official member of this center, as determined by the member engagement manager.
     
  • Prospective Member. Any internal contact that is eligible for membership who is not currently a member. Currently, that means graduate and medical students, post-docs, research scientists, and professors (excluding those in contract roles).
     
  • Alumni. Anyone who attended University of Michigan but has left the university (i.e., those marked as Alumni in MCommunity, with no other roles or affiliations).
     
  • Community Partner. A strategic external partner, such as community organizations, research collaborators from other universities, etc.
     
  • EFDC Leadership. Members of executive leadership for the center (currently, the center director and faculty leads).​​​​​​​
     
  • EFDC Staff. Team members of this center, whether full-time, part-time or temporary.
     
  • Peer-to-Peer Partner. School contact from schools running a P2P program. Excludes students.
     
  • U-M Communication Contact. Internal contacts used by the Communications team, primarily for promoting content and events.
     
  • U-M External Partner. Also known as Affiliate in MCommunity, these are external contacts not employed by the University or Michigan who have level-1 or level-2 access to university resources (e.g. study collaborators from other universities).
     
  • U-M Partner. A strategic internal partner, such as specific people in HITS or ITS, or members of MeTRIC.
     
  • U-M Staff. A University of Michigan or Michigan Medicine non-faculty staff member. Also includes student workers.
     
  • Undergraduate Student. A University of Michigan student at the undergraduate level. When viewed in MCommunity, this would be someone with any student role and no staff roles.
     
  • Vendor. External vendor contact (e.g. remote study management companies, wearable manufacturers, event video recording providers, etc.). 
     
  • Other. Default value when entering a new contact, when unsure or when adding in bulk. Contacts that use the type "Other" are picked up by an automated process to guess the correct contact type.
     

 

Automatic Updates to Contact Types (Advanced)

Different background automations, as well as bulk uploads, can trigger changes to the contact type field. However, the updates follow a specific hierarchy to ensure contact types can only move one way unless changed manually.

 

Contact Type Priority

  • Automated detection of contact types works by looking at the email address, job title, school affiliation, company, and information gathered from MCommunity and MS Teams.
  • Contact types are only changed one-way: Other -> ... -> EFDC Ladership. They are never changed the opposite direction automatically, but can be changed manually.Uploaded Image (Thumbnail)

 

Auto-Detection Rules

  • Member. This person is a member of the Membership group in the Groups list, or was added to the Membership group in MCommunity.
     
  • Prospective Member. Anyone who has a graduate or medical student role in MCommunity, residents (per job title), post-docs (per job title), research scientists (per job title), and professors (anyone with "Professor" in the title, excluding those that also say "adjunct").
     
  • Alumni. Those marked as Alumni in MCommunity, with no other roles or affiliations, and no department in either MCommunity or MS Teams. When a contact type is changed to Alumni, it is also de-activated in the People list and will no longer be updated or shown in reports.
     
  • Community Partner. Not auto-detected.
     
  • EFDC Leadership. Not auto-detected.
     
  • EFDC Staff. Anyone with the the "MM Eisenberg Depression" department listed in MCommunity or MS Teams, who is not already categorized as EFDC Leadership.
     
  • Peer-to-Peer Partner. Auto-detected for some local schools based on e-mail address (specifically the domain portion).
     
  • U-M Communication Contact. Not auto-detected.
     
  • U-M External Partner. Anyone with an "Affiliate" role in MCommunity but no "Faculty and Staff" role, who have an active account in either the University or Michigan Medicine MS 365 environment.
     
  • U-M Partner. Not auto-detected.
     
  • U-M Staff. Anyone with a "Faculty and Staff" role in MCommunity, and an active MS 365 account, .who is neither a student nor affiliate per MCommunity.
     
  • Undergraduate Student. Anyone with a "student" role in MCommunity, excluding those who are also graduate students and those who also have a "Faculty and Staff" role.
     
  • Vendor. Auto-detected for some mobile technology vendors only, based on e-mail address.
     
  • Other. Used when nothing could be auto-detected, unless the contact type is already set to something else.

 

Notes

  • None.

 

Resources

  • None.

 

About the Author

Gabriel Mongefranco is a Mobile Data Architect at the University of Michigan's Eisenberg Family Depression Center. Gabriel has over a decade of experience with automation, data analytics, database architecture, dashboard design, software development, and technical writing. He supports U-M researchers with data cleaning, data pipelines, automation and enterprise architecture for wearables and other mobile technologies.

 |   |   | 

 

Print Article

Related Articles (2)

This article is deep dive into MCommunity data and different ways to access it. MCommunity is the University of Michigan's public directory, providing information about people and groups. The directory information is often necessary for day-to-day research study management, day-to-day business operations at centers & institutes, and for automation.
This article describes the steps for adding new contacts to the TrackMaster Membership Tracking Tool on SharePoint.