Follow

DualEnroll.com Integration with Ellucian Banner

Introduction

DualEnroll.com exchanges data with the Ellucian Banner student information system using standard XML files placed on a secure FTP site.  The actual exchange of data is performed by one party uploading an XML file to the FTP site and the other party, in turn, downloading and processing the file.  This is done on a scheduled basis, typically once per hour.

There are three situations in which DualEnroll.com and Banner must exchange data:

  1. Banner provides DualEnroll.com with course and course section information.
  2. DualEnroll.com  provides Banner with student admission application information and receives back a student identifier or, alternately, links directly to the college’s online admission application and receives back a student identifier.
  3. DualEnroll.com  delivers a course registration request to Banner and receives back and indication of the success or failure of the request.

Available Source Code

A complete set of source code for implementing the integration of Banner with DualEnroll.com is available on the Ellucian Commons Community Source Shared Code Repository.  The integration was developed at DualEnroll.com customer Lake Michigan College and graciously contributed to the repository for the benefit of the Banner community.  While the source code represents a fully functional integration at Lake Michigan College, it may require modifications to adapt to the specific needs of individual Banner implementations.

The integration is contained in the project “DualEnroll/Banner Data Exchange” available at https://csicode.ellucian.com/gf/project/dualenrollexch/.  You must register for an account and log in to access the repository.  Click the “Files” tab to view the downloadable source code files.

A complete set of the XML Schema Definition (XSD) files and matching sample XML files used for the data exchange are available at: http://dev.dualenroll.com/schemas/v1/index.html.  An explanation of the details of each component of the data exchange follow.

Course and Course Section

Banner provides DualEnroll.com with a filtered list of courses and course sections available to dual enrollment students.  This might be a static data set requiring only a single exchange at the beginning of a term or it might be a dynamic data set updated, for example when a section becomes full.  There is also a related data set, always static, which maps college courses to high school graduation requirements.  This is optional and is used to allow students to filter available courses by those that will meet their particular graduation requirements.

courses.xsd is the schema definition and courses.xml is a sample of a valid data file.  Most of the fields are self-explanatory.  The “course-fee” field allows for multiple fee types and amounts based on student characteristics.  The “allow-high-schools” field allows the college to restrict a course section to a specific list of high schools.

course_mappings.csv is the correspondence of college courses to high school graduation requirements.  This is generally delivered as a spreadsheet created by the college registrar’s office or individual high schools.

Student Admission Applications

When a high school student registers with DualEnroll.com they are given a unique internal reference number.  That needs ultimately to be mapped to a student identifier in Banner.  That can be done in one of two ways.

Normally, DualEnroll.com displays a high school/dual enrollment-specific admission application screen, customizable for the college’s needs.  DualEnroll.com then supplies that information to Banner.  application.xsd is the schema definition and application.xml is a sample of a valid data file.  Again most of the fields are self-explanatory.  The ‘reference-number’ field is an identifier generated by DualEnroll.com to identify the student in a response. 

All responses from Banner, both for admission applications and for course registration requests, are supplied in a single file.  status.xsd is the schema definition and status.xml is a sample of a valid data file.  The ‘application-status’ section is the applicable response to an admissions application.  Banner, after processing an admission application, places a corresponding record in this file.  The ‘reference-number’ is the same ‘reference-number’ supplied by DualEnroll.com with the admission application.  ‘student-number’ is the verified existing or new student number supplied by the SIS, either matching a student from the application to an existing student, or admitting a new student.  The ‘admitted’ field indicates the success or failure of the application.  The ‘course-fees’ field provides the option of selecting different fee structures for different students.  Once DualEnroll.com processes a status.xml record matching a given ‘reference-number’ that record is removed from the application.xml file so Banner doesn’t process it again.

DualEnroll.com resubmits the application information for each new registration, even if the student has already been admitted.  For those subsequent registrations, the ‘student-number’ field is populated with the last value received from Banner.  Banner may respond with the same student-number or a revised student-number if, for example, a duplication is identified after the initial response. 

As an alternative to having DualEnroll.com display the application form, If the college has an existing student online admission application suitable for high school/dual enrollment students, DualEnroll.com can redirect to that online application.  Upon completion, the application can redirect back to DualEnoll.com with the URL including the Banner student identifier created for that student.  Or, to avoid any need for customization, the student can be directed to record and enter their student identifier directly into DualEnroll.com.

Course Registration Requests

When a student registers for a course, and when all approval and payment workflow steps have been successfully completed, DualEnroll.com provides Banner with a course registration request.  registration.xsd is the schema definition and registration.xml is a sample of a valid data file.  The registration request is a record placed in the registration.xml file.  Again the fields are self-explanatory. The ‘reference-number’ field is a unique identifier for this registration request created by DualEnroll.com.  For new registrations, the “action” field is set to “add”.  By default, DualEnroll.com supplies most of the course section and fee information as a cross check against erroneous registrations.

Banner responses to registration requests are supplies in the same file as admission application responses.  status.xsd is the schema definition and status.xml is a sample of a valid data file.  The ‘registration-status’ section is the applicable response to a registration request.  Banner, after processing a request, places a corresponding record in this file.  The ‘reference-number’ field identifies the registration request to which the response applies.  The ‘enrolled’ field indicates the success or failure or the registration.  In the event of a registration failure, the contents of the ‘comments’ field are included in the failure notification to the student.  Once DualEnroll.com processes a status.xml record matching a given ‘reference-number’ that record is removed from the registration.xml file so Banner doesn’t process it again.

Additional Data Sets

Additional data sets described by the forms.xsd and students.xsd schemas are used for additional capabilities and are not widely applicable.  Likewise, the ‘course-completion’ section of the status.xsd schema is not widely used.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk