Results for “igs_as_anon_id_ass”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AS_ANON_ID_ASS is a table in the IGS (Student System) product schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It holds the association between a person and an assigned Anonymous ID used specifically for the assessment method. In institutions that enforce blind marking or anonymous grading, assessors must evaluate student work without seeing the student's identity; this table is the cross-reference that makes that possible. Each row links a person (identified by PERSON_ID) to a generated ANONYMOUS_ID within a particular assessment context, so that marks, feedback, and results can be captured against the anonymous identifier and later reconciled back to the real student.

Because the entity records an association between two or more referenced entities (the person and the assessment/load context), the heuristic Data Vault classification mined from its foreign key structure is a link. This is a modeling suggestion rather than a physical implementation: the table behaves as an associative or intersection table whose natural grain is one anonymous identifier assignment per person, per assessment type, per load calendar instance.

Key Information Stored

The documented physical schema comprises 15 columns. The most significant are the identity and context columns that define the assignment:

• PERSON_ID — the person (student) to whom the anonymous identifier belongs; a core component of the primary key.
• ANONYMOUS_ID — the generated anonymous identifier used during marking and result capture.
• ASSESSMENT_TYPE — the assessment method or type for which anonymity applies.
• LOAD_CAL_TYPE — the load calendar type defining the teaching period context.
• LOAD_CI_SEQUENCE_NUMBER — the calendar instance sequence, completing the period context.
• SYSTEM_GENERATED_IND — indicates whether the anonymous ID was produced automatically by the system.
• Standard WHO and concurrent request columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE provide audit and traceability.

Two unique indexes act as documented business-key candidates. IGS_AS_ANON_ID_ASS_U1 (PERSON_ID, ASSESSMENT_TYPE, LOAD_CAL_TYPE, LOAD_CI_SEQUENCE_NUMBER) enforces that a person receives only one anonymous ID per assessment type in a given load instance. IGS_AS_ANON_ID_ASS_U2 (ANONYMOUS_ID, LOAD_CAL_TYPE, LOAD_CI_SEQUENCE_NUMBER) enforces that an anonymous identifier is unique within a load instance. The primary key constraint IGS_AN_ANON_ID_ASS_PK covers PERSON_ID, ASSESSMENT_TYPE, LOAD_CAL_TYPE, and LOAD_CI_SEQUENCE_NUMBER.

Common Use Cases and Queries

Typical reporting needs include reconciling an anonymous mark set back to a named student, auditing which students received anonymous IDs for a period, and verifying that no duplicates exist. A reconciliation query might join this table to person and assessment tables on PERSON_ID, ASSESSMENT_TYPE, LOAD_CAL_TYPE, and LOAD_CI_SEQUENCE_NUMBER. A duplicate-detection query would group by ANONYMOUS_ID, LOAD_CAL_TYPE, and LOAD_CI_SEQUENCE_NUMBER and filter for counts greater than one, mirroring the U2 uniqueness rule. Administrators also query this table to confirm that anonymous IDs were generated for a specific assessment type and load calendar instance before releasing marks.

Related Objects

• IGS_AS_ASSESSMNT_TYP — referenced by ASSESSMENT_TYPE; defines the valid assessment methods.
• IGS_CA_INST_ALL — referenced by LOAD_CAL_TYPE and LOAD_CI_SEQUENCE_NUMBER; supplies the calendar instance.
• Person and student records — joined via PERSON_ID to resolve the anonymous identifier back to a named individual.
• Assessment, mark, and result tables in the IGS_AS family — use ANONYMOUS_ID as the operational key during anonymous marking.