帝王会所

The DARS team generally uses a naming convention when creating pseudo names. If you would like to ensure the correct pseudo name is being used for a particular requirement/sub-requirement, run an Administrative Audit with List All: Pseudo.

1. Go to the FAC 鈥�
   • Go to the Advising tab - DARS
   • Enter the student鈥檚 ID number and select Lookup
   • Select Request Administrative Audit

2. On the request administrative audit pop-up enter the student鈥檚 Plan Code; Catalog; and List All 鈥� Pseudo
   • It is rare, but there are situations where the List All: Full should be used. Here are a couple of situations where List All: Full may be useful:
     • If the pseudo name is needed for a requirement that is already fulfilled
     • If the pseudo name is hidden
       • If an administrative audit is run with List All: Pseudo, but the pseudo name is still not visible.
     • Otherwise, List All: Full should not be used. Exception processors run the risk of negatively impacting DARS encoding and setup.

3. Once the administrative audit has run, the audit will appear in the Administrative Audit(s) section on the DARS landing page.
   • To view the DARS, select View Month DD, YYYY Audit

*Note: Students cannot see the Administrative Audit(s) section.

4. Now, the DARS will display with pseudo names.
   • 1 Sub-requirement pseudo names
     • Exception processors will use this pseudo most frequently.
     • Sub-requirement pseudos always begin with $:
     • If multiple pseudo names are listed, use the first pseudo in most cases.
     • In example below (0MPHIL2): Can be used to add, substitute, or delete a course in the 鈥淥ther Requirements: PHIL 6901鈥︹�� section.
   • 2 Requirement pseudo names
     • This pseudo is rarely needed.
     • At the undergraduate level - this Pseudo applies to the major.
     • At the graduate level - this Pseudo may apply to the entire program, so proceed with caution.
     • In example below (0MPHIL): Can be used to require 2 sub-requirements instead of 3 (Core Areas, Other Requirements, and Thesis).
   • 3 Group pseudo names
     • This pseudo is rarely needed. These pseudo names typically have a 鈥淕R鈥� near the end.
     • In example below (0MPHIL1GR2): Can be used to add, substitute, or delete a course in the 鈥淎NCIENT鈥� group.

**Pro tip: Copy/paste the pseudo (without the $:) Most exception processing errors come from typos in pseudo names.

Note: all graduate-level pseudo names start with the number zero 鈥�0,鈥� not the letter O.

5. Other Administrative Audit Pseudo tips:
   • Do not use pseudo name that end in 鈥淩鈥�
     • These are reject-line pseudo names.
     • Reject-line courses and pseudo names are italicized and highlighted in red.
     • Used to exclude courses from a requirement.
   • Never use pseudo names that start with an 鈥淴L鈥�
     • These are X-line pseudos
     • X-line pseudos are only needed for the DARS encoders/programmers.
   • An asterisk (*) is a wildcard
     • In the example below, 鈥淢IS****鈥� means accept any course with an 鈥淢IS鈥� subject code.

The PeopleSoft (PS) pseudo search can be used to provide general guidance regarding the appropriate pseudo name for exception processing. Using this option requires an understanding of the DARS general naming convention. Understanding the general naming convention is helpful for other pseudo searches as well.

1. PS 鈥� DARS Pseudo Name Search

• The PS - DARS Pseudo Name Search can be found using the following pathway:
  • Custom Applications > Student Records > DARS Exception > DARS Pseudo Name Search

• Enter the student鈥檚 Plan Code and Catalog Year
  • Leave the radio button selected for 鈥渙rder as displayed on DARS report鈥�
  • Select Retrieve List

The DARS Pseudo Name Search displays the overall requirement pseudo names.

• In the example below, ADLGENLIB is the requirement pseudo.
  • Knowing the requirement pseudo would only allow the exception processor to make changes to the number of sub-requirements needed (2 SUB-REQTS in example below).

• Most exceptions require modification of sub-requirements (鈥淐OMPLETE 10 ADDITIONAL LIBERAL鈥︹�� in the above example).
  • To find the sub-requirement pseudo, the exception processor has two options:
    1. Run an Administrative Audit with List All: Pseudo
    2. Understand and apply the Pseudo Naming Convention

2. General Naming Convention for Pseudos

The DARS Team typically follows a naming convention when creating pseudo names. The naming convention is structured by Requirement, Sub-requirement, and Group.

1. Requirement = Requirement pseudo may be found in PeopleSoft Pseudo Name Search or by Running an Administrative audit.
   1. In example below: 0MPHIL
2. Sub-requirement = Requirement pseudo + 1, 2, 3鈥�
   1. In example below: 0MPHIL2
3. Group = Requirement pseudo + GR1, GR2, GR3鈥�
   1. In example below: 0MPHIL1GR2

Exception processors with DARS Dean-Level access in the Faculty and Advising Center (FAC) have the option of running a Sample Audit with a List All: Pseudo. This process is similar to the process of running an Administrative Audit. Sample audits differ from typical Administrative Audits in that they do not have student information populated.

1. Start by selecting DARS under the Advising tab in the FAC
   • Select 鈥淪ample Audits鈥�

2. The following must be entered to run a sample audit with pseudo names:
   • Plan Code (e.g., OR6922)
   • Catalog Year (e.g., 2024)
   • List All dropdown: Pseudo
     • Do not select 鈥淔ull鈥� from the list all dropdown.
     • Selecting 鈥淔ull鈥� provides an overwhelming amount of information about the DARS encoding.
     • There are rare situations where the 鈥淔ull鈥� option must be used to find hidden pseudo names.

3. Select Submit Request and the audit will display in the Sample Audit(s) section.