Colleague Implementation and Installation (UniData)

Astra interfaces with Colleague on UniData through the creation of SQL tables and virtual attributes for use as a translation layer between Astra and the Colleague UniData database files.

The creation of the SQL tables and configuration of virtual attributes must be performed by an administrator at the institution prior to the implementation of the interface.  This task is done using either Metadata Manager or VSG tools to convert Unidata files to SQL files.  The SQLized files will be housed on the same server as your Unidata instance and Ad Astra will pull the data using UniObjects commands.

An alternate option is to create a SQL database instance that replicates the data in your Unidata instance into a format that looks like a Colleague SQL instance using Ellucian Colleague DataOrchestrator.  Ad Astra can provide the table and column names needed to run this tool.  This option will require the DataOrchestrator tool, an administrator to run the tool, and a SQL Database server to host the SQL database instance.  If this is done, regular replication is required to make the data as current as possible. The Astra Schedule  function of writing room assignments back to Unidata cannot be used as this connection will not be direct to Unidata. The room assignment export feature can be used with a text file export integration if this SQL option is used.

Make sure to configure fields as single value fields unless otherwise noted and make sure virtual attribute notation and syntax matches the help examples exactly (ex:STU_TYPES instead of STU.TYPES).

 

Interface Preparation

The following steps must be performed to configure the interface between Colleague on UniData and Astra: See Astra Schedule Tables, Platinum Analytics Tables, HESI Tables for a list of the tables and fields that must be created.

Create the required SQL base tables from UniData files. The creation of the base tables can be achieved using VSG.

DatatelUniObjectsCourseImport.xml

  • COURSES_1
  • CRS_DEPTS
  • CRS_LOCATIONS
  • CRS_EQUATE_CODES
  • CRS_COREQ_COURSES

DatatelUniObjectsPgmRuleImport.xml

  • ACAD_REQMTS
  • ACR_CATALOGS
  • ACAD_PROGRAM_REQMTS
  • ACPR_ACAD_REQMTS
  • ACAD_REQMT_BLOCKS
  • ACRB_BUT_NOT_SUBJECTS
  • ACRB_BUT_NOT_COURSES
  • ACRB_COURSES
  • ACRB_FROM_SUBJECTS
  • ACRB_FROM_CRS_LEVELS
  • ACRB_FROM_DEPTS
  • ACRB_FROM_COURSES

DatatelUniObjectsPgmStudentImport.xml

  • STUDENT_PROGRAMS
  • X_STPR_ACPG_MAJORS
  • PERSON_ST
  • PST_ADMISSIONS_TESTS
  • STUDENT_PROGRAMS
  • X_STPR_ACPG_MAJORS
  • ACPG.MAJORS

Create the required virtual attributes. The table detail provided in step 1 includes the virtual attributes that must be created for each table.

Example for the virtual attribute called “ASTRA_SEC_ACTUAL_ENROLLMENT” for the COURSE_SECTIONS table:

:AE DICT COURSE_SECTIONS ASTRA_SEC_ACTUAL_ENROLLMENT
Top of "ASTRA_SEC_ACTUAL_ENROLLMENT" in "DICT COURSE_SECTIONS", 9 lines, 147 characters.

001: I
002: DCOUNT(SEC_ACTIVE_STUDENTS,@VM)

003:
004: ACT. ENROL.

005: 3R
006: S


Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.