Skip to main content
CollegeSource Support

Multiple InstCDs


As more and more institutions move toward using multiple inst code (InstCD) values, they must consider how this change affects our applications and resultant changes that should be instituted. This document addresses some high-level functional and technical concerns and is intended as a supplement to more detailed technical documentation that currently resides per configuration.


Setting up Default Tables for Home Use, Institutions Using InstCDs

Default fields for home tables are useful for institutions using the InstCd field to separate campuses, colleges, or other divisions. Separate sets of fields exist to provide default information for the TA Table and the IREF Table.

Defaulting TA Table Target IDs (Funneling)

COM.TINSTID and TINSTCD define the default target IDs for the TA table. COM.USETARGET defines if and how to look for default tables with TINSTID/CD:

  • If USETARGET is blank, then uAchieve will not look for a default table.
  • If USETARGET is B, then uAchieve will look for a TA Table using TINSTID and TINSTCD values as the target institution ID. In uAchieve, these are the same values for InstID and InstCD used at login. This setting is useful for institutions that use InstCD to separate divisions, but have the same set of TA rules for all articulations. TA Tables need to be set up only once, with all divisions pointing to the correct InstID/InstCd combination under which the TA Tables are housed. 
  • If USETARGET is D, then uAchieve looks first for a TA Table using the InstID and InstCD of the individual division, then looks for a default table using TINSTID/TINSTCD if all courses are not articulated by the original TA Table. This setting is appropriate for institutions that use multiple InstCd values to separate divisions and has some division-specific rules with a large number of rules consistent regardless of division.

When using a default target TA Table, it is still possible to use DP Mask and/or have a default TA Table specified on the TA table.

Defaulting Target IREF Table IDs

For the IREF Table, there is a similar set of COM fields to provide the target ID.

Setting USEMREF to Y will instruct uAchieve to look for the target IREF Table using the values in MINSTID and MINSTCD. That IREF Table must be set up with the owner InstID/CD and the table’s Source ID and CD set to the values in MINSTID and MINSTCD. MINSTCD must have a value that isn’t blank.

If USEMREF is blank, no default table will be accessed.

This function is useful for institutions using different InstCD values when there is no need to have a separate IREF Table for each division that has a different InstCD. These defaults can be used in conjunction with the target TA Table defaults to keep an institution’s articulation data in one, unduplicated location despite using InstCD and storing student evaluations specific to each InstCD.

If an institution that has multiple InstCD values can use a single evaluation of the student’s courses regardless of the student’s InstCD, then uAchieve will also allow the student’s courses to be stored in a different InstCD, as though it were a default. Refer to the discussion of HINSTCD and HINSTCDSW in the COM Table section of these materials.



Let Self-Service Know About Multiple InstCDs

uAchieve Self-Service is currently the only web application that handles the "log-in" process for multiple institutions. Once logged in, navigating between applications carries over the logged in institution. You must let Self-Service know about the use of multiple InstCDs by defining them in the properties file. The different InstCDs that will be available follow a simple format: InstCDs are defined using an actual InstCD value plus a name to describe that InstCD to the user (e.g., "MU" and "Miami University"). The InstCD and name are separated by a colon and each InstCD/name pair are separated by a comma. Another option is to have a single InstCD/name pair by using the backslash (\) to continue the definitions onto the next line.

Formal Syntax

Below is the formal syntax:

<instcd1>:<name1>,<instcd2>:<name2>, etc...

Below is an example of several InstCDs configured:

CollegeSource.instcds=\ :Default College,\
TRA:redLantern College,\
CMP:Computer Design,\
MED:Medical School

Determine how Self-Service Should Determine the COM

In order to run an audit with the correct COM containing the InstCD you intend to run for, you need to determine how you want Self-Service to determine the COM. This configures which COM key should be used when running audits.

Strategies for Resolving the Appropriate comKey to use

In the Admin area, under Audits section, then COM settings define COM. Five different strategies are available for resolving the appropriate comKey to use when running audits (with example of each below):

  1. * sync - the comKey used will be the current user's InstCD
    1. Example: sync
  2. * dropdown - the comKey used will be chosen by the user from a drop-down
    1. Example: dropdown:999:DARSweb,BUS:Business,ENG:Engineering,WIP:No IP Courses
  3. * mapped - the comKey used will be determined by the user's InstCD via a lookup
    1. Example: mapped:TST:999,MU:MU,BUS:BUS,ENG:ENG
  4. * static - the comKey used will be the one configured
    1. Example: BUS
  5. * instidMapped - the comKey used will be determined by the user's InstID and InstCD via a lookup
    1. Example: instidMapped:TEST40-\ :SSIKE,TEST40-TST:SSIKE,TEST40-MU:SSIKE,TEST40-BUS:SSIKE,TEST40-ENG:SSIKE,007104-\ :SSFER

Define Security Properties

Security properties may need to be defined for users depending upon whether they should have access to only one InstCD or specific InstCDs. If users should access all, then no security properties must be defined.

  • Advisors will be given a choice at login if they have access to more than one InstCD.
  • Students may be allowed to have the same choice as advisors when logging in if just defined by InstCDs in the properties file. Giving students multiple properties using security properties will force them to choose at login; if they only belong to one, they will not have a choice.

If you only define multiple InstCDs in the properties file and do not use security properties setting but you want students to default to a certain InstCD (i.e., no choice at login) with the choice to change the InstCD only when requesting an audit, then set the following property:


  • Determines if students get a default institution from the configs or sees the select institution page.

    This does not apply to properties if a student has multiple institution properties; they will still need to choose an institution.



If you define multiple InstCDs in the properties file and do NOT want your advisors to have to choose at login, a new property was introduced (in 4.4) to allow for advisors to not have a choice:


  • Determines if advisors get a default institution from the configs or sees the select institution page.


  • Was this article helpful?