Content Comparison

Functional Requirements

• Athena to Slate SyncFeed
  • Create a source format to import Athena data.
  • Athena data will not populate students' opt-out lists. Therefore, create a portal that simplifies the process of setting students' message groups in Slate.

Technical Requirements

• Security and Access Management
  • Import users for launch
    • Alumni Relations - Admin and Staff
    • Program Admins
  • Define role-based security model and assign users to appropriate groups based on role
  • Roles needs to clearly separate the communications-centric needs of the Alumni and Programs from the Advising functionality
    • No student information beyond the contact details and population queries should be available to Slate+Alumni user group (unless there is administrative overlap in roles that should allow access) 
  Include program-level grouping to further segment access to program-specific student populationsSet the feed to check for a new file nightly.
  • The feed will update alumni's Athena fields in Slate.
• Slate to Athena Feed
  • Create a Slate query that exports any new additions to message groups (opt-out groups) each night.
  • Create a Slate query that exports all alumni message groups (opt-out groups) each week.
• Slate Athena Sync Portal
  
  • The Athena to Slate feed can only update alumni's Athena fields, not their message groups. Therefore, the portal  will compare alumni's Athena opt-out fields to their Slate message groups and provide a mechanism to change them either on an individual or group basis.

Technical Requirements

• Athena to Slate Feed
  
  • Create a source format with Athena data with the following fields

• Athena to Slate Opt-Out Sync Portal
  
  • Methods: 
    • Main screen: Provides a landing page for users. Uses a query and liquid template to make sure the user has permission to edit Athena data.
    • Process list: Provides a list of alumni whose records need to be updated. Uses the "Alumni with Opt-Outs" query to get the list of alumni with opt-out records.
  • Views:
    
    • Home Screen: Welcomes the user. Contains a button that directs the user to the Process List method
    • Process List: Provides a list or alumni whose opt-out records need updating:
      • The query gets the records of any students who have a "Yes" value for any Athena opt-out field OR a has any opt-outs on his/her record.
      • Liquid Template iterates over the rows checking to see if the record needs updating:
        • If the alum has a "Yes" value for CU Do Not Contact, 

Data Requirements

• Incoming Data
  • Create scheduled exports based on last modification date for the required data points in the following systems
    • SIS
      • This is already covered by the Advising project data feeds
    • Athena
      • Preferred email, address, limited demographics, and flags for communication restrictions captured at OAD
  • Create source formats and scheduled imports for all data noted above
  • Create manual formats and processes for importing any data not managed in source systems
    • None currently identified; though the idea is to support non-alumni imports, such as organization contacts
• Outgoing Data
  • Create scheduled exports for the following systems
    • Athena
      • Granular opt-out values based on the Athena integration project definition
• Managing Data
  • Create forms for adding/editing any manually sourced data points
  • Automatically imported records need to be updated in the system of record (e.g., Athena, SIS)
• Reports and queries
  • Audit queries to validate imported data
  • Determine best reports for leadership and users to validate and monitor performance

...