1. Data Integration with Veracross Wednesday, June 23 rd Lauren Banks

2. What is data integration? Common data that exists across multiple systems Data integration automates the process of moving data from one system into another

3. Why integrate? Veracross is the master repository for data Facilitate data management Increase data accuracy Save time

4. What data flows into finalsite? Overlapping data that is common to both systems flows one-way from Veracross into finalsite Constituent data Academic data Calendar events

5. Constituent “Profile” Data Student, parent, faculty and staff, alumni data Name, email, phone, address, username, birth date, class year, job title flow into finalsite’s Constituent Manager Constituents are directed back to Veracross to make profile updates

6. finalsite’s Constituent Manager Some data will flow into finalsite via the integration Schools can choose not to map certain data points Additional data can live and be maintained only in finalsite The integration can be implemented with existing constituents in finalsite by simply “rekeying” importIDs

7. Academic Data Classes and rosters flow from Veracross into finalsite’s Academic Groups Assignments from Veracross are displayed in an element in finalsite’s Group Spaces Deep linking from finalsite facilitates navigation back into Veracross

8. Student Academic Group Space

9. Technical details Veracross API provides XML data over HTTPS Scheduled task on your finalsite server requests updated data hourly Records in finalsite are updated based on “importID” Veracross data points are mapped into corresponding data base fields in finalsite Constituent records are not automatically deleted from finalsite Phone and email data is deleted in finalsite if it no longer appears in Veracross

10. Calendar Events finalsite calendars can be configured to pull data via iCal feeds Calendar data is entered in Veracross and displayed in finalsite calendars. Data pulled into finalsite calendars can be further customized by specifying additional parameters such as “event_type” or “school_level” Scheduled task on your finalsite server polls your Veracross iCal hourly for any updates

11. Authentication and Single Sign-On Reduce password fatigue: Your constituents can log into finalsite with their Veracross usernames and passwords. Simplify end-user experience: Authenticated users can access Veracross from their finalsite portals without logging in a second time. LDAP authentication: Alternately, you can choose to authenticate your constituents via your local LDAP server.

12. How is the data used in finalsite? eNotify: email addresses will be synchronized with constituent records Veracross to ensure accuracy Online directories: Constituent email, phone, address, parent-student relationships flow into finalsite to populate your online directories Login credentials: Constituents can log into finalsite with their Veracross usernames and passwords. Calendars: instead of doing dual-entry of calendar data, configure your finalsite calendars to use Veracross iCal feeds. Academics: Pre-populate Group Spaces for teachers and students with your Veracross class and roster data.

13. New Development Summer 2010 Token-based authentication Deep links from finalsite portals and groups to Veracross Assignments pulled into Academic Group Space calendars Athletics teams and rosters Athletic events

14. Q & A