Search Results igs_as_anon_id_us_uk

Overview

The IGS_AS_ANON_ID_US table is a data object within the Oracle E-Business Suite Student System (IGS), which is noted as obsolete in the provided ETRM documentation. Its core function is to manage the assignment of anonymous identifiers to students for a specific assessment method, designated as "SECTION." This mechanism is typically employed in academic environments to support anonymous or blind grading processes, where an instructor marks student work without knowing the identity of the student. The table serves as a critical junction, linking a student's personal and academic enrollment information to a generated anonymous ID within a specific academic load calendar context. It is important to note the documentation explicitly states this table was "Not implemented in this database," indicating it may exist as a defined structure but without populated data or active use in a standard deployment.

Key Information Stored

The table's structure is defined by two unique keys and several foreign key relationships. The primary data points stored include identifiers for the student, their course of study, and the specific unit offering. The primary key (IGS_AS_ANON_ID_US_PK) is a composite key consisting of PERSON_ID, COURSE_CD, and UOO_ID, uniquely identifying a record for a student in a specific course and unit section. A separate unique key (IGS_AS_ANON_ID_US_UK) ensures the anonymity aspect is maintained, comprising the ANONYMOUS_ID itself along with the LOAD_CAL_TYPE and LOAD_CI_SEQUENCE_NUMBER, which define the academic calendar period (load calendar instance) for which the anonymous ID is valid. This design prevents the same anonymous ID from being reused within the same grading period.

Common Use Cases and Queries

The primary use case revolves around generating and retrieving anonymous identifiers for grading purposes. A typical process would involve a batch job, likely driven by a PL/SQL package, that populates this table at the start of an assessment period. Common reporting or operational queries would involve joining this table to student and unit offering tables to translate between anonymous IDs and real student identities after grading is complete. A sample query to retrieve all anonymous IDs for a specific course and load calendar would be:

• SELECT anonymous_id, person_id, uoo_id FROM igs_as_anon_id_us WHERE course_cd = 'MATH101' AND load_cal_type = 'SEMESTER' AND load_ci_sequence_number = 202301;

Conversely, a query to resolve an anonymous ID back to a student's details would join through the IGS_EN_SU_ATTEMPT_ALL or IGS_EN_STDNT_PS_ATT_ALL tables.

Related Objects

The table maintains strict referential integrity through documented foreign key relationships with core Student System tables. These relationships are essential for ensuring the anonymous IDs are assigned only to valid academic enrollments and calendar instances.

• IGS_CA_INST_ALL (Load Calendar Instance): Joined via LOAD_CAL_TYPE and LOAD_CI_SEQUENCE_NUMBER. Validates the academic period.
• IGS_EN_STDNT_PS_ATT_ALL (Student Program Attempt): Joined via PERSON_ID and COURSE_CD. Validates the student's enrollment in the specified course program.
• IGS_EN_SU_ATTEMPT_ALL (Student Unit Attempt): Joined via PERSON_ID, COURSE_CD, and UOO_ID. Validates the student's specific attempt at the unit offering section.
• IGS_PS_UNIT_OFR_OPT_ALL (Unit Offering Option): Joined via UOO_ID. Validates the specific unit section offering.

The primary key IGS_AS_ANON_ID_US_PK and unique key IGS_AS_ANON_ID_US_UK are the defining constraints for this table, ensuring data integrity for the anonymous grading process.