Overview
Data is extracted from the SIS and transmitted to the Student Success & Engagement application using several data feeds. Student Success & Engagement accepts the data using one of two methods: via CSV files using Apache Drill, or via a Direct Database Connection (using queries within SS&E Accelerate or SQL Views). See the Connect Overview and Import Process articles for requirements and additional information.
The individual data feeds must follow the format requirements outlined in the SIS Import Definitions. Data feeds may be configured and customized using the Accelerate Configuration in order to follow the import definitions.
The details outlined in this guide are subject to change as Watermark processes and requirements change over time.
SIS Integration and Data Feed Implementation Process
Before beginning the SIS integration process, the Connect Server setup must be completed by the institution. The Connect Overview lists the server requirements.
The SIS Import Definitions article defines the import requirements for each data feed.
- Decide on Connect Method: CSV or Direct DB
- Configure Connect Server
- Data Integration Meeting
- Sprint 1 - Critical Feeds: Priority 1
- Working Session 1.1
- Working Session 1.2
- Sprint 2 - Required Feeds: Priority 2 & 3
- Working Session 2.1
- Working Session 2.2
- Begin Data Verification
- Reports & Training
- Sprint 3 - Optional Feeds & Wrap Up: Priority 4 & 5
- Working Session 3.1
- Working Session 3.2
- Complete Data Integration & Verification
- Integration Troubleshooting & Training
- Update feeds through Design & Build and beyond
(Make continuous updates to feeds as requested by System Admin team)
Each sprint includes:
- Institution drafts data feeds
- Two technical working sessions to review best practices, questions, challenges
- Feedback and iterative review process with Watermark Technical Services
Data Sheet
In preparation for building the data feeds, the Implementation Project Manager will share a Data Sheet to keep the project team aligned on the progress of the data feeds. A Data Integration ticket will also be created for communication about data integration, questions, notes, etc.
The Data Lead is responsible for keeping their progress and notes updates in the Data Sheet.
The Watermark Technical Services team will keep track of the feed progress and notes as well.
Data Verification
As feeds are being finalized and imported into SS&E, the Institution System Admin and Data Lead will verify that the data imported into SS&E is accurate and complete by comparing the data verification reports with the source data in the SIS and/or LMS. The reports contain many data points which can be used to identify patterns of missing data, inconsistencies, or other errors.
The Watermark Technical Services team will review the verification reports with the System Admin and Data Lead at the Reports & Training Meeting. This is the System Admin’s opportunity to resolve any data issues or questions before training begins.
System Admin and Data Lead:
- Identify sample students and staff for verification.
- Verification Checklist
- For each sample student/staff, verify that the data imported into SS&E is accurate and complete by comparing the data verification report with the source data in the SIS and LMS.
- Work together to identify and resolve any inaccuracies in the reports. Focus especially on patterns of missing/inconsistent data.
- Mark progress in the Verification Checklist (optional)
- If the Admin and Data Lead are unable to find a resolution to a data issue or inconsistency, the data lead should reach out to Watermark Technical Services for help via Data Integration ticket. Changes may be made to the Accelerate configuration or other solutions may be explored together.
To wrap up Data Integration and Verification, the implementation team will review the reports together to answer any remaining questions about data integration and to establish data management practices for the remainder of implementation and beyond.
Roles and Responsibilities - Best Practices
The institution's Data Lead is primarily responsible for the creation and maintenance of all data feeds.
Watermark Technical Staff may provide support, however the data is ultimately owned by the institution and can often only be changed by the institution's IT team. The institution should first try to solve any data feed inconsistencies internally between the System Admin and the Data Lead, and reach out to Watermark staff for additional support if needed.