As with any project, there are dependencies that need to be taken into account for project planning and timelines. The following are a list of core dependencies that will be helpful to be aware of as your institution works with your Stellic project manager to plan your implementation.
Configuration sheet must be completed before the Stellic instance can be created.
The instance must be created before Stellic creates the metadata file for SSO setup.
The institution will need to create the CNAME record if a .edu URL will be used before Stellic creates the metadata file (or a new metadata will need to be generated later and delayed access to the platform while the new URL is setup).
The institution must create user accounts for the Stellic team and identify primary attribute before SSO setup can be completed.
All data feeds must be validated initially against the values in the configuration sheet and standard formatting before they can be loaded by Stellic.
All missing configuration values identified in the feed validation process must be added before Stellic can load the feed data.
Catalog (program, concentration, and course feeds) must be loaded first.
Section/offering data can only be loaded after course data (sections include course codes)
SSO must be completed before Stellic can load student data into the instance (for security reasons)
Student enrollment data can only be loaded after sections are created so Stellic doesn’t create incorrect section connections to student enrollments; student program data is dependent on program and concentration values being loaded.
User data must be loaded before advisor and instructor names appear appropriately in the platform (will only display identifiers without names until then).
User data must be loaded before permission feeds can be established.
In addition, it may be helpful to note how each type of data impacts features available within the Stellic platform and the integration/onboarding activities that each enables.