...
Certain academic information comes to students via the attending institution. This information includes enrollment, STDNT_ENRL field, and term activation, STDNT_CAR_TERM field. This information is created for students by a particular institution, so the keys to these tables include the EMPLID and the INSTITUTION field. There are some tables where the key structure does not include the INSTITUTION field, but INSTITUTION appears in the table anyway. An example of this is the academic program, ACAD_PROG. This academic information exists only because of the students’ relationship with a particular institution.
...
When joining two tables in query, the system will create a join on similar keys. The EMPLID from one table will be joined to the EMPLID of another table; INSTITUTION will be joined with INSTITUTION, etc. Because INSTITUTION, BUSINESS_UNIT and SETID are defined differently, query will not create a join between them. The query writer must do it. So if the query needs to join two records, one of which has INSTITUTION as a key, another with BUSINESS_UNIT, the code first_table.INSTITUTION = second_table.BUSINESS_UNIT must be added manually. In CUNYfirst, the INSTITUTION always equals the BUSINESS_UNIT and SETID. For example, if the INSTITUTION The example has illustrated below:
| Panel |
|---|
INSTITUTION = ‘BAR01’ (Baruch), then the BUSINESS_UNIT = ‘BAR01’ and the SETID = ‘BAR01’ |
...