Infinite Campus Digital Learning Partner Integration

SameGoal is an Infinite Campus Digital Learning Partner. We recommend leveraging our Digital Learning Partner integration when possible, which includes demographics, flags, and reporting integrations. Using these integrations, districts can:

• Set special programs flags automatically in Campus
• Display completed plan documents when flags are clicked within Campus
• Eliminate manual double entry of Special Education and Section 504 state reporting data

Demographics integration is required for flags and reporting integrations. However, these latter integrations may be configured independently at the same or different times. To learn more, visit each integration step/method below.

• Add SameGoal as a Digital Learning application
• Demographics
• Flags
• Vertical Reporting
  • Running EMIS Extracts in Campus
  • Vertical Reporting FAQs

An administrative account in SameGoal is required for setup.

Add SameGoal as a Digital Learning application link

To add SameGoal as a Digital Learning application:

• Submit a Campus Support case asking to enable the SameGoal Digital Learning Partner integration.
• Once enabled, complete Step 1 in Campus to add SameGoal as a Digital Learning application.

Demographics link

About: This integration imports student and parent demographics from Campus into SameGoal nightly using a OneRoster 1.2 connection.

Considerations: This integration must be setup first before flags and reporting integrations may be used. It sets a "sourced id" from Campus for each student in SameGoal as their "Internal SIS Student Id" (used in those integrations).

If your district currently uses our outline link-based document viewer integration, it will no longer work after this demographics integration is configured. Your district should transition to the flags integration at the same time.

To setup demographics integration:

• If you have not yet done so, add SameGoal as a Digital Learning application
• In Campus:
  • Complete Step 2 to create a OneRoster connection.
  • Enter connection information in SameGoal (see below).
• In SameGoal:
  • Visit Settings > District Information.
  • Under the "Infinite Campus" section on this page, locate "Digital Learning Partner Nightly Demographics".
  • Enter connection information generated in Campus. This includes:
    • Base URL
    • Access Token URL
    • Client ID
    • Client Secret
• It may take up to 24 hours for this integration to run.
  • A good way to tell if this integration has run is to visit a student's "Basics" tab in SameGoal.
  • Their "Internal SIS Student Id" should be of format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
• If your district previously used SIF-based demographics integration, remove the SIF-based configuration. If both demographic integration methods are enabled, the SIF-based integration may overwrite OneRoster values. This will likely cause flags and reporting integrations to fail.
  • In SameGoal:
    • Visit Settings > District Information > Details.
    • Under the "Infinite Campus" section on this page, remove "SIF URL".
  • In Campus:
    • Remove the "IEPAnywhere" SIF zone located under System Administration > Data Interchange > Zones.
    • Remove the "SameGoal - IEP Anywhere" SIF agent located under "System Administration > Data Interchange > Agents.

Flags link

About: This integration automatically sets a flag in Campus nightly for each student in SameGoal that has a "Program Participation" badge. Program participation badges in SameGoal are calculated from completed documents for each special program.

When clicked, each program flag in Campus launches a secure display of the most recent plan document for that special program in SameGoal, thereby streamlining communication and collaboration.

This integration may be configured for all supported Special Programs in SameGoal, or separatedly (eg one at a time, with different cutover dates for each program). This is helpful in the case a district uses SameGoal originally for Special Education only, then expands SameGoal use to 504, etc over time.

Considerations: There are two main ways this integration may be configured:

• Option 1: Have this integration "take over" existing flags the district is already using for each special program (eg as of a specified cutover date, SameGoal is the owner and source of truth for this special progam flag in Campus).

  • lightbulb Tip
    If this option is used, districts should ensure all flags currently entered in Campus are reflected in SameGoal (eg student has completed documents in SameGoal "badge" the student in SameGoal. If certain groups of students never had documents entered in SameGoal, but had manually entered flags in Campus, these flags will be end-dated as of the cutover date when the integration is enabled.
  • lightbulb Tip
    This option should only be used if:
    • (a) The district has been using SameGoal at least one full year (so that a plan document is expected to have "badged" the student in SameGoal); or
    • (b) The district began using SameGoal less than a year ago, but did an initial key programs data load in SameGoal to bootstrap student program participation badges in SameGoal.
    • Said differently, any manually entered flag in Campus for a particular special program will be end-dated with the integration cutover date less one day if the student does not have a corresponding program participation badge in SameGoal.

• Option 2: Have this integration create new program flags.

  • The pro here is that the integration will not "touch" existing Campus flags.
  • The downside is that the district will then have two flags for each Special Program potentially (one managed by SameGoal, another managed manually).

To setup flags integration:

1. Determine which Special Programs to integrate. This integration currently supports:

• Special Education
• Section 504
• Advanced Learners
• K-4 Literacy

Each program flag may be included in the integration independently. For example, if your district wishes to enable Special Education immediately, then incorporate other program flags at a later date, that workflow is supported.

2. Configure flags. Flags must be configured in Campus matching SameGoal's naming convention:

• Special Education
• Section 504
• Advanced Learners
• K-4 Literacy

For each flag:

• If you want this integration to "take over" an existing flag (see Option 1 above):
  • Submit a Campus Support case asking to configure your district's existing program flag(s) (specify which) for SameGoal's Digital Learning Partner integration. Campus will:
    • Ensure the desired flag(s) are marked as active, flagged and Special Ed
    • Update the flag(s) to match SameGoal's naming convention
    • Grant SameGoal access to update these existing flag(s)
• If you want this integration to create a new flag (see Option 2 above), complete Step 5 in Campus.
  • lightbulb Tip
    Flags must be named exactly as stated above in Campus to ensure integration.
  • lightbulb Tip
    All flags used for integration must have the box "Special Ed" checked, even if the flag is for another program (think of the checkbox as synonymous with special programs).

3. Create an LTI connection. An LTI connection enables Campus users to view documents in SameGoal when a flag is clicked.

• In Campus:
  • Complete Step 4 to create an LTI connection.
  • When prompted for Configuration Information from the Partner Program information, enter:
    • Launch URL: https://samegoal.com/iep/lti/launch
    • Keyset URL: https://samegoal.com/iep/lti/jwks
    • Login Initiation URL: https://samegoal.com/iep/lti/oidc
    • Target Link URL: https://samegoal.com/iep/lti/launch
  • Enter LTI connection information generated in Campus into SameGoal (see below).
• In SameGoal:
  • Visit Settings > District Information.
  • Under the "Infinite Campus" section on this page, click "add Digital Learning Partner Document Viewer".
  • Enter the LTI connection information generated in Campus. This includes:
    • Public Keyset URL
    • OpenID Endpoint
    • Deployment ID
    • Client ID
    • Cutover Dates (for each special program)

4. Confirm integration. It may take up to 24 hours for this integration to run. Once it has:

• A flag in Campus should appear for each student with a matching program participation badge in SameGoal unless the student is not included in the OneRoster demographics integration (a good way to quickly tell is to visit a student's "Basics" tab in SameGoal, and verify their "Internal SIS Student Id" is a long string of format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX).
• If this integration was setup to take over an existing flag in Campus:
  • If a student has an open flag for this program in Campus as of the program cutover date entered in SameGoal, the open flag in Campus is end dated (as the cutover date less one day).
  • If the student in SameGoal has a program participation badge that starts on or before the cutover date, a new flag is added to Campus that contains the LTI launch URL).
  • The reason existing flags are one-time end-dated in Campus with the cutover date less one day is so that each flag, going forward, contains the LTI launch URL.

5. Remove outline-link based integration. If your district previously used outline link-based document viewer integration, outline links will no longer work.

• In Campus:
  • Remove custom authentication connections located under System Administration > Data Utilities > Custom Auth Utility.
  • Remove outline links located under System Administration > Custom > Outline Links.
• In SameGoal:
  • Remove "Return URL" for Infinite Campus located in Settings > District Information > Details.

Vertical Reporting link

About: This integration pulls state reporting data generated in SameGoal related to Special Education and Section 504 into Campus "on-the-fly" at report generation time. In Ohio, integrated reports include:

• EMIS GE, FE, GQ, FD reports
  • lightbulb Tip
    GQ includes only special education records
  • lightbulb Tip
    FD includes disability and 504 status
• Ohio Pre-ID Assessment report

Considerations:

• When this integration is enabled, all data in the reports run from within Campus listed above actually pull data from SameGoal "on-the-fly". Data from Campus is not included (except FD, which only pulls Disability Condition and 504 field field information from SameGoal).
• Therefore, all state reporting data should be entered in SameGoal at the point this integration is enabled. If some data was previously entered into Campus manually and not in SameGoal, "stub" documents should be entered in SameGoal that reflect data in Campus (so this data is included) and district workflows should be updated to be sure data is entered into SameGoal going forward.

To setup reporting integration:

1. Log in to SameGoal using an administrative account and select Settings > Data Exports > + add data export.
2. Enter the account information (first name, last name, email) for the person administering the API Account. This is also the person who would receive emails should errors occur. Then click "Add data export".
3. Leave the "SFTP Push (optional)" section empty and proceed to the "Endpoint Permissions" section below.
4. Click "+add endpoint" and select the stateReporting/fd endpoint. For each of the configuration options (eg: Limit, Offset, Sort, etc), select the "Allow caller override" checkbox. For the FD endpoint, in the "Replace Unknown Fields" section, also select the "Using '@' character" checkbox. Click "Update".
5. Repeat the previous step for all of the other state reporting end points (stateReporting/fe, stateReporting/ge, stateReporting/gq, stateReporting/ohioPreId).
6. Click the "Update data export" button at the bottom of the screen.
7. Check the email address entered in step two above. Accept the TOS and copy & paste out the clientID / clientSecret. Note: You must save the clientSecret during this step. It cannot be viewed again later.
8. Complete Step 3 in Campus to create a Vertical Reporting connection. Enter the Vertical Reporting credentials received from SameGoal when prompted.
   • Base URL: https://api.samegoal.com/v1/oh/
   • Token URL: https://api.samegoal.com/v1/token
   • Client ID & Client Secret from the previous step
9. To check the connection, run one of the reports listed above with Campus. All valid records shown within SameGoal for these reports should be reflected in Campus except when:
   • The student is excluded from state reporting (as marked in Campus). Exclusions in Campus can apply to a particular student, calendar, school or grade level.
   • A record entered in SameGoal does not fall within an enrollment period for the student entered in Campus.
   • The student is not included in the OneRoster demographics integration (a good way to quickly tell is to visit a student's "Basics" tab in SameGoal, and verify their "Internal SIS Student Id" is a long string of format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX).

Running EMIS Extracts in Campus link

To run the FD extract in Campus:

• Check "Pull data from SPED product integration".
• Check "Request additional 3 years of data from SPED product integration".
• Leave "Date Range" fields blank. These will not apply when "Request additional 3..." is checked.

To run the GE extract in Campus:

• Check "Pull data from SPED product integration".
• Enter a date range as desired.
• Do not check "Pull Prior IEPs/Evals" checkbox, unless you require 3 years of prior records (rare). NOTE: When "Pull Prior IEPs/Evals" is checked, date range filter will not apply to results.

To run GQ, FE, Ohio Pre-ID extracts in Campus:

• Check "Pull data from SPED product integration".
• Enter a date range as desired.

SameGoal makes data for the current FY, and up to 4 years prior available through the API.

Vertical Reporting FAQs link

Does the reporting integration create stub documents?

No. Stub documents are not required, and were only used in prior integration methods as a workaround for not having a better way to hook into the Campus reporting engine. Far better than stub documents with limited data, full plan documents can now be viewed from within Campus by clicking on the flag set by SameGoal.

Does the reporting integration include adhoc reports in Campus?

No. Only EMIS GE, GQ, FE, FD and the Ohio Pre-ID Assessment reports will be integrated. In speaking with districts regarding existing adhoc reports in Campus related to Special Education, nearly all reports have an analog in SameGoal. Because SameGoal is the canonical source of information about Special Education and other special programs documented in SameGoal by the district, these reports are better suited to be run in SameGoal.

This may require some process change at the district-level; primarily, some district users who have not previously had access to SameGoal may need a user account and brief training on running reports in SameGoal.

If your district has any adhoc reports in Campus that do not appear to be addressed by a report in SameGoal, please contact help@samegoal.com so that we may work with you to address.