It is the campus’s responsibility to monitor for duplicates.  The more duplicates a campus has in CS the higher probability of incorrect matching to occur within CS. The same can be said about CHRS. The more duplicates in CHRS, the higher probability of incorrect matching occurring. 

Managing Duplicates in CHRS - This document provides campuses with guidance and best practices for identifying and resolving duplicate records.

Confirm Campus Solutions still has the standardized values and no modification has occurred. 

1. Name Type

2. Name Suffix

3. Name Prefix

4. Address Type

5. Phone Type

6. Email Type

7. POI Type

When CHRS, CS, or CFS is down for upgrade, maintenance, application of MPs, production campuses during wave implementation (several days) or some other reason, integration can be impacted for one or more campuses depending on the circumstance. To minimize the impact, campuses should proactively understand the potential effects and be aware of any responsibilities they may need to fulfill during such periods.

Database Maintenance - CHRS

Database Maintenance - CS

Database Maintenance - CFS

When CHRS, CS, or CFS is down for upgrade, maintenance, application of MPs, production campuses during wave implementation (several days) or some other reason, integration can be impacted for one or more campuses depending on the circumstance. When integration is impacted, it is recommended that campuses complete the integration checklist to ensure integration is working as expected when systems are returned. 

Campus Integration Validation Checklist (Without CMS)

Requesting CHRS environment to connect to CS environment - Guidance for production campuses on the steps to follow when requesting a non-production CHRS database connection to their own masked Campus Solutions environment for the new year.