- Must use Clever ID as a key identifier for all data types
- Must have a strategy for matching existing users to Clever data
- Must update data at least once per day (if data is updated upon login, this will suffice)
- Must archive records when data in Clever is unshared/deleted, and restore records if the Clever ID reappears (this includes Terms and Courses)
- Must be able to handle missing data fields for non-required (non-guaranteed) fields per Clever's data schema
- If application tracks historical data, history must be tied to student record
- Student-teacher associations must be preserved (if applicable)
- Which version of Clever's API are you using?
- Which field does your application use as the key identifier from Clever?
- What's the top-level or central record in your data model?
- What are the steps that need to be taken for a district to get set up with your application via Clever?
- Does your application use district-app tokens to sync data?
- Does your application need to run a sync to initialize data in the account before they can log in?
- How does your application handle missing fields which are not required / guaranteed in Clever?
- Does your application update data upon login or with a daily batched sync?
- Which Clever user types will have accounts in your application?
- Do you support a user type that has more access than teachers?
- How will you match Clever districts with existing districts in your CRM / database?
- How will you match Clever schools with existing schools in your CRM / database?
- Does your application match user records in order to preserve historical/progress data and accounts? If so, how?
- Does your application sync student-teacher associations from Clever?
- How often is a new sync triggered, and how?
- Do you update data on user login, using full data syncs, or using events?
- Can a teacher or admin do any of the following:
- Edit the permissions a user has or assign additional roles to a user
- Create users who are not managed by the Clever sync
- Create groups of students that are not managed by the Clever sync
- Split a section into subgroups
- Add or remove students from a section that is synced by Clever
- If you can do any of the above, will the changes persist until manually edited, or will the update be overwritten or deleted on the next Clever sync?
- What happens if a student moves between classes?
- What happens if a student moves between schools?
- What do you do if a record is deleted from Clever and no longer appears in the API?
- Can a record be restored after it has been deleted / archived?
- Does your application store progress data for display or reporting purposes (e.g. lesson completion, attendance, user-generated content, etc.)?
- Is there any case where progress data would be deleted?
- How do you handle semester or school year rollover?
- Which record types do you store/access?
- What happens when a user logs in for the first time?
- What happens when a user logs in after their account has been provisioned?
- Who kicks off the initial sync?
- Which record types will be synced?
- What access levels of administrator/super-teacher users do you support, and how do they map (or not map) to Clever user types?
- If a teacher is also an administrator in Clever, they will have two Clever IDs - one for the teacher record and one for the administrator record. How is this handled in your application?
- If you are syncing sections, is there any data on the section object that would change your application's behavior, or assign content or curriculum, etc?
- How do you handle users who aren't associated with any sections or student-teacher associations?
- How do you handle users that have multiple sections / student-teacher associations?
- How do you handle users that are associated with classes / teachers / students in multiple schools?
- Do you support co-teachers?
- If you support co-teachers, is there a maximum number of co-teachers that can be associated with a single class?
- Can you initiate a full data (non-events) sync if needed?
- Which records do you process events for?
We provide a 5-school data set that we built to help you test some of the tougher edge cases:
To see a full list of edge cases and the users that fulfill each one, check out Certification ISD Edge Cases.
Updated 6 months ago
When you're ready, submit for Certification!
|Submit for Certification|