Academic Requirements Outlines according to the current and to the preceding academic year’s catalogue are posted in LOCUS at a link navigated to from the portal-page after login. AROs amount to a static listing of the information the Academic Requirements Report (ARR) is programmed to look for in students’ course-records, tracking their satisfaction of Core and other requirements, including the major(s) and minor(s, if any) they have declared. AROs offer the most accessible way to check the programming in LOCUS of majors and minors. Please recall that students are subject to the requirements programmed for majors and minors as of the time they declare them in LOCUS: students who declare a given major/minor in different academic years may be subject to different requirements for it.

The Academic Requirements Report is the function in LOCUS that reads students’ course-records so as to track their satisfaction of Core and other requirements, including the major(s) and minor(s, if any) they have declared. Students may check their own ARRs in their Student Centers in LOCUS; their registered Advisers may run students’ ARRs at the Advisee Student Center in LOCUS. Please recall that students are subject to the requirements programmed for majors and minors as of the time they declare them in LOCUS: students who declare a given major/minor in different academic years may be subject to different requirements for it.

Academic Units in the College of Arts & Sciences are either departments or interdisciplinary programs formally so constituted: the term refers to the organizational structure framing faculty-members’ relationship to the academic enterprises in which they participate within the College. Both departments and interdisciplinary programs oversee major(s) and/or minor(s), and some departments oversee interdepartmental major(s)/minor(s) jointly. Sometimes it is convenient to refer to the overseeing entities by an inclusive term.

An active course may be scheduled, and appears in all displays of the Course Catalog in LOCUS. An inactive course is not available for scheduling; inactive courses do not appear in Browse Catalog displays. Registration & Records inactivates a course either by making its “status” Inactive rather than Active, or by un-checking its “allow course to be scheduled” box, or both. The Academic Council has authorized requests to inactivate unused courses to be directed to the Associate Dean for Academic Affairs, for administrative action and reporting into Academic Council minutes: these requests do not require action by the Council.

• In the context of the CAS Academic Council’s collective oversight by faculty of curricular matters in the College, the term application may refer to a curricular request or to the standardized form on which the application is submitted for the Council’s review.
• A group of applications submitted together under a single Unique ID is called an application-package.
• The main types of curricular change requested in the College have evolved as application-types
  • New Major/Minor
  • Change in Major/Minor
  • New Course
  • Course Change
  • Permanent Tag and Inclusion in an Interdisciplinary Major/Minor
  • Permanent Cross-Listing and Inclusion in a Departmental Major/Minor
• Additionally, the CAS-AC DocFinity Platform is used for Temporary Tag/Cross-List Requests to credit a specific class-section of a course not otherwise included in the applicant academic unit’s major/minor, on a semester-specific basis. These requests are reviewed and approved by the Dean’s Office, not by the Academic Council.

Complete, accurate records make it possible to reconstruct intentions and understandings in force at the time curricular changes (among other things) were made, so that any problems arising later can be unpicked and corrected: the archival function of the CAS-AC DocFinity Platform, preserving the records of curricular review, is of vital lasting value to the College.

DocFinity is a web-based Enterprise Content Management System. The CAS-AC DocFinity Platform uses DocFinity to regularize and centralize the documentation with which the faculty of the College of Arts and Sciences, through the College’s representative Academic Council, oversees curricular change in the College. Consistent formatting of all the information necessary to evaluate curricular requests, advise on them constructively, pass them on for approvals needed beyond the College, and process them so they will operate smoothly as intended after they have been approved, facilitates efficient review, collaboration, and accuracy. Centralized, complete records clarify reviews and facilitate any problem-solving that may become needed later. The CAS-AC DocFinity Platform, containing as it does the complete documentation of the College’s review of curricular proposals, also serves as an archive of curricular approvals.

Class Component is the term used by Registration & Records to refer to different scheduling-units for different instructional modalities, under a single Course Number. At Loyola currently, many labs associated with lecture-courses are coded as separate, co-requisite courses: for example, our fictional Department of Forestry might offer TREE 121L, Arboriculture Lab, along with TREE 121 Arboriculture. But it would alternatively be possible to set up TREE 121 Arboriculture with both Lecture and Laboratory components, and require all registrants in a given LEC section also to register for one LAB section associated with it. Currently at Loyola most discussion-sections (component-code DIS) are set up this way. Adding a new class component to an existing course is considered a Course Change requiring approval by the Academic Council.

It is possible to schedule sections of two (or more) different courses to meet jointly in a given term, as a Combined Section. One or more of the class-sections may be open to enrollment by students while the other(s) may be non-enrollment sections.

• Combined Sections can be used to offer coursework to students working on the same material at different levels, with differentiated bases of assessment: for example in the fictional Department of Forestry, TREE 345/445 Fire Ecology and Restoration, serves upper-level undergraduates and beginning graduate students jointly. In this example both sections should allow students to register according to their own Student Group so as to receive the correct credit.
• Combined Sections can be used to offer cross-listed classes under both Course Numbers simultaneously, for example, TREE 375/PPOL 375, Natural Resource Policy, cross-listed between the Department of Forestry and the School of Public Policy; provided the courses are cross-credited appropriately in students’ majors and minors, either or both sections might serve as enrollment sections.

• Course Inventory Forms must be part of every application submitted to Academic Council that will ultimately involve new or changed course-programming in LOCUS, because the CI Form tells Registration & Records what to code for the course in question. R&R controls what information is requested on the CI Form. They post a blank form among the Education Record Forms at the Online Forms & Help tab in LOCUS: download and save with a filename identifying the course in question (e.g., TREE121-CIForm.pdf), fill it out, and upload and index it as a supporting document in your application package.
• CI Forms requesting changes in coding of existing courses should supply the course-identifying information at the head of the form, School, and effective date [items 2, 3, and 4 of the current form], but then only the specific elements to be changed, with a note in the Comments box that all other course-attributes should remain as-is.

Course Numbers identify specific courses in the Course Catalogue, e.g., TREE 121, course-title Arboriculture, in the fictional Department of Forestry. When a form asks for a Course Number separately from the Subject Area Code, the two elements are distinguished. LOCUS uses alphabetical Subject Area Codes, typically 4 letters but occasionally 3 letters. The numerical Course Numbers typically use 3 digits, which may be extended by a fourth, alphabetical character (e.g., TREE 121L, Arboriculture Lab).

The term cross-listing is used for several related ideas that may be useful to distinguish by their operation in LOCUS:

• If courses are coded as equivalent, students who have completed a class under one Course Number will be blocked from registering for the equivalent course under the other Course Number, because LOCUS will read the enrollment-request as an unauthorized repeat of the class. Equivalency of courses is sometimes referred to as cross-listing.
• If one of a pair (or more) of equivalent courses is specifically required by a given major or minor, or included in a requirement-option list, students in that major or minor who take the equivalent course under the other Course Number will receive credit for it as if they had taken the listed course. But if a course would be picked up by a major or minor as an elective, that is, by wildcard programming only, any equivalent courses must be explicitly coded into the Academic Requirements Report as alternatives to the wildcard in the Electives list, in order to ensure that the equivalencies are correctly cross-credited. Cross-crediting commonly motivates cross-listing of courses in different Subject Areas.
• When equivalent courses are scheduled as a Combined Section, so that both Course Numbers appear in the Class Schedule (whether or not both are offered as enrollment sections), their joint appearance in the Class Schedule is often referred to as cross-listing; some people also refer to non-equivalent classes being offered in a Combined Section as being cross-listed, but this usage is less happy.
• LOCUS preserves records of cross-listed courses in Subject Area Codes of Interdisciplinary Programs, but since tagging began to be used to identify courses serving interdisciplinary majors and minors, most of these courses have ceased to serve a practical purpose: they may be inactivated. (The historical record of the inactivated course is preserved in LOCUS, so that past students' academic records continue to be reported fully.)

It is advantageous to cross-list courses in departmental Subject Area Codes when members of the faculty of either department can be expected to teach substantially the same class to students pursuing major(s) or minor(s) in either academic field (thus for example, our fictional Department of Forestry cross-lists TREE 134, Peaches, with FZZZ 134, Peaches, in the Department of Things with Fuzz). Typically the section of the course in the Subject Area of the home-department of the faculty member teaching the course is used as the enrollment section. Provided the equivalency of the cross-listed courses is correctly cross-credited in the applicable major(s)/minor(s), all students will receive the appropriate credit, whether or not the other cross-listed/equivalent course also appears in the Class Schedule in a Combined Section. (It is perfectly possible to include non-departmental courses in departmental majors and minors without cross-listing: the Department of Forestry requires its majors to take FZZZ 201, Bees, from the Department of Things with Fuzz, but never teaches an equivalent course).

• Submitters bear the responsibility to formalize all approvals of their proposals with their home unit and all second units through the appropriate internal processes of those academic units, before submitting any applications for consideration by the College's Academic Council. The College's curricular-review process presumes that proposals are submitted to the Academic Council only after they have received the full backing of the submitting academic unit(s).
• When filling out the Summary Memo, please ensure all partnering second-units are listed in items 3 and 4, and all curricular-change types are identified in item 6, before clicking "submit," so that DocFinity's routing system will direct the application-package to all stakeholders correctly. (Stakeholders added later can still use the Search function and manual Diary-entries to review applications and record their approvals, but the more complete the application-package can be from its start, the more efficiently the process will work.)
• No application-package shall be vetted by the Curriculum Committee or reviewed or voted on by the Academic Council as a whole, unless the Chairperson/Program Director of the academic home-unit submitting the application(s) in question shall have recorded approval of the submission in the CAS-AC DocFinity Platform no later than the submission-deadline for the month. Successfully-recorded approval shall appear, time-stamped, in the Diary of the Summary Memo for the application-package. The Chairperson/Program Director records approval in the Tasks panel of the Jobs workspace in DocFinity, after carefully reviewing all documents to ensure the proposed curricular changes are presented clearly and fully, with no errors or inconsistencies in the documents; the record of approval is completed by clicking the "Complete Job" icon to sign out of the Tasks panel.
  • Application-packages approved by the submitting home-unit's Chairperson/Program Director later than one month's deadline may be reviewed in the following month.
  • If late recording of the submitting home-unit's approval causes the application-package to miss processing deadlines, it is the submitters' responsibility.
  • Because errors, inconsistencies, and unclarities need correction but correction takes time, it is preferable for the submitters to secure all parties' approval in principle in advance of submitting, and to proofread all documents rigorously.
  • It is preferable for submitters to submit application-packages, and for the submitters' Chairperson/Program Director to record approval on behalf of the academic home-unit, before the submission-deadline.
• No applications within an application-package shall be voted on by the Academic Council as a whole or shall receive the Council's approval if voted on by mistake, unless all co-signatory stakeholders partnering in the application shall have recorded approval of the application in the CAS-AC DocFinity Platform no later than the day of the monthly meeting. Successfully-recorded approval shall appear, time-stamped, in the Diary of the Summary Memo for the application-package. The Chairperson/Program Director of each second unit partnering in the application records approval in the Tasks panel of the Jobs workspace in DocFinity, after carefully reviewing all documents pertaining to the second-unit's interest in the proposed changes to ensure they are correct and acceptable; the record of approval is completed by clicking the "Complete Job" icon to sign out of the Tasks panel.
  
  • The interval between the application's submission and the monthly meeting, as a cutoff for co-signatory approvals, allows for inclusion of appropriate stakeholders by recommendation of the Curriculum Committee or other reviewers during the Academic Council's review-process; but no application can go forward if it has not received approval by all its stakeholders.
  • It shall be the responsibility of the Curriculum Committee, as its Chairperson shall delegate, to double-check the application-package for outstanding approvals on the day of the monthly meeting, and to withhold the Committee's recommendation from any applications still lacking their full sets of approvals.
  • The Council may determine that applications lacking approval of certain co-signatories can be voted on with the deletion of the non-approved partnership if it is secondary rather than integral to the application (e.g., a New Course proposed for cross-listing may go forward without an unapproved cross-listing, but a New interdisciplinary Major/Minor may not go forward without the approval of all its participating academic units). If such a determination is made, the submitters may accept such a deletion as a friendly amendment and, if the Council votes to approve the amended application, the submitters must undertake to amend all pertinent documents during the cleanup period.
  • It is preferable for submitters to submit application-packages only after securing approval in principle from all partnering stakeholders in advance, and for the stakeholders' Chairpersons/Program Directors to record approval on behalf of the academic second-units, before the monthly meeting.
• Curricular changes that will necessitate new or changed programming in a major/minor must be approved by the Academic Council no later than the December meeting of one academic year, in order to be on-track for effectiveness the following Fall term. Please recognize that this timetable limits the "effective date" that can be requested for any proposed curricular change.
• New or changed course programming must be approved by the Academic Council no later than the February meeting of one academic year, in order to be on-track for effectiveness the following Fall term, or no later than the March meeting of one academic year, in order to be on-track for effectiveness in the Spring term of the following academic year. Please recognize that this timetable limits the "effective date" that can be requested for any proposed curricular change.

• Most members of the faculty of the College of Arts and Sciences hold appointments in an academic department; a few hold joint appointments between different departments. The term thus refers to an organizational structure of the College by its academic focus.
• DocFinity uses the term department to refer to any subdivision of a business, so that not only academic departments but also interdisciplinary programs, the University Libraries, and the Dean’s Office are sometimes referred to as departments in the CAS-AC DocFinity Platform.

• All documents in the CAS-AC DocFinity Platform, both the eForm Summary Memos and uploaded documents, have a Diary associated with them in the platform: when you have opened a document, open its Diary by clicking the View Diary icon in the menu-bar. Approval-routines generate diary entries recording who granted the approval and when: these records are associated with the Summary Memo.
• It is also possible to enter Diary Entries directly, by clicking the Add icon in the menu-bar for the opened Diary, writing in the new window that then opens, and clicking the Save icon.
• Council members (especially but not only members of the Curriculum Committee) will assist submitters and maintain a helpful paper-trail by noting corrections, queries, and recommendations in the Diary of a document, then sending the submitter an e-mail message noting which documents want attention. Having coherent Diaries for each document saves duplication of requests to the submitters.
• Submitters should edit eForms in DocFinity, or revise other documents outside DocFinity and use the Replace icon in the menu-bar to upload the revised document in the place of the original, with the original Diary still attached. Please then add to the Diary a new Entry recording the update, so that reviewers will know earlier comments have been addressed (the Comment that appears during the Replace routine does not appear to get recorded in the Diary, so it must be done separately).

• The date on which curricular changes programmed in LOCUS become effective, is their effective date. Normally, specific effective dates precede the term for which the changes are targeted, so that changes approved for the Fall semester actually go live during the preceding summer.
• Curricular changes that will necessitate new or changed programming in a major/minor must be approved by Academic Council no later than the December meeting of one academic year, in order to be on-track for effectiveness the following Fall term. Changes in majors and minors normally are made only for effectiveness the following Fall term, for the sake of clarity and consistency in all communications with students about their major(s)/minor(s).
• New or changed course programming must be approved by Academic Council no later than the February meeting of one academic year, in order to be on-track for effectiveness the following Fall term, or no later than the March meeting of one academic year, in order to be on-track for effectiveness in the Spring term of the following academic year.
• Students are subject to the requirements of major(s)/minor(s) they declare, as in force at the date they declare the major(s)/minor(s) in LOCUS.

As of Fall 2017, the Summary Memo is the only eForm in the CAS-AC DocFinity Platform. eForms reside in the platform and must be edited there. The Summary Memo needs to be an eForm so it can interactively generate a Unique ID for the application package and manage the routing of the package to stakeholders so that all parties concerned in the applications can sign off and keep the records centralized.

• LOCUS’s programming-structures for Academic Requirements Reports mean that the term elective should be restricted to courses included in a major/minor by wildcard programming, e.g., TREE 3##, any 300-level course in the Subject Area Code for the fictional Department of Forestry.
• Since ARRs cannot read tags (a tag indicates that a course is included in an interdisciplinary major/minor, but tags function only in Class Search), most interdisciplinary and interdepartmental majors/minors must be programmed with requirement-option lists. Therefore the distinction between true, wildcard-programmed electives and requirement-options of an interdisciplinary or interdepartmental major/minor affects the timetable Academic Council’s curricular approvals must meet: a new course TREE 358 Ecofeminism would be picked up as an elective in the Forestry minor by the pre-existing wildcard rule TREE 3##, but would need to be specified, and therefore explicitly programmed, in a list of (elective-like) options for the interdisciplinary minor of the Gender Studies Program. (Ecofeminism will be an option for the Theory requirement of the GSP-BA and an option for the Ethics requirement of the TREE-BS, requiring explicit programming in both majors.)
• Optional courses not included in students’ declared major(s)/minor(s) as specifically required courses, requirement-options, or electives earn credit as hours toward graduation, but not in the major(s)/minor(s).

When two (or more) sections of different courses are scheduled to meet jointly in a given term as a Combined Section, one or more may be open to enrollment by students while the other(s) may be non-enrollment sections. If the courses of the Combined Section serve different Student Groups (for example, graduate and undergraduate sections working on the same material at different levels, with differentiated bases of assessment), allowing students to register in the course appropriate to their own Student Group ensures they receive the correct credit. But if equivalent courses are cross-credited appropriately in students’ majors and minors, all students would receive appropriate credit and a Combined Section could make the class more visible to both constituencies, even if only the section in the Subject Area of the instructor’s home department served as the enrollment section.

If courses are coded as equivalent, students who have completed a class under one Course Number will be blocked from registering for the equivalent course under the other Course Number, because LOCUS will read the enrollment-request as an unauthorized repeat of the class. If one of a pair (or more) of equivalent courses is specifically required by a given major or minor, or included in a requirement-option list, students in that major or minor who take the equivalent course under the other Course Number will receive credit for it as if they had taken the listed course. But if a course would be picked up by a major or minor as an elective, that is, by wildcard programming only, any equivalent courses must be explicitly coded into the Academic Requirements Report as alternatives to the wildcard in the Electives list, in order to ensure that the equivalencies are correctly cross-credited.

Before-and-After Major/Minor Grids lay out the current structure and proposed changes in a given major or minor in a clearly legible, comprehensive graphic form. They enable reviewers to understand how individual elements fit together in students’ studies, and thus to contextualize curricular requests. One grid is required for every major and for every minor that will be affected by the curricular changes being considered in an application package; please consolidate grids so that only one grid per major or per minor involved in the application-package is submitted, each accounting for all changes in which it is concerned.

The basic format of the grid tabulates

We recommend submitters consult the Academic Requirements Outlines posted in LOCUS so as to confirm that the current programming of the Academic Requirements Report for each major and for each minor involved corresponds to their understandings, give or take approved changes currently in processing for effectiveness at a later date. The Current Major/Minor column should show the structure of the major/minor as most recently approved. Please list specifically required courses and courses in requirement-option lists individually, and electives by their wildcard-programming rules. If the changes requested in the application package will not affect a given area of the grid, please mark “n/a” in that box of the Proposed Changes column.

• The concepts of home unit and second unit(s) pick up the organizationally neutral usage of academic unit to refer to either departments or interdisciplinary programs. The home unit is the academic unit originating an application package; second unit(s) are additional academic units with interest in one or more individual applications within the package. Second unit(s) may also be referred to as stakeholders in a curricular change.
  
  
• The department or interdisciplinary program that oversees the subject area of a given course number may also be referred to as the course’s home unit.

The indexing function in DocFinity allows submitters to attach metadata to a document in the platform, by which it becomes possible for the Search function to find the document. Because metadata recorded in the index, not information inside the document itself, are what the Search function can identify, it is urgent that all pertinent metadata be indexed completely and accurately.

Although most majors and minors in the College of Arts and Sciences are administered either by an academic department or by an interdisciplinary program, some are administered jointly by two academic units, without involving a separate administrative structure (e.g., the minor in Biostatistics, the major in Sociology and Anthropology). For the most part, formal procedures for curricular review of interdepartmental majors/minors follow the patterns of departmental majors/minors, except that both academic units sign off jointly to give authorization. Courses serving interdepartmental majors/minors are not typically identified in LOCUS by tags.

• Interdisciplinary majors/minors are administered by interdisciplinary programs formally so constituted in the College of Arts and Sciences as administrative units.
• The authority in curricular matters of Directors of interdisciplinary programs is presumed to arise from the consent of the participating faculty, just as the authority of departmental Chairpersons for departmental and interdepartmental majors/minors is presumed to arise from departmental consent; nonetheless, while Directors authorize applications to add individual courses to interdisciplinary majors/minors by Permtag Applications, participating departments are expected to sign off as stakeholders on applications for structural changes to interdisciplinary majors/minors.
• Courses serving interdisciplinary majors/minors normally are identified in LOCUS by tags. Please note, however, that the programming of a major or minor to include a course is entirely separate from the programming of a course with a tag, although both items of programming should be done to match. The only function of a tag is to match its parameter in LOCUS's Class Search.

Interdisciplinary Programs are formally constituted as administrative units, by authority of the Provost and the President, in or across Schools within Loyola University Chicago. Two or more academic departments typically participate in the administration of an interdisciplinary program; interdisciplinary programs typically administer one or more interdisciplinary majors/minors.

LOCUS is the student information system used by Loyola University Chicago. Functions important for curricular purposes include the Course Catalog, Class Scheduling, and academic records including the programming of students’ Academic Requirement Reports.

Metadata in DocFinity’s index enable the Search function to find documents. Metadata can include, for example, the Unique IDs of specific application-packages, the application-types of specific requests, the academic units and individuals who submit applications, course numbers, and the date of the meeting at which the Academic Council approved an application – but only if this information is added to the index. Since different items of information may be salient when in future it becomes necessary to refer back to application-packages, it is helpful for submitters to index pertinent metadata as completely as possible when they are seeing their application packages through the curricular-review process.

Some paperwork distinguishes parent courses and child courses. The parent course of a pair (or more) of equivalent courses, was at some point considered at least logically prior to the child course(s), whether or not they were created at different times. Ordinarily the home unit of the parent course is anticipated to take the lead in updating it, although it is important that parallel applications be approved for child course(s) also so that they remain in line with the parent course. It is conceivable that the evolution of academic fields and the patterns of University hiring could occasionally cause a parent course and a child course to exchange status.

LOCUS uses Plan Codes to identify specific majors and minors. Plan Codes typically consist of 4 alphabetical characters, which may or may not correspond with a Subject Area Code administered by the same academic unit as the major/minor in question, plus a suffix indicating the degree: thus for example the Department of Chemistry and Biochemistry administers the BIOC-BS, CHEM-BA, CHEM-BS, and CHEM-MINR, B.S. in Biochemistry, B.A. in Chemistry, B.S. in Chemistry, and Minor in Chemistry, respectively. The Academic Requirements Outlines in LOCUS are a convenient place to verify Plan Codes.

• Prerequisites are courses a student must have either already completed or, if a continuing student at Loyola, be currently enrolled in as of the registration period in the preceding term, in order for LOCUS not to block them from registering for a target class.
• Corequisites are courses that must be enrolled in concurrently with a target class.
• Changing the prerequisites or corequisites of an existing course is considered a Course Change requiring approval by the Academic Council.
• Prerequisites and corequisites may be either enforced or advisory in LOCUS:
  • If some precondition of a student's success in a course is something LOCUS can readily identify in a student's record as having been either satisfied or unsatisfied, such as the student's having successfully completed a certain prerequisite course, LOCUS can be set to enforce the prerequisite, and not allow students to register if they have not satisfied the prerequisite condition.
  • But if a course's preconditions for success are not regularly coded in LOCUS, LOCUS would not be able to enforce them meaningfully: they may be useful to indicate in the course-description in the catalogue on an advisory basis, only. (For example, the degree of fitness needed to succeed in the fictional Department of Forestry's Treejumping class, TREE 387, is assessed by physicians attached to the campus ROTC division.)

• As opposed to specifically required courses on the one hand and to electives on the other, a requirement with options gives students pursuing a given major/minor choices among a set of individually specified alternatives: for example the Ethics requirement of the fictional major in Forestry might be satisfied by any two of TREE 355 Environmental Justice, TREE 356 Sustainable Development, TREE 357 Ethnobotany, TREE  358 Ecofeminism, and TREE 359 Natural Resources Conflict Resolution.
• Just like specifically required courses, requirement-option lists must be individually programmed in students’ Academic Requirements Reports: therefore their processing-requirements and deadlines are parallel.
• Interdisciplinary and interdepartmental majors/minors typically rely on requirement-option lists, since ARRs cannot read tags.

The term reviewer applies to any person who consults an application-package in the CAS-AC DocFinity Platform during the process of curricular review:

• Members of the Academic Council's Curriculum Committee undertake the important responsibility of reviewing all applications thoroughly, working with the submitters so as to resolve any potential difficulties they identify, and formulating recommendations for the Council as a whole.
• All members of the College's Academic Council are expected to familiarize themselves with all applications submitted for the Council's review in any given month, in advance of the monthly meeting, so as to advise the submitters and represent the interests of the academic unit they each represent on the Council, in the Council's discussion and voting. They too are invited to work with submitters while applications are under review so as to resolve any potential difficulties they identify.
• Depending on the nature of the application-package and its needs, the Associate Dean for Academic Affairs and other members of the Dean's Office may also review elements of applications and work with submitters so as to resolve potential difficulties.
• Stakeholders in the application-package outside the package's home-unit, such as second-units partnering with the home unit in individual applications within the package, are more commonly referred to as stakeholders but may also perform the function of reviewers.
• Members of the submitters' home unit, such as the Chairperson/Program Director, are commonly included in references to the submitters, but they too may also perform the function of reviewers.

Every student pursuing a given major/minor must successfully complete every one of its specifically required courses in order to complete the major/minor successfully. Majors and minors vary tremendously how much they make use of specifically required courses.

Any academic unit that will be concerned in a proposed curricular change is a stakeholder in it. The term is especially used of second unit(s) signing on to a change proposed by the major/minor’s or course’s home unit.

Student groups are used by LOCUS to program enrollment-restrictions according to characteristics of students prospectively enrolling in a given course: for example, students who have declared a certain major/minor, students of a certain academic standing, or students enrolled on a specific overseas campus. Restrictions according to Student Group may be programmed for a course permanently, in the Course Catalogue (in which case they are subject to approval through the College’s curricular-review process), or in the Class Schedule for a specific class-section in a specific semester.

Subject Area Codes in LOCUS identify the academic field in which a course is coded. Subject Area Codes typically use 4 letters but occasionally 3 letters. The View Course Catalog or Browse Course Catalog index in LOCUS is a convenient place to verify Subject Area Codes with currently effective courses.

• The verb submit is used to refer to two different steps in the processes of the CAS-AC DocFinity Platform:
  • Initial Submission: After all the applications and supporting documents have been prepared and the eForm of the Summary Memo drafted, to submit the Summary Memo formally begins the application-process. Please remember that DocFinity's ability to send application-packages to all stakeholders depends on the information in the heading of the Summary Memo and in its items 3, 4, 5, and 6: ensure that all these elements are complete and correct before the initial submission, or your application-package will not route successfully. When the Summary Memo is completed, including both the Table of Contents and all co-signatories, scroll down to the Submit button at its bottom and click. This step will generate an automated e-mail message to the submitter, confirming the Unique ID generated at the top of the Summary Memo for the application package. It will also make the Summary Memo visible to other users in the CAS-AC DocFinity Platform: the Job Queue will label it an “Initial Submission.”
  • Submission Complete: When the applications and supporting documents have all been uploaded to the CAS-AC DocFinity Platform and indexed, go to the Jobs Queue, check all the tasks in the task-menu, then check the box “is the Submission Complete?”, select “Submission Complete” in the pop-up window, and then sign off with the “Complete Job” icon in the toolbar. This step is also known as submitting the application-package. It sends the package forward to departmental and interdisciplinary co-signatories with the job-status “Submission Complete.” (Any co-signatories added after this point will have to work outside DocFinity's routing system, through e-mail, DocFinity's Search function, and manual Diary-entries.)
• The noun submitter refers, according to context, either to the individual who fills out the eForm for the Summary Memo and whose UVID is incorporated in the autopopulated Unique ID, or to the academic home unit initiating the application-package.

The Summary Memo, an eForm in the CAS-AC DocFinity Platform, interactively generates a Unique ID for the application package, manages the routing of the package to stakeholders for review and signoff, and contains a Table of Contents that enables all users to navigate the application-package efficiently.

• In the rare event a single submitter submits multiple packages of curricular-change applications on the same date, please add to the automatically generated ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1.
• The Table of Contents should follow the format exemplified in the Instructions for the Summary Memo.
• Please plan out the entire application-package before drafting. Complete all information in the heading of the form and identify all stakeholders (items 3, 4), bibliographers if needed (item 5), and all curricular-change types (item 6) before submitting, so that DocFinity's routing can include all parties correctly. If any of this information is incorrect or missing, DocFinity will not be able to route the application-package correctly. (Stakeholders added later will nonetheless be able to use the Search function and manual Diary-entry in order to review the applications pertinent to them and record their approval.)

In addition to the standardized application-forms, many kinds of curricular request also require certain supporting documents be uploaded and indexed together with the application-package, and identified in the Table of Contents in the Summary Memo: for example, any time the coding of a course in LOCUS is to be changed, a Course Inventory Form must be submitted laying out the changes in the format Registration & Records requires. Please consult Instructions for the different kinds of curricular request in order to determine which types of supporting document your applications will need. Some applications, as submitters may determine independently or in consultation with the Dean’s Office, AC Curriculum Committee, or other entities, may be clarified and supported by additional supporting documents; in those instances they too should be uploaded, indexed, and included in the table of contents in the Summary Memo.

• Tags mark courses in LOCUS’s course-catalogue, or class-sections in particular terms’ class schedules, as possessing specified “class attributes” such as Core or Engaged Learning credit. The tags of greatest pertinence in the College of Arts and Science’s curricular review, however, identify class-sections’ carrying credit toward interdisciplinary major(s)/minor(s). Tags appear in the Enrollment Information box of the Class Detail display.
• The Class Search function in LOCUS can read tags, so that they make it possible to search across different Subject Area Codes for class-sections bearing particular tags.
• Academic Requirements Reports cannot read tags: the inclusion of a course in an interdisciplinary major or minor is entirely separate within LOCUS from the marking of a course as so included (although certainly no course should be tagged with information that is not true).
• Interdisciplinary Programs may apply to tag departmental courses and include them in interdisciplinary major(s)/minor(s) on either a permanent or a temporary, semester-specific basis.
  • Permanently tagged courses should also be programmed permanently in students’ ARRs as specifically required courses, courses satisfying specified requirement-options, or (wildcard-programmed) electives. Permanently tagging a new or existing course and adding it to an interdisciplinary major/minor requires approval by the Academic Council; the request-type is familiarly called Permtag.
  • Temporary Tag requests (and requests to cross-list departmental courses on a temporary, semester-specific basis; the request-type os familiarly called Temptag/Tempcross) are processed through the DocFinity Platform in application-packages structurally similar to the permanent requests reviewed by the Academic Council. Please see the Instructions. Temptag/Tempcross applications are reviewed by the Associate Dean for Academic Affairs. Classes temporarily included in students’ major(s)/minor(s) must be hand-credited by students’ CAS Advisors via Individual Directives. Please advance Permanent Tag requests as soon as it is determined they are appropriate, so as to avoid the inefficiencies of the temporary process.

The Temporary Tag/Cross-List Request is made on a semester-specific basis, for the purpose of crediting to specified major(s)/minor(s) a specific section of a course not ordinarily included. Please file Temptag/Tempcross requests separately from requests involving permanent course-coding or major/minor coding. Please see the Instructions.

• Temptag/Tempcross requests most commonly arise in the case of variable-topics courses, not all of whose potential topics would be suitable for the major(s)/minor(s) in question.
• Temptag/Tempcross requests may be used to fill in the processing-lag between approval of Permanent Tag or Permanent Cross-listing requests and their becoming effective.
• Temptag/Tempcross requests are processed through the DocFinity Platform in application-packages structurally similar to the permanent requests reviewed by the Academic Council, but see the Instructions. Unlike permanent tag or permanent cross-list requests, temptag/tempcross requests do not involve Course Inventory Forms, since no permanent change is to be made in the coding of the course itself. Since neither is any permanent change made in students' ARRs, classes temporarily included in students’ major(s)/minor(s) must be hand-credited by students’ CAS Advisors via Individual Directives.
• Temptag/Tempcross requests require co-signatory authority of all stakeholders, just like permanent tag or permanent cross-list requests.
• Temptag/Tempcross requests are reviewed by the Associate Dean for Academic Affairs, not by the Academic Council. Although they can be turned around relatively quickly, please submit them with enough lead-time before registration for the term the class will be offered that Registration and Records can process the information to appear in the Class Schedule.
• Please advance Permanent Tag or Permanent Cross-list requests as soon as it is determined they are appropriate, so as to avoid the inefficiencies of the temporary process.

The Unique ID holds its application-package together in the CAS-AC DocFinity Platform. A number of the form UVIDmmddyyyy (according to the submitter’s UVID and the submission-date, e.g., mlettie05162017) auto-populates when the submitter opens a new Summary Memo eForm. (In the rare event a single submitter submits multiple packages of curricular-change applications on the same date, please add to the automatically generated ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1.) By entering the Unique ID on every Application-form and every Supporting Document in the application-package and including the Unique ID in the indexed information for every item in the package, submitters enable DocFinity to identify documents as belonging to their packages.