Content Comparison

...

• Security and Access Management
  • Update permissions on all existing objects to ensure proper access based on role and need
    • Realms
      • Add Advising realm to all advising specific objects
        • Queries, Forms, Mailings
      • New objects should have appropriate realm assigned going forward, particularly new Alumni elements
• Communications / Deliver
  • Filters
    • Document existing filters that can be added to recipient list queries to refine the audience
    • Consider adding new filters or data points based on additional criteria (likely next cycle)
  • Ensure that the default sender alias is not defaulting to spsadvising for any alum/program comms
    • This cannot be set per user, and will require control through process documentation
  • Use the Designer functionality for all standard communications
    • Document workflows for mailing creation, recipient list selection, queuing for review, and sending
    • Test and validate send privileges for user roles
  • Components 
    • Coordinate with Web Dev team for next phase of component development (likely for next build cycle)
      • Focus on new designs, flexible branding, and responsive functionality
  • Chrome Extension
    • Plan for distribution to users, and document installation process
    • Refine functionality for improved usability
      • Better input for Events List component
      • Consider methods for getting images into the Slate library through the extension form
  • Model out the guardrails to ensure that emails are not sent directly, but go to the review queue for the Alumni team to review
    • If there is a way to only require this when there are Alums in the recipients list, that would be great, but may not be possible

...

• Database Ops / Feeds
  • Automate incoming data feed per technical specifications
    • From Athena (in development)
      • Requires opt-out data fields for all Athena categories that apply
      • Person-scoped fields
        • Athena ID
  • Automate outgoing data feed per technical specifications
    • To Athena
      • SPS opt-out values
      • Universal identifier (TBD - Athena ID, CUID, or UNI)
• Communications / Deliver
  • Filters
    • Consider adding new filters or data points based on additional criteria (likely next cycle)
  • Components 
    • Coordinate with Web Dev team for next phase of component development (likely for next build cycle)
      • Focus on new designs, flexible branding, and responsive functionality
• Landing Page
  • Create separate homepage widgets for the Alumni realm highlighting relevant information
    • Actual widgets TBD
• Communications / Deliver
  • Create template(s) in simple HTML to accommodate truly unique designs that fall outside of the designer components
    • May require content blocks for shared/reused messages
  • Templates
    • Create a simple universal template that can flex its layout depending on the components in use

...