草莓社区

Skip to main content
Back to LUC.edu
College of Arts & Sciences Academic Council
Request Info Visit Apply

Instructions for Temporary Tag/Cross-listing Requests

What does a Temporary Tag/Cross-listing do?

  • 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.
    • Such 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. (If all sections of a course would appropriately be included in a certain major/minor, the course should be permanently included in the major/minor: paired requests to make two departmental courses equivalent or else to tag a departmental course and add it to each interdisciplinary major/minor concerned should be made through the  platform and the  platform; they may be bundled.)
    • Temporary Tag/Cross-List requests also may be used to fill in the gap between the Academic Council's approving a permanent tag/inclusion or a permanent cross-listing and the change's becoming effective.
    • The Temporary Tag/Cross-List Request, when approved, generates a record for the Dean’s Office whereby students’ Academic Advisors may confirm and "direct" the credit to their major or minor individually. LOCUS does not automate this function for semester-specific inclusions.
  • An approved Temporary Tag/Cross-Listing may or may not be visible in LOCUS. The record in the Dean's Office and the Academic Advisors' interventions applying Individual Directives to students' ARRs are the most substantively important outcomes of the process for the sake of students' academic records and are secured by approval of a Temporary Tag/Cross-List Request. But addionally:
    • if the temporary tag/inclusion by an Interdisciplinary Program is applied for with enough lead-time, the IDP’s tag can be added to the class-section’s Class Attributes in the Class Schedule display. Any such temporary tags are searchable in the Class Schedule, in just the same way permanent tags are searchable;
    • cross-listed sections, however (temporary or permanent), require the academic units’ schedulers to work together and submit a  to Registration & Records. Listing both departmental course-numbers in the Class Schedule means that students can search with either subject-area code and find the joint section. Cross-crediting, via Individual Directive or permanent coding of the major/minor, is needed to ensure students receive the course's credit in the correct terms of their own major/minor declarations. Both semester-specific and permanent cross-crediting requests are to be made through CIM: respectively, they are handled by a (see further below) or by the combination of a request and a request.

Who initiates a Temporary Tag/Cross-listing request?

The Temptag/Tempcross application may be submitted either by the “home” academic unit of the class-section sought to be temporarily tagged or cross-listed, or by the “second unit” seeking to include it.

What are the deadlines?

  • Temporary Tag and Temporary Cross-list Requests are reviewed and processed on a rolling basis.
  • Ideally, the academic units partnering on a semester-specific basis so that specified class-sections may be credited to specified major(s)/minor(s) in which the course in question is not ordinarily included - the class-offerers and the class-adders - agree together and pursue their Temporary Tag or Temporary Cross-list Request well in advance of registration-season for the semester in which the class-sections are to be offered.
  • If a temporary tag/inclusion by an Interdisciplinary Program is applied for with enough lead-time before the end of the registration-period for the semester in which the class-section is to be offered, subject to Registration & Records' workflows, the IDP’s tag can be added to the class-section’s Class Attributes in the Class Schedule display.
  • If a temporary cross-listing/inclusion by an academic Department is applied for with enough lead-time before the end of the registration-period for the semester in which the class-section is to be offered, subject to Registration & Records' workflows, the academic units' schedulers have the option of working together to submit to Registration & Records a  form so as to set up a Combined Section. 
  • If a Temporary Tag or Temporary Cross-list Request is applied for and approved later in the registration-period or even during the semester in which the class-section is being offered, the Dean's Office can add the approved crediting of the class-section to the major(s)/minor(s) to its records, so that students pursuing the major(s)/minor(s) can ask their Academic Advisors to "direct" the credit for the section to their major or minor individually. It is preferable, however, for the Temporary Tag or Temporary Cross-list Request to have been pursued in advance.

Using Miscellaneous Requests in CIM for a Temporary Tag/Cross-Listing

    • Effective 6 November 2025, the section-specific, semester-specific Temporary Tag and Temporary Cross-List requests are to be submitted through the portal in CIM.
    • The landing-page for CIM's  platform presents:
      • a SEARCH button with write-in window
        • Type in a Subject Area Code used at Loyola, with * wildcard following it, to get all courses in that Subject Area for which Miscellaneous Requests have been submitted.
        • Type in *temporary*, with two * wildcards, to get all Temporary Tag and Temporary Cross-List requests that have been submitted titled as the form requests.
      • a pulldown menu of Quick Search requests by Status of the individual Request.
      • a PROPOSE NEW MISCELLANEOUS button
        • Click to open a blank form through which a new Miscellaneous Request may be proposed. Click the pull-down menu arrow in the Request Type box at the head of the form: options for the Temporary Cross-List and Temporary Tag requests are at the bottom of the list.
      • a results-window
        • Click on the heading in the result-window's banner, to organize the result listings by Request Code number or else to alphabetize them by Request Type, [Request] Title (see further below), step of its Workflow at which the request currently resides, or status of the Request.
        • Click on a specific course in the results-window to open CIM's representation of the current state of the Request.
    • Preliminary steps - before starting workflows in CIM:
      • Submitters design the curricular changes they intend: members of the academic units concerned identify the value of the specific class-sections, offered in specific semesters, to major(s)/minor(s) in which the courses are not permanently included, as applicable. Distinguish the mechanisms for semester-specific inclusion of the specific class-section that are appropriate to use:
        • Temporary tags mark the semester-specific inclusion of specific class-sections in interdisciplinary major(s)/minor(s) that do not otherwise include that course.
        • Temporary cross-listings are set up to make visible the semester-specific inclusion of specific class-sections in departmental and interdepartmental major(s)/minor(s) that do not otherwise include that course.
        • Pertinent terms are discussed further on the page of Concepts and Terms.
      • Formalize preliminary approval of each course-proposal with its home-unit and partner-unit(s) as applicable, pursuant to the parties' internal processes.
    • Either the academic unit offering the class-section or the academic unit seeking to include the class-section in its major(s)/minor(s) may initiate a Temporary Tag/Cross-List Request.
    • When design and preliminary approvals are complete, log in to CIM's  portal.
      • Click the green Propose New Miscellaneous button to open a blank form through which a new Miscellaneous Request may be proposed: a new Miscellaneous Request Management form will open.
      • First step: in the Request Type box at the head of the form, click the pull-down menu arrow: options for the Temporary Cross-List and Temporary Tag requests are at the bottom of the list. Select the one you want.
      • If you are making a Temporary Cross-List request, proceed as follows. All red-rimmed input boxes must have their responses filled in, or the application will not be able to advance. All grey-rimmed input boxes should be filled in if the information applies, but may be left blank if the information is not applicable. Hover the cursor over the greyish circular ? buttons to see definitions or instructions for specific items, or click on the ? button to open a dialog-box with the same text; close dialog-boxes by clicking the red ⊗ button in their corner or by clicking a new ? button.
        • As its ? button instructs, the red-rimmed Request Title box should be filled out with the two course numbers in the format [Subject Area Code] [Course Number], separated by a slash, then the text "Temporary Cross-List," e.g., BIOL 395/CHEM 396 Temporary Cross-List.
        • If you can serve as contact-person concerning the proposal, you are not "submitting on behalf of someone else"; if you cannot serve as contact-person, check the box "yes" and select the appropriate contact-person from the pull-down menu in the Proposal Contact box.
        • As its ? button instructs, the request should list every academic unit whose course will be part of the cross-listed set in the Academic Units boxes, both home-units of the major(s)/minor(s) that otherwise already include the course and the home-units whose major(s)/minor(s) will secure use of the specific class-section through the present request: use the green ⊕ button to add Unit-boxes as needed, and select from the pull-down menu.
        • As its ? button instructs, the request should list as Academic Group(s) every School within which the participating Academic Units are located: select each School from the pull-down menu, using the green ⊕ button to add Group-boxes if needed.
        • Select the term in which the cross-listed class is to be offered from among the Temp Tag/Cross-List options at the bottom of the pull-down menu as the Effective Term.
        • Click the green ⊕ button in the red-rimmed Enrollment Course box and use the interactive menu to select the Course that will serve as the Enrollment Section of the cross-listed set. (Either select School, then Subject Area, then active Course and click Add Selected, or write in the [Subject Area Code] [Course Number] and click Add Course.) Click Close when done. Fill in the specific Section Number in the red-rimmed Section Number box. If the section has a Topic title, fill it in to the grey-rimmed Special Topic box.
        • As many times as needed, click the green ⊕ button in the red-rimmed Non-Enrollment Course box and use the interactive menu to select the Course/s that will serve as non-enrollment section/s of the cross-listed set. (Either select School, then Subject Area, then active Course and click Add Selected, or write in the [Subject Area Code] [Course Number] and click Add Course.) Click Close when done. Fill in the specific Section Number for each course in the red-rimmed Section Number box.
        • Your two-sentence maximum summary of the proposed change should describe the temporary crediting of the class-section in the requested major(s)/minor(s) where it is not already permanently included, via the semester-specific cross-listing.
        • Your brief description of the course or special-topic should include concrete reasons why the section is appropriate to include in the requested major(s)/minor(s) where it is not already permanently included, via the semester-specific cross-listing.
        • The trios of red-rimmed boxes Specifically Required, Requirement-Option Choice, and Elective (use the green ⊕ button to add rows as needed) show how the class section is to function in student's major(s)/minors(s) in terms of the three categories of programming within ARRs, for both those major(s)/minor(s) already permanently including the course and those major(s)/minors(s) that will be using the specific course-section by virtue of its temporary cross-listing. Where a class-section will not be specifically required or a requirement-option choice, for example, but will serve only as an elective, write "none" for the options that do not apply.
        • If a section-syllabus or other document helps support the request, attach it using the green Attach File button: click and navigate in the interactive box that opens to the folder where the document is stored, select it, and click "open." Repeat as needed.
        • When all items of the Request are complete and correct, click the green Start Workflow button.
      • If you are making a Temporary Tag request, proceed as follows. All red-rimmed input boxes must have their responses filled in, or the application will not be able to advance. All grey-rimmed input boxes should be filled in if the information applies, but may be left blank if the information is not applicable. Hover the cursor over the greyish circular ? buttons to see definitions or instructions for specific items, or click on the ? button to open a dialog-box with the same text; close dialog-boxes by clicking the red ⊗ button in their corner or by clicking a new ? button.
        • As its ? button instructs, the red-rimmed Request Title box should be filled out with the course number of the section to be tagged, in the format [Subject Area Code] [Course Number], then the text "Temporary Tag," e.g., THEO 280 Temporary Tag.
        • If you can serve as contact-person concerning the proposal, you are not "submitting on behalf of someone else"; if you cannot serve as contact-person, check the box "yes" and select the appropriate contact-person from the pull-down menu in the Proposal Contact box.
        • As its ? button instructs, the request should list in the Academic Units boxes the home-unit of the course whose section is to be tagged temporarily pursuant to the present request, and every academic unit permanently associated with that course (by equivalency or permanent tag), plus the : use the green ⊕ button to add Unit-boxes as needed, and select from the pull-down menu.
        • As its ? button instructs, the request should list as Academic Group(s) every School within which the participating Academic Units are located: select each School from the pull-down menu, using the green ⊕ button to add Group-boxes if needed.
        • Select the term in which the cross-listed class is to be offered from among the Temp Tag/Cross-List options at the bottom of the pull-down menu as the Effective Term.
        • Click the green ⊕ button in the red-rimmed Course box and use the interactive menu to select the course whose section is to be tagged temporarily pursuant to the present request. (Either select School, then Subject Area, then active Course and click Add Selected, or write in the [Subject Area Code] [Course Number] and click Add Course.) Click Close when done. Fill in the specific Section Number in the red-rimmed Section Number box. If the section has a Topic title, fill it in to the grey-rimmed Special Topic box.
        • Your two-sentence maximum summary of the proposed change should describe the temporary crediting of the class-section in the requested major(s)/minor(s) where it is not already permanently included, via the semester-specific tag request.
        • Your brief description of the course or special-topic should include concrete reasons why the section is appropriate to include in the requested major(s)/minor(s) where it is not already permanently included, via the semester-specific tag request.
        • The trios of red-rimmed boxes Specifically Required, Requirement-Option Choice, and Elective (use the green ⊕ button to add rows as needed) show how the class section is to function in student's major(s)/minors(s) in terms of the three categories of programming within ARRs, for both those major(s)/minor(s) already permanently including the course and those major(s)/minors(s) that will be using the specific course-section by virtue of its temporary cross-listing. Where a class-section will not be specifically required or a requirement-option choice, for example, but will serve only as an elective, write "none" for the options that do not apply.
        • Check the box for the interdisciplinary program whose major(s)/minor(s) will include the temporarily tagged class-section, in the specified semester, in virtue of the present request.
        • If a section-syllabus or other document helps support the request, attach it using the green Attach File button: click and navigate in the interactive box that opens to the folder where the document is stored, select it, and click "open." Repeat as needed.
        • When all items of the Request are complete and correct, click the green Start Workflow button.
    • When an application has been launched in its CIM workflow, each new approval sends the application forward. CIM automatically sends e-mail to the individual designated for the role whose approval is needed. This message will contain a link to the specific one of CIM's Approve Pages at which the application is waiting. The role is indicated in the link. Please promptly go to the Approve Page in question.
      • From the Pages Pending Approval list, please select each individual request in turn: it will open in the Page Review window below. Read through the Page and confirm that the application presented is appropriate in its terms and correctly presented, in particular that it conforms to the governing rules of the body as whose representative you serve in your role in this list. The notification's request to you in your role is whether the body's consensus has been properly secured in favor of the application.
      • If your role as approver includes making any edits within the Page, use the leftmost, blue "edit" button in the taskbar to open an editable window in which you can make appropriate changes and annotate them in the "Reviewer Comments" box at the bottom. Click the "save changes" button when you are done.
      • If you identify changes that should be made by a previous entity in the workflow, use the middle, red "rollback" button in the taskbar to select the entity to whom the request should be rolled back and in the "Comment/Reason" box to explain why. Click the "Rollback" button to send the request to the appropriate recipient. When the appropriate reconsiderations have been made and the proposal re-approved, CIM will advance the application back to you again. (Or else click "cancel" and abort the rollback, if it's not the appropriate measure to take.)
      • Once the application is in every way as it should be, from the perspective of the entity you represent as approver, use the rightmost, green "approve" button to send the application forward to its next stop on its workflow.
    • All users may search in CIM's platforms for applications in which they have an interest (use the "quick searches" box), and see in the Workflow column at what stop in their individual workflow each application presently rests. The Approval Path includes dates and times at which approval was recorded for the different roles in the workflow. If an application appears to have paused excessively long at a certain step, the user may click on the role in the workflow column and generate an e-mail to the person assigned to that role, to reach out and offer help getting the application back into progress.
    •