/
2024-07-03 Advice on implementing Experience

2024-07-03 Advice on implementing Experience

Owned by Kidd, Denise
Last updated: Jul 08, 2024
2 min read

Russ’s notes

Jody, Paula, Colette, Russ Abshire (ULL)

  • 2 years to implement

  • Worked with Ellucian to develop enhancements

  1. Inventory of current links (Gibson)

    1. Identify custom portals that will not migrate to Experience

      1. Noel-Levitz questionnaire - could not create schemas or tables for custom cards yet

      2. TouchNet - housing deposits

      3. T2 Parking system

      4. Will provide list of custom apps that didn’t come over

  2. Understand what the transition would look like

    1. Ellucian card types - how they were used, when to use/when not to use for specific things (HTML, embed, etc.) - used HTML where possible

    2. Associated card types to the inventory of links for a point of reference of where to start

    3. These two took a lot of time, but worth it.

  3. Page management - content you want to display that can change (change the page instead of the card)

    1. For more information like training doc, lengthy content

  4. Max of 12 categories - associated categories to cards

    1. A card can only belong to a single category

  5. Roles

    1. Ethos role - generated via Ethos with vague queries - ULL has a matrix to identify what the queries pull

    2. IDP - identity provider Microsoft Azure

    3. ERP roles - GORIROL (more specific/detailed)

      1. Pulled directly from Banner - does not use Ethos

      2. API - user identity profiles

        1. Security groups/classes

        2. apiuser is the user that’s doing the query

      3. ‘Admin’ roles - hard query - specify experience admin is x ID, y ID, z ID

    4. UserID - Can put someone directly in the system and give them privileges, but this overrides any roles associated to that user.

  6. Single Sign-on

    1. Ellucian EEiD

    2. The category will only show up if you have access to the card. Card access based on role not access Category

  7. Companion app -

    1. need developer accounts that we self-manage

    2. iOS & Android

    3. Android - need to provide several documents to google for Android to get an organization based account. Can be finicky.

  8. Permissions is going to take some time and energy

  9. Delivered cards -

    1. Banner -

      1. Student-based (class schedule, grades, etc.)

      2. Tuition (TouchNet)

    2. CRM

    3. Third-party (DW, TouchNet)

    4. Integrations

      1. Insights/Data Connects

      2. Ethos

  10. SDK - software development kit

    1. Workstation based

    2. React/Node.js/javascripting

    3. 2 20-hour classes

 

User experience council - marketing chairs, IT co-chairs - who to include, building processes

Look into on-demand training

Soft roll-out Feb 5. Kept current portal available. Rolled out app on 5/31

Related content