Use course articulation data in queries when staff, students, or external systems need transfer credit information from Slate. This article focuses on finding articulation results, preparing those results for Deliver or portals, and exporting transfer credit data to a student information system.
This article assumes that course catalogs and course articulations have already been configured. For setup and matching criteria, see Courses, Transfer Credit, and Ongoing Classes.
📝 Note
Course articulation results appear only after the articulation process has evaluated the student's course records. If expected results are missing, confirm that the course data has been articulated before troubleshooting the query.
Before querying articulation data
Course articulation data depends on relationships between the student, the student's school course records, organization course catalogs, and organization-level course articulations.
Before building a query, identify the question the query must answer:
Staff review: Which students have evaluated transfer credit that staff should review?
Student communication: Which articulation results should appear in a Deliver mailing or portal?
SIS export: Which evaluated transfer credit records are ready to send to the student information system?
Exception review: Which students have course data but no matching articulation result?
Choosing the query population
Start with the population that matches the intended audience or downstream process. The exact query base and joins depend on your database configuration, but most articulation reporting starts from a student population and adds course-related exports.
Go to Queries / Reports.
Create or open a query for the students whose transfer credit data you need.
Add filters for the relevant student population, such as transfer students, enrolled students, a specific round, a specific term, or students with imported transcript data.
Add joins or exports for the student's schools, school courses, and course articulation results.
Run the query and review a small sample before using the data in communications, portals, or integrations.
Recommended exports
Include enough identifiers and result details for the query's purpose. For SIS exports, coordinate the export layout with the team that owns the receiving system.
Student identifiers
Slate reference ID or another person-scoped identifier.
SIS ID, campus ID, or another identifier required by the receiving system.
Name and email address, when the output is for staff review or Deliver.
Source course details
Source school or organization.
Source school identifier, such as CEEB or organization key.
Student course number, course name, credits, grade, and term or semester dates.
School course GUID or another stable course-level identifier, if available and needed for matching.
Articulation result details
Course articulation name or identifier.
Transferred institutional course number and course name.
Transferred credits or units.
Articulation status, review status, or posting status, if your process stores one.
Export control values
Export date, posted date, or sent-to-SIS indicator.
Error or exception status returned by the SIS, if your integration imports posting results back into Slate.
Term, career, campus, or academic program values required by the SIS.
Filtering articulation results
Use filters to keep the query aligned with the decision or process that depends on it.
For staff review: Filter for students with new articulation results, missing review status, or results created after a specific date.
For Deliver or portals: Filter for results that are appropriate for students to see. If the SIS is the system of record for posted transfer credit, distinguish evaluated credit from officially posted credit.
For SIS export: Filter for articulation results that are complete, reviewed, and not yet exported or posted.
For exceptions: Filter for students with source course data but no articulation result, or for courses that fail expected matching criteria.
⭐ Best practice
Use a separate query for each purpose. A staff review query, a student-facing portal query, and an SIS export query usually need different filters and exports.
Using query results in Deliver and portals
Course articulation query results can support student-facing and staff-facing communication.
Deliver: Use the query as a recipient list, and add exports or content blocks that summarize evaluated transfer credit.
Portals: Use a query or portal data part to show evaluated transfer credit, missing transfer credit items, or transfer credit review status.
Staff review: Use a query, report, or dashboard to show articulation results and exceptions that need follow-up.
📝 Note
If students can see articulation results before the SIS posts official transfer credit, label the portal or mailing content clearly so the status of the credit is not ambiguous.
Exporting articulation data to the SIS
Use a data export when articulation results need to be sent to the SIS for transfer credit posting.
Create a query that returns only articulation results that are ready for SIS posting.
Add the identifiers and transfer credit details required by the SIS.
Choose the query execution method that matches the integration process. A cumulative export sends all matching records each time. An incremental or differential export can limit output to new or changed articulation records.
Add the query to the appropriate integration in the Integration Center, or schedule the export according to your institution's data export process.
Track exported or posted results with a field, tag, interaction, imported SIS status, or another institution-defined marker so future exports include the correct records.
📖 Determining Your Data Export Process
Troubleshooting missing results
If a query does not return the expected course articulation data, review the data used to match the student course to the organization course articulation.
Confirm that the student's school record is associated with the correct organization.
Confirm that the student course number matches the organization course number used by the articulation.
Confirm that the student's semester start and end dates fall within the organization course date range, if a range exists.
Confirm that all requisite courses in the articulation are present on the student record when the articulation requires more than one course.
Confirm that the transferred courses and credit values are correct on the organization course articulation.
Confirm that the articulation process has run after the most recent course data import or update.