Instructions for Curricular Changes

  • For permanent changes in coding of courses or programs, the academic unit (department or interdisciplinary program) initiating a change bears the responsibility to initiate the paperwork so as to effect that change.

  • It is helpful if the person who fills out and submits the Summary Memo can readily address any questions about the changes proposed, since that person’s name will be associated with the application-package as the submitter and that person’s UVID will be built into the application-package’s automatically-generated Unique.
  • “Chairperson/Program Director” must be named because that person gives authority for the academic unit submitting the application.

  • The proposing unit should identify all parties concerned in the changes proposed (e.g., cross-listing departments and tagging interdisciplinary programs in a course, participating units in a cross-disciplinary major or minor), so that DocFinity may collect their approvals. Stakeholders’ approval will be recorded in the Diary Entries of the Summary Memo. The approvals show the parties understand and consent to the changes proposed. A complete set of approvals must be received before the application can be considered.

  • If the proposing unit’s changes provoke additional changes in a second academic unit’s programs, the second unit should submit the needed additional applications, under its own authority but together with the proposing unit’s package (for example, if a home unit’s course-change means the course should change from being an elective to a specific requirement in another unit’s minor, the second unit should sign onto the home unit’s change and submit its own Change of Minor application; using the same Unique Number will hold the whole package together).

Either cross-listing or tagging may arise when a course serves a major or a minor outside its home unit.

  • “Tagging” means the name of the Interdisciplinary Program in question appears in LOCUS’s display of Course Attributes for a course belonging to a different home unit.
  • The tag permits students to search in the Class Schedule for classes that may serve a given interdisciplinary program’s major or minor, regardless of the classes’ home units.
  • Although the tag should not appear on courses not included in the major or minor, applying the tag and including the course are two separate operations by R&R.
  • “Cross-listing” means the same course, in terms of its defining content and objectives, is designated in LOCUS by course numbers in more than one Subject Area Code belonging to separate academic units.
  • Courses are cross-listed most often when they might be taught by members of faculty holding appointments to different academic units (for example, our fictional course Peaches is cross-listed as both FRST 134 in the Department of Forestry and FZZZ 134 in the Department of Things with Fuzz): a particular instructor’s home unit schedules the class under its own Subject Area Code. Academic Requirements Reports for both units’ major(s) and minor(s) must be set up so as to ensure that either course-number will be read as cross-crediting and serving students in both programs.
  • Courses required by a major or minor of an interdisciplinary program may need to be cross-listed with departmental courses, but usually tagging suffices.
  • Whereas a permanent tag always appears on a course, cross-listed courses appear together in LOCUS only if they are scheduled together as Combined Sections.
  • 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 FRST 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.

  • If there is no expectation members of both departments will teach the course, a second unit may include non-departmental courses in its own departmental majors and minors without cross-listing: our fictional Department of Forestry requires its majors to take FZZZ 201, Bees, from the Department of Things with Fuzz, but never teaches an equivalent course.

  • Do recall for purposes of visibility, cross-listed courses appear together in LOCUS only if they are scheduled together as Combined Sections, regardless of whether or not they are also cross-credited.
  1. What to do first: (1) consult interested parties; (2) design collaboratively; (3) prepare applications and supporting documents; (4) fill out and submit Summary Memo and note Unique ID generated (in the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions); (5) upload all applications and supporting, documents; (6) vital:index all applications and documents with the Unique Number and other pertinent information. Allow sufficient lead-time for DocFinity to gather authorizing signatures from all parties concerned, before the Submission Deadline for the meeting of Academic Council at which you want your proposal to be discussed.
  2. Academic collegiality and planning, for smooth application-processes: Please identify all academic units that may have an interest in the curricular changes you are requesting. Please consult with these colleagues in preparation for submitting the applications. If they will want to use your course(s) in their major(s) or minor(s), or if they contribute to your interdepartmental or interdisciplinary major(s) or minor(s), they should be included in the document-routing the Summary Memo Sheet sets up. All parties should indicate their approval of the application before it comes before the Academic Council for its review. (Stakeholders identified later in the process can be added, but it’s messy. The more preliminary consent has been secured in advance and indicated clearly in the paperwork, the smoother everything flows and the less potential for confusion and error. Thank you.)
  3. Documentation: The Instructions for Curricular Changes at the Academic Council website (http://luc.edu/cas/academiccouncil/instructionsforcurricularchanges/) offer a guide which forms and supporting documents are required. Please note that different changes may require different forms: for example, a New Course that will be picked up by wild-card programming as an elective in a major or minor is implicitly included in the existing structure of the major/minor and will not require Change of Major/Minor applications, but a New Course will require Change of Major/Minor applications if it is to satisfy any Requirements with Options (students choose, e.g., 2 courses from a list of 5) or to be a Specifically Required Course. Constituent applications in the submission-package should be listed in Item 2.
  4. Be it ever so obvious, there’s always a grid: Your application-package needs to include one completed before-and-after grid for each major and for each minor that will be affected by the curricular changes you are proposing. This need is felt even for electives in LOCUS’s sense, that is, when the course(s) involved are picked up by wildcard programming in the major(s)/minor(s) so that the existing major/minor structure does not change. The grids show reviewers the academic context of your proposed curricular changes, so that they can understand better why the changes are desirable. They also facilitate the programming your changes will require when they’re being implemented. 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. Please list grids as the last item of the Table of Contents in Item 2.
  5. Sample Format for the Table of Contents (item 2):

    1. Change in Major, FRST-BS

  a. Parties Concerned: this application incorporates in the Forestry major the new courses proposed in this package: FRST 337 and FRST 367 (see below) will be electives [i.e., picked up by existing wild-card programming] in FRST-BS as all four courses will be in FRST-MINR, but GSP 359, Ecofeminism (cross-listed with FRST 358 and SOTH 359: see below) should be added to the options for the Ethics requirement of FRST-BS, and the cross-listed FRST 372, Urban Constituencies and City Government (PPOL 260) will serve as an alternative to FRST 371, National Park System, among the options for the Management requirement of FRST-BS.

    b. Change in Major Form for FRST-BS; for related course-documents and before-and-after grid, see below

    2. Change in Major, GSP-BA

  a. Parties Concerned: this application incorporates in the Gender Studies major the new course in Ecofeminism, GSP 359, team-taught by members of the Department of Forestry and of the Department of Social Theory and cross-listed in both departments (FRST 358, SOTH 359: see below). This course should be added to the options for the Theory requirement of GSP-BA. It will be an elective in GSP-MINR as also in SOTH-BA and SOTH-MINR

    b. Change in Major Form for GSP-BA; for related course-documents and before-and-after grid, see below

    3. New Course, FRST 337, Parks and Urban Forestry

  a. Parties Concerned: the course will be offered by the Department of Forestry as an elective [i.e., picked up by existing wild-card programming] in FRST-BS and FRST-MINR; we expect it will be of interest to the School of Public Policy when they complete design of the new major and BA-to-MPP programs in Urban Policy and Management, presently under discussion.

    b. New Course Form for the proposed FRST 337

    c. Sample Syllabus for the proposed FRST 337

    d. Course Inventory Form for the proposed FRST 337

    4. New Course, FRST 367, Applied Landscape Architecture

  a. Parties Concerned: the course will be offered by the Department of Forestry as an elective in FRST-BS and FRST-MINR

    b. New Course Form for the proposed FRST 367

    c. Sample Syllabus for the proposed FRST 367

    d. Course Inventory Form for the proposed FRST 367

5. New Course, GSP 359, Ecofeminism

    a. Parties Concerned: the course will be team-taught by members of the Department of Forestry and of the Department of Social Theory, for the Interdisciplinary Program in Gender Studies; it will be cross-listed in both departments (FRST 358, SOTH 359) but the Gender Studies course is the “parent” course. The new course will be added to the options for the Theory requirement of the GSP-BA and the Ethics requirement of the FRST-BS (see Change in Major applications above); it will be an elective in GSP-MINR, FRST-MINR, SOTH-BA, and SOTH-MINR.

    b. New Course Form for the proposed GSP 359 with cross-listed FRST 358, SOTH 359

    c. Sample Syllabus for the proposed GSP 359/FRST 358/SOTH 359

    d. Course Inventory Forms for each of GSP 359, FRST 358, SOTH 359

6. New Course Number for Cross-listing Existing Course: FRST 372, Urban Constituencies and City Government (PPOL 260, School of Public Policy)

  a. Parties Concerned: the Department of Forestry seeks to create FRST 372 so as to cross-list the School of Public Policy’s course PPOL 260, Urban Constituencies and City Government. The course will serve as an alternative to FRST 371, National Park System, among the options for the Management requirement of FRST-BS (see Change in Major application above); it will be an elective in FRST-MINR

    b. New Course Form for the proposed FRST 372

    c. Sample Syllabus for PPOL 260, proposed for cross-listing as FRST 372

    d. Course Inventory Form for the proposed FRST 372

7. Major/Minor Grids: FRST-BS, FRST-MINR, GSP-BA, GSP-MINR, SOTH-BA, SOTH-MINR

The heading information of the New Major/Minor form corresponds to the heading information of the Summary Memo eForm. We recommend that you draft in advance all the application-forms that will be part of your application-package, including any New Major/Minor forms needed, omitting only temporarily the Unique Number.

After you submit your Summary Memo, copy the Unique Number it generates for your application-package onto each of your application-forms, including any New Major/Minor forms needed. Then upload the application forms and all supplementary documents, and index all items by the Unique Number of the application-package.

The Plan Code of the new major or minor (item 2) will be a shorthand for it in LOCUS’s coding: typically plan-codes abbreviate the major/minor title in four characters, plus -BA/BS/MINR as applicable. Registration & Records will determine the Plan Code actually adopted.

  • The list of stakeholders in addition to the Department or Interdisciplinary Program submitting the application (item 2.b) should correspond to this specific New Major/Minor’s part of the Table of Contents in the Summary Memo, and confirm it. It is re-stated in the application form because not all applications in the package necessarily concern the same additional stakeholders. The line of the form may be copied and pasted in order to list multiple partners.

  • The statement of rationale for the major/minor in item 3 of the application-form should be as full as needed to make clear your plans for the proposed major/minor and demonstrate its merits. The Summary Memo’s brief statement of changes in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package. Fuller reference to the Proposal Document (see item 8) is implicit.

  • Item 4 details the association of any New Course applications with the present application-package or planned for the future.

  • Item 5 details the association of any Course Change applications, including any discontinuations, with the present application-package or planned for the future.

  • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 6) flags these considerations for other reviewers. In particular, if the proposal will require any changes in library-resources, please ensure the appropriate librarian is identified and included in item 2.c of the Summary Memo.

  • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, Registration & Records undertakes to make new major/minor programming approved by AC no later than December of one academic year, effective as early as the Fall semester of the following academic year.

  • Please ensure that all course-applications and supplementary documents entailed by your New Major/Minor application (see items 4, 5) are also submitted within your application-package under the same Unique Number. In particular, a New Major/Minor Proposal (10-page maximum) will be required, following the Academic Affairs Proposal Guidelines (download from Academic Program Development link at http://luc.edu/academicaffairs/curriculumresearch/curriculumdevelopment/programdevelopment/), as will a Major/Minor Grid (outline the new major/minor in the Proposed column).
  • Your application-package (under one Unique Number) will require one Change in Major/Minor application form for each major, and one for each minor, that will require re-programming of its Academic Requirements Report in order to realize the curricular changes the application contemplates.
  1. Note that New Courses (for example) will not necessitate a Change in Major/Minor application if they will all be picked up as desired in the major/minor by an existing elective-rule.
  2. Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes, even if Change in Major/Minor applications are not required.
  • The heading information of the Change in Major/Minor form corresponds to the heading information of the Summary Memo eForm. We recommend that you draft in advance all the application-forms that will be part of your application-package, including any Change in Major/Minor forms needed, omitting only temporarily the Unique Number.
  • After you submit your Summary Memo, copy the Unique Number it generates for your application-package onto each of your application-forms, including any Change in Major/Minor forms needed. Then upload the application forms and all supplementary documents, and index all items by the Unique Number of the application-package.
  • The Plan Code of the major or minor concerned in the application-document (item 2) is used in LOCUS for coding purposes (e.g., DANC-BA for the major in Dance). Convenient places to look so as to confirm your Plan Code include the index-list of the Academic Requirements Outlines and the outlines themselves: you can navigate to the Academic Requirements Outlines from the portal-page that displays when you’ve logged in to LOCUS.
  • The list of stakeholders in addition to the Department or Interdisciplinary Program submitting the application (item 2.b) should correspond to this specific Change in Major/Minor’s part of the Table of Contents in the Summary Memo, and confirm it. It is re-stated in the application form because not all applications in the package necessarily concern the same additional stakeholders. The line of the form may be copied and pasted in order to list multiple partners.

  • The statement of changes in the major/minor, and their rationale, in item 3 of the application-form should be as full as needed to make clear your plans for the major/minor and demonstrate the merits of the changes. The Summary Memo’s brief statement of changes in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.

  • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 4) flags these considerations for other reviewers. In particular, if the proposal will require any changes in library-resources, please ensure the appropriate librarian is identified and included.

  • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, Registration & Records undertakes to make changes in major/minor programming approved by AC no later than December of one academic year, effective as early as the Fall semester of the following academic year.

  • Please ensure that all course-applications and supplementary documents entailed by your Change in Major/Minor application are also submitted within your application-package under the same Unique Number.
  • The heading information of the New Course form corresponds to the heading information of the Summary Memo eForm. We recommend that you draft in advance all the application-forms that will be part of your application-package, including any New Course forms needed, omitting only temporarily the Unique Number.

  • After you submit your Summary Memo, copy the Unique Number it generates for your application-package onto each of your application-forms, including any New Course forms needed. Then upload the application forms and all supplementary documents, and index all items by the Unique Number of the application-package.

  • The rationale in item 3 of the application-form should be as full as needed to make clear your plans for the course and demonstrate its merits. The Summary Memo’s brief statement in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.

  • If the new course will be a pre-requisite for existing course(s: item 5.b), please also submit as a part of this application-package the Course Change requests for those other course(s), so that the change will sort with their paper-trails.

  • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying faculty, library, equipment, and other resources the proposed new course will require so as to be realized successfully (item 8, if applicable) flags these considerations for other reviewers.

  • If a second (or more) Course Number is desired for the new course, in a Subject Area Code belonging to a different academic unit, the cross-listed course(s) may be created by this application (item 9.a): such cross-listing most often is desired when the same course in its substance might be taught by members of faculty holding appointments to different academic units. From this course-creation forward to the end of time, care must be taken to ensure that the “child” course(s) match(es) the attributes of the “parent” course as either is updated. Please ensure that all partners in the course are identified in the Table of Contents in the Summary Memo so that they may be included in the routing of the documents, and ensure that a separate Course Inventory Form for each “child” course, matching the attributes of the “parent” course but headed according to its own “home” academic unit, is submitted and indexed together with the Course Inventory Form for the new “parent” course. Specify the cross-listed courses’ role in all majors and minors in which they will function, including the cross-listing department’s, in item 11, and include the new courses in before-and-after grids for each affected major and minor. File those grids as supplementary documents to this application-package and index with its Unique ID.

  • If any Interdisciplinary Program(s) wish(es) to include the new course in its major(s)/minor(s), the appropriate tags may be included as Course Attributes of the new course through this application (item 9.b). Please ensure that all partners in the course are identified in the Table of Contents in the Summary Memo so that they may be included in the routing of the documents. Specify the new course’s role in all majors and minors in which it will function, including the tagging IDPs’, in item 11, and include the new course in before-and-after grids for each affected major and minor. File those grids as supplementary documents to this application-package and index with its Unique ID.

  • Item 11 registers not only all major(s)/minor(s) in which the new course will figure, but also whether it will be (i) specifically required in any major/minor, so that all students pursuing the major/minor must complete it successfully, (ii) included in a list of specified courses from which students pursuing the major/minor must successfully complete a certain, smaller number of courses, and if the major/minor includes more than one such list in which list(s) does the course figure, or (iii) covered by a wildcard-rule such as “students take three SUBJ 3xx electives.”
  1. New Courses will necessitate Change in Major/Minor applications if they will need to change existing programming of the ARR(s) in order to satisfy a specific requirement or requirement-option choice.
  2. New Courses will not necessitate Change in Major/Minor applications if they will all be picked up as desired in the major/minor by an existing elective-rule.
  3. Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes, even if Change in Major/Minor applications are not required.
  • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, Registration & Records undertakes to make new courses approved by AC no later than February of one academic year, effective as early as the Fall semester of the following academic year, and new courses approved by AC no later than March of one academic year, effective as early as the Spring semester of the following academic year; once it is effective the new course will be picked up by existing Elective rules in all applicable major(s)/minor(s) but any changes in major/minor programming (i.e., if the new course will be specifically required or will figure in any requirement-option lists) must be approved no later than December of one academic year in order to become effective as early as the Fall of the following academic year.
  • Please ensure that all supplementary documents entailed by your New Course application are also submitted within your application-package under the same Unique Number.
  • The Course Change application is used when a course’s “home” department seeks to change its programming in the Course Catalog. It now excludes requests by “second” academic units to create new courses for the purpose of cross-listing the existing course or to tag the existing course for the purpose of including it in an interdisciplinary major/minor: those changes may be sought concurrently with Course Changes by the home department but by means of separate applications initiated by the “second” academic units.

  • The heading information of the Course Change form corresponds to the heading information of the Summary Memo eForm. We recommend that you draft in advance all the application-forms that will be part of your application-package, including any Course Change forms needed, omitting only temporarily the Unique Number.

  • After you submit your Summary Memo, copy the Unique Number it generates for your application-package onto each of your application-forms, including any Course Change forms needed. Then upload the application forms and all supplementary documents, and index all items by the Unique Number of the application-package.

  • Coding information for the existing course (item 1) may be consulted in the Course Catalog in LOCUS and information about courses’ current roles in majors and minors in the Academic Requirements Outlines to which you can navigate from the portal-page that displays when you’ve logged in to LOCUS.

  • If the course is to be discontinued (“yes” to item 2), the reason why remains good to know (item 3), and Registration & Records will want a Course Inventory Form (item 7) filled out for discontinuation of the course (items 2.1, 2.2, 2.3, 2.4, and 2.6 or 2.7 of the Course Inventory Form), but other items of the form can be skipped and other supplementary documents omitted.

  • The rationale in item 3 of the application-form should be as full as needed to make clear your plans for the course and demonstrate the merits of the changes. The Summary Memo’s brief statement in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.

  • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 4.f, if applicable) flags these considerations for other reviewers.
  • Item 5 registers, and should highlight, all changes in major/minor programming associated with the course-change, but also 5.b registers the specifics of the broader question in item 1: is the course (i) specifically required in any major/minor, so that all students pursuing the major/minor must complete it successfully, (ii) included in a list of specified courses from which students pursuing the major/minor must successfully complete a certain, smaller number of courses, and if the major/minor includes more than one such list in which list(s) does the course figure, or (iii) covered by a wildcard-rule such as “students take three SUBJ 3xx electives”?
  1. Course Changes will necessitate Change in Major/Minor applications if they will need to change existing programming of the ARR(s) in order to satisfy a specific requirement or requirement-option choice.
  2. Course Changes will not necessitate Change in Major/Minor applications if they will all be picked up as desired in the major/minor by an existing elective-rule, or if existing programming of the ARR(s) will not need to be altered in light of the Course Changes.
  3. Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes, even if Change in Major/Minor applications are not required.
  • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, Registration & Records undertakes to make course-changes approved by AC no later than February of one academic year, effective as early as the Fall semester of the following academic year, and course-changes approved by AC no later than March of one academic year, effective as early as the Spring semester of the following academic year; but changes in major/minor programming must be approved no later than December of one academic year in order to become effective as early as the Fall of the following academic year.

  • Please ensure that all supplementary documents entailed by your Course Change application are also submitted within your application-package under the same Unique Number.
  • The Permtag application is used by an Interdisciplinary Program seeking to add a “tag” to the Course Attributes of an existing course and to include the course in major(s)/minor(s) of the IDP. The tag enables students majoring or minoring with the IDP to search in the Class Schedule in LOCUS for classes listed under other academic units’ Subject Area Codes. (Tags should not appear on courses not included in the IDP major/minor in question, but the tag as a Course Attribute is separate in LOCUS’s programming from the Academic Requirements Reports of majors and minors.)

  • The heading information of the Permtag form corresponds to the heading information of the Summary Memo eForm. We recommend that you draft in advance all the application-forms that will be part of your application-package, including any Permtag forms needed, omitting only temporarily the Unique Number.

  • After you submit your Summary Memo, copy the Unique Number it generates for your application-package onto each of your application-forms, including any Permtag forms needed. Then upload the application forms and all supplementary documents, and index all items by the Unique Number of the application-package.

  • Coding information for the existing course (item 1) may be consulted in the Course Catalog in LOCUS and information about courses’ current roles in majors and minors in the Academic Requirements Outlines to which you can navigate from the portal-page that displays when you’ve logged in to LOCUS.

  • The rationale in item 3 of the application-form should be as full as needed to make clear your plans for the course and its role(s) in the major(s)/minor(s) (specifically required course or requirement-option: since students’ Academic Requirements Reports function by Subject Area Codes, not the interdisciplinary tags, interdisciplinary majors and minors normally are programmed in terms of individually required courses and requirement-option lists, not “electives” in LOCUS’s sense), and to demonstrate the merits of the changes. The Summary Memo’s brief statement in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.

  • Item 4 registers, and should highlight, the role(s) the tagged course will have in the IDP’s major(s)/minor(s), but also the specifics of the broader question in item 1 (including any departmental major(s)/minor(s) in which it may serve as an elective, in LOCUS’s sense, by wildcard programming, in contrast to the IDP major(s)/minor(s): see note 5 above). Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes.

  • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 4) flags these considerations for other reviewers.

  • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, since programming of IDP major(s)/minor(s) is necessarily at stake in a Permtag application (see note 5 above), Registration & Records undertakes to make Permtag applications approved by AC no later than December of one academic year, effective as early as the Fall semester of the following academic year.

  • Please ensure that all supplementary documents entailed by your Permtag application are also submitted within your application-package under the same Unique Number.
  • The Newcross application is used by a Department or Interdisciplinary Program seeking to create a new course number in a Subject Area Code of its own, for purposes of cross-listing an existing course. Typically cross-listing is desired when members of different departments or programs will be called on to teach, in substance, the same course; courses required for Interdisciplinary Programs’ majors or minors may need to be cross-listed with departmental courses, but usually tagging suffices instead (for tagging, use the Permtag form).

  • The heading information of the Newcross form corresponds to the heading information of the Summary Memo eForm. We recommend that you draft in advance all the application-forms that will be part of your application-package, including any Newcross forms needed, omitting only temporarily the Unique Number.

  • After you submit your Summary Memo, copy the Unique Number it generates for your application-package onto each of your application-forms, including any Newcross forms needed. Then upload the application forms and all supplementary documents, and index all items by the Unique Number of the application-package.

  • Coding information for the existing course (item 1) may be consulted in the Course Catalog in LOCUS, and information about its current role(s) in majors and minors in the Academic Requirements Outlines to which you can navigate from the portal-page that displays when you’ve logged in to LOCUS. We need to be fussy about all the elements of the existing course, because the new, cross-listed course will need to match it in all respects and be coded as an alternative for any Electives the “parent” course satisfies.

  • Please ensure that the “home” department of the “parent” course is identified in item 2.b of the Summary Memo so that its signatory will be included in the routing of the submission-package.

  • The rationale in item 2 of the application-form should be as full as needed to make clear your plans for the course and demonstrate the merits of the new cross-listing. The Summary Memo’s brief statement in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.

  • Item 3 states for the new course in the submitter’s Subject Area Code the basic identifying information that will have to be created in LOCUS. The Subject Area Code, obviously, will be different from that of the pre-existing course; the Course Number in the submitter’s Subject Area Code may or may not be the same as the number of the pre-existing course. All other parameters of the new course, however, should match those of the pre-existing course.

  • Item 6 provides the space to distinguish whether the existing course is specifically required, a requirement-option, or an elective in its current major/minor inclusions, as well as to add the new cross-listed course and its status in any additional majors/minors it will implicate. All the majors/minors will need re-programming so as to include interchangeably both the pre-existing course and the new cross-listed course. Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes.

  • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 8) flags these considerations for other reviewers.

  • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, since cross-crediting the now cross-listed courses will necessitate re-programming of major(s)/minor(s) (see note 8 above), Registration & Records undertakes to make Newcross applications approved by AC no later than December of one academic year, effective as early as the Fall semester of the following academic year.

  • Please ensure that all supplementary documents entailed by your Newcross application are also submitted within your application-package under the same Unique Number. Particularly, please ensure that the CI Form for this new cross-listed course duplicates all coded information from the pre-existing “parent” course: consult the Course Catalog entry in LOCUS.
  • Your application package is required to include one before-and-after grid for every major and for every minor that will be affected by the curricular changes being considered.
  1. The structurally complete, clear graphic presentation by the grids concisely shows reviewers the academic context of your proposed curricular changes, complementing your verbal statement why the changes are desirable.
  2. If any new programming of your major(s)/minor(s) will be involved, the grids will also facilitate it and ensure the revised structure of the major or minor will be understood in the same terms by all.
  3. The section-specific Temporary Tag/Cross-list requests also need the same information so as to ensure students receive program-credit correctly.
  • Please note that a single course may figure in more than one major or minor: one grid will be required for each major and for each minor concerned in the application-package. On the other hand, separate course-applications within the package may be concerned in the same set of major(s) and minor(s): only one grid per major or per minor should be submitted with the application-package, each accounting for the full set of courses involved.
  • The grid is organized according to the operations by which students’ Academic Requirements Reports are programmed in LOCUS.
  1. “Individually required courses” are the ones that normally every student must complete successfully in order to earn the major or minor. Conceptual groups of individually required courses may be described by lists within the category (see sample grid for DANC-BA).
  2. “Requirements with options” permit students choices within sets of individually specified courses. A single major/minor may include more than one different requirement-option choice, according to its conceptual structure. Requirements for choices may be structured in terms of the course or of the credit-hour. (See sample grid for DANC-BA.)
  3. “Electives” are courses students may use to complete the course- or hours- requirements of the major or minor, when their choice is constrained not by a list of specified courses but by a Subject Area Code or level of courses within the Subject Area Code (e.g., 4 credit-hours DANC 2## or DANC 3##: see sample grid for DANC-BA).
  • Note for Interdisciplinary Programs: since students’ Academic Requirements Reports function by Subject Area Codes, not the interdisciplinary tags (tags function only within LOCUS’s Class-Search operations in the Class Schedule), interdisciplinary majors and minors are programmed in terms of individually required courses and requirement-option lists.
  • The current programming in LOCUS of your major(s)/minor(s)’ Academic Requirements is reflected by the Academic Requirements Outlines (follow links from the portal-page after you log in to LOCUS). We recommend that all departments and interdisciplinary programs prepare charts for each of the majors and minors you oversee, reflecting current coding, and store them for ready reference in a drive shared by your fellow faculty-members. When you begin to prepare any curricular-change application, compare your reference-charts and those of any other parties concerned against the AROs for the current catalogue, resolve any discrepancies in consultation with the Associate Dean for Academic Affairs, and use the corrected information in the “Current major/minor” column.
  • Depending on the complexity of the curricular changes you are proposing, the “Proposed changes” column may identify proposed changes briefly (e.g., “add new course SUBJ xxx to Requirement-Option Choice 2”) or re-draw the category with a new list. Please state “no change” when the category should not change.
  • A sample grid for the 2017-18 form of the B.A. in Dance is posted by way of illustration:

 

Item

Current Major/Minor

Proposed Change(s)*

Major/Minor title

Dance (DANC-BA) [2017-18 programming as example]

 

Individually required courses (i.e., all students must take each course)

Foundational Courses:
DANC 250: Dance History
DANC 270: Dance Kinesiology
THTR 321C: Costuming Practicum
THTR 321E: Electrics Practicum

Synthesis:
2 credit-hrs DANC 323: Rehearsal and Performance
DANC 360: Dance Pedagogy
DANC 370: Composition: Dance
DANC 380: Senior Showcase Capstone
DANC 394: Internship in Dance

 

Requirements with options (e.g., students must take 2 of 5 listed courses)

Applied Courses, Ballet: total 8 credit-hours
DANC 341: Intermediate Majors Ballet
DANC 343: Advanced Majors Ballet

Applied Courses, Pointe: total 4 credit-hours
DANC 312: Pointe I
DANC 314: Pointe II

Applied Courses, Modern Dance: total 4 credit-hours (2 hrs at each level)
DANC 224: Majors Modern II
DANC 324: Majors Modern III

 

Elective courses (i.e., programmable by wild-card rules, rather than by identifying specific courses required or for students to choose among)

4 credit-hours DANC 2## or higher-level (DANC 3##)

 

Credit Hours

40

 

Other changes

   

Proposed effective date

n/a

Fall, __________