Subjects
Note: Information must be written in the present tense, third person, using full sentences (unless the field does not require full sentences).
Marketing speak, unsubstantiated non-factual claims, and jargon should be avoided.
Fields that do not comply with the format guidelines will not be approved and will therefore either be returned to the faculty for amendment or will be amended by the APO so that they do comply.
| Field name | Description and format | Where to update | Requires APO: CIS approval | Publicly available (e.g. online) |
| CASS subject number | Uses the official approved subject number | CASS | n/a | Yes |
| Subject name | Uses the official approved subject name | CASS | n/a | Yes |
| Course area | The course area that 'owns' / administers the subject. Stored in CASS as 'Keyword 1' | CASS | n/a | n/a |
| Teaching responsibility | The name of the organisational unit recorded on CASS as having teaching responsibility. Could be a faculty, school or department. If not specified on CASS, the default is the owning faculty. | CASS | n/a | No |
| Examination responsibility | Identifies if the exams for the subject are 'Centrally conducted' or 'Faculty based' | CASS | n/a | No |
| Replaces which subject | Used if the subject replaces one or more discontinued subjects on student study plans. Lists the subject numbers of the replaced subject(s). | CIS: CI, Subjects | No | No |
| Default/even-year offering pattern | Formal specification used for setting up default annual availabilities on CASS. Indicate the location, teaching period, mode, year of first offering, and status (confirmed or conditional). | CIS: CI, Subjects | No | Yes |
| Odd-year offering pattern | Formal specification used for setting up odd-year availabilities (if different from default/even-year offering pattern) on CASS. Indicate the location, teaching period, and modes available. | CIS: CI, Subjects | No | Yes |
| Teaching period and year first offered | Indicate the teaching period (Autumn session, Spring session, Summer session, etc.) and year that the subject is first offered, e.g. Autumn session, 2008 Spring session, 2008 Summer session, 2008/09 | CIS: CI, Subjects | No | No |
| Course(s)/major(s) where subject is a core component | A list of all courses and majors where the subject is a core component. It does not need to cover every single course as a CASS extract would. | CIS: CI, Subjects | No | No |
| Prize offered | Indicate the prize(s) available, if any. | CIS: CI, Subjects CIS: SO, Change Request tab | No | No |
| CASS credit points | The credit point value of the subject. | CASS | n/a | Yes |
| Attendance | This field covers basic information relating to hours per week, mode of attendance, e.g. 6hpw, distance, on campus, block, weekly First letter must be in lower case (unless referring to session title) and there must be no full stop at the end of the section Information specific to particular teaching periods/modes, e.g. Summer session, tutorial, etc., should appear in brackets, e.g. 6hpw (Spring session), 9hpw (Summer session) 1hpw (lecture), 3hpw (laboratory) If the attendance information is particularly detailed, colons and/or semi-colons may be required for clarity (this should be avoided where possible, however), e.g. lectures (Summer session): 4hpw x 4wks (2hrs face-to-face; 2hrs blended learning), laboratory (Summer session): 6hpw x 4wks Limit of 20 words (150 characters) Minimum attendance expressed as a percentage belongs in the 'Minimum requirements' field, not this field, e.g. 'Students must attend 80 per cent of scheduled classes to pass the subject.' Note(s) • Changes must go through the APO:CIS approval process before they can be published. • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects CIS: SO, Change Request tab | Yes | Yes |
| Local delivery: standard | Will be used to set up Syllabus Plus each year. Takes the form of a table, indicating Format (e.g. lecture/workshop), Iteration (e.g. 1), Duration (e.g. 2 hr), Max class size (e.g. No limit/30), Ref code (e.g. NVC/NTCVC), Teaching weeks (e.g. 1-14/2-14) | CIS: CI, Subjects | No | Yes |
| Local delivery: block | Will be used to set up Syllabus Plus each year. Takes the form of a table, indicating Format (e.g. lecture/workshop), Iteration (e.g. 1), Duration (e.g. 2 hr), Max class size (e.g. No limit/30), Ref code (e.g. A), Teaching weeks (e.g. 1-14/2-14) | CIS: CI, Subjects | No | Yes |
| Enrolment restrictions | Include details of the courses/majors, etc., that students must (or must not) be enrolled in to do the subject, e.g. 'availability: Graduate Certificate in IT students only', 'availability: Software Engineering major only First word must be 'availability: ' and there must be no full stop the end of the section. Limit of 20 words (150 characters) Note(s) • Changes must go through the APO:CIS approval process before they can be published. | CIS: CI, Subjects | Yes | Yes |
| CASS academic requisites | This field details the compulsory Academic requisites stored in CASS. The brackets, which have to remain, are a result of parsing the requisite rules to display only the Academic requisites. All requisites are prerequisites unless otherwise indicated; a lower case 'c' after the subject code indicates that the subject is a corequisite. Antirequisites do not form part of CASS Academic requisites. | CASS | n/a | Yes |
| Recommended studies | Include details of subjects or experience that students would benefit from having completed, but which don't fall into the compulsory CASS requisite category. The following styles apply: (a) when adding recommended subjects, insert the subject number followed by a single space and then insert the name of the subject (note: the faculty is responsible for keeping this data up to date; it cannot be auto-corrected if, for example, a change occurs in a CASS-stored subject name); (b) do not include requisites which should be part of Admission or Other requisites in CASS; (c) separate subjects with a semi-colon; (d) any other recommended studies should begin with a lower case letter, and be separated by a semi-colon if there is more than one; (e) do not include a full stop at the end; (f) note the text 'Recommended studies: ' will be auto-generated in publications so shouldn't be included in the field data; e.g. 013336 Contemporary Issues in Adult Education; 013709 E-Learning Design; a minimum of 80 per cent in the Basic Mathematics Skills Test Note(s) • Changes must go through the APO:CIS approval process before they can be published. • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects CIS: SO, Change Request tab | Yes | Yes |
| CASS antirequisites | This field details the antirequisites stored in CASS. | CASS | n/a | Yes |
| CASS other requisites | This field details the other requisites stored in CASS, e.g. 'Faculty approval required'. | CASS | n/a | Yes |
| Requisite elaboration/waiver | This field is used if the 'CASS other requisite(s)' need explanation, e.g. to indicate the basis for obtaining Faculty approval, or to explain any circumstances of a requisite waiver. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects CIS: SO, Change Request tab | No | Yes |
| Subject classification | Details the category/strand/program/classification that the subject falls into, e.g. 'Engineering Practice', 'Fields of practice: Electrical Engineering program', 'Disciplinary Strand – Communication and Information Studies – 100 level', 'Elective' This field starts on a new line, begins with a capital, and has no full stop at the end. Limit of 20 words (150 characters) Note(s) • Changes must go through the APO:CIS approval process before they can be published. | CIS: CI, Subjects | Yes | Yes |
| Level | Provides the level this subject is offered at, e.g. 'Undergraduate', 'Postgraduate', 'Undergraduate and Postgraduate' Note(s) • Changes must go through the APO:CIS approval process before they can be published. | CIS: CI, Subjects | Yes | Yes |
| CASS subject level code | The standard letter code used in CASS to indicate the level of a subject. | CASS | n/a | No |
| Linked subjects | Specify any other subjects that the description also applies to. Useful when a subject has a 6cp and 8cp offering but you only want to hand out the one outline in class, e.g. 'Note: This subject outline also applies to 50105 Communication and Information Environments.' Use the actual and complete name of the subject, without abbreviations or ampersands. You cannot use heading tags around the sentence. | CIS: CI, Subjects | No | No |
| Proposal author | The full name of the person who prepared the proposal for submission to Faculty Board. | CIS: CI, Subjects | No | No |
| Subject coordinator and contact details | Provide details in the following format, as required; each component optional. [Subject coordinator's name in full, including any academic title, e.g. 'Dr John Smith', 'John Smith (Lecturer)' [Position] UTS: [xxxx] [Building ID location details] telephone (02) 9514 [xxxx] fax (02) 9514 [xxxx] email [xxxx]@uts.edu.au [Descriptive sentence about preferred means of contact.] Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Teaching staff and contact details | Provide details in the following format, as required; each component optional. [Title][first name][surname] [Position] UTS: [xxxx] [Building ID location details] telephone (02) 9514 [xxxx] fax (02) 9514 [xxxx] email [xxxx]@uts.edu.au [Descriptive sentence about each staff member and preferred means of contact.] Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Assessor | Add the assessor's name in this field. Subject coordinators and assessors are usually appointed at the same time. Assessors work with subject coordinators, acting as peer reviewers to review and improve the appropriateness of assessment tasks. Refer to the Coursework Assessment Policy. | CIS: CI, Subjects | No | No |
| Notes | A brief statement used to alert students to specific issues related to the subject as a whole which may mean that this subject is unsuitable for them and stop them from reading further, e.g This subject requires attendance at a full-day workshop. If students cannot attend this workshop due to other commitments, they are unable to enrol in the subject. Information must be written in the present tense. Limit of 50 words (375 characters) Note(s) • Changes must go through the APO:CIS approval process before they can be published. • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects | Yes | Yes |
| Description | Write the subject description here. Information must be written in the present tense, third person, using full sentences, e.g. This subject covers ... Students learn to ... (rather than 'You will learn to ...) Limit of 300 words (2,250 characters) Note(s) • Changes must go through the APO:CIS approval process before they can be published. • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects CIS: SO, Change Request tab | Yes | Yes |
| Teaching and learning strategies | This information should build on information already given in the Attendance field. What sort of activities will be undertaken in tutorials, practicals, etc. Information should cover all modes of delivery. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects CIS: SO, Change Request tab | No | Yes |
| Content (topics): generic | Indicate the subject content (topics) as a list of headings (topic names or numbers, e.g. 'Topic 1' or 'Management') with a sentence briefly describing the topic, or as a bulleted list. | CIS: CI, Subjects CIS: SO, Change Request tab | No | Yes |
| Field group: Subject learning objectives (SLOs) | The subject learning outcomes or objectives (SLOs), i.e. the professional, personal or academic knowledge, skills and values that students are expected to be able to demonstrate on completion of the subject. This data is stored in three fields updated via: CI / [subject code] / Graduate Attributes / Learning objectives: Code; Description; Short description. A standard SLO lead-in sentence can be added in CI / Course Area / SLO lead-in sentence. If it contains data, it will appear above the list of SLOs. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | n/a | n/a | |
| Graduate Attributes / Learning objectives / Code | Insert a code for the subject learning objective (SLO). The code should be an whole number or a letter (upper or lower case). Currently there is no system validation on codes but they should obviously be unique and in a sequence with no gaps. There is no limit to the number of SLOs that can be entered. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects, Graduate Attributes tab CIS: SO, Change Request tab | No | Yes |
| Graduate Attributes / Learning objectives / Description | Insert the full subject learning objective Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects, Graduate Attributes tab CIS: SO, Change Request tab | No | Yes |
| Graduate Attributes / Learning objectives / Short description | Insert a shortened form of the full subject learning objective (the short description appears in the drop-down list with the SLO code when a link is being set up in a subject assessment task between an assessment criteria and an SLO via the criteria linkages table (CLT)) Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects, Graduate Attributes tab | No | Yes |
| Contribution to the development of graduate attributes | The format of this field has changed because course intended learning outcomes should now be stored via CIS / Course / Graduate Attributes / Intended learning outcomes. The field can be left blank (or blanked if there is already data in it: this can be done globally by CIS Admin) or can now be used to further explain the list of CILOs, e.g. when a subject is shared across several courses all with different CILOs, and the development of graduate attributes. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects CIS: SO, Change Request tab | No | Yes |
| Additional subject costs | Include a brief sentence about additional costs that students undertaking this subject incur, such as cost of field trips, materials, excursions, travel, accommodation, etc., e.g. Subject notes cost $20 (purchase number: CN12345) and are available from the UTS Union shop, level 3, building 1, City campus. Limit of 60 words (450 characters) Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Field trips | Outline details of field trips required as a component of this subject. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Result type | Defines the subject as either 'Graded, no mark', 'Graded, with mark', 'Pass/ Fail, no mark', 'Pass/ Fail, with mark'. | CASS | n/a | Yes |
| Assessment: generic information | It is a requirement that subject outlines have a brief description of each assessment task, its percentage worth, and when it is due. The 'Assessment: generic information' field is provided so subject coordinators can use it to avoid repetition of information in the individual task entries that applies to all tasks, e.g. information on the means of submission or the penalty for late submission which may be the same for all tasks. There are also five other assessment-related fields that should be used for specific information that applies to all (relevant) assessment tasks. The five fields are: 'Plagiarism detection software', 'Moderation of marks', 'Assessment feedback', 'Examination material and equipment' and 'Supplementary assessments'. The requirement to have an entry in any of these five fields depends on the nature of the subject and its assessment regime. This field and the five other assessment-related fields should only be used where the arrangements for the subject are different from the default arrangements that apply to all subjects as described in the faculty generic information that is appended to the outline (in some faculties) or published as a faculty study guide (in others). A reference to this study guide should be part of each subject outline disclaimer (the 'Disclaimer' field is editable in CIS). The information in the 'Assessment: generic information' field should not cover topics that are covered by the five other assessment-related fields. Information should cover specific subject requirements on matters such as assignments, late penalties, provisions for student negotiation of assessment tasks, etc., that go beyond or are exceptions to the faculty-specific assessment information. This information should apply to all assessment tasks in the specific subject only. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Assessment tasks: Display status checkbox | The checkbox indicates which of the assessment tasks are included in the subject outline. This allows differences instances of a subject (e.g. default, block, short) to use a different set of assessment tasks. All assessment tasks are displayed on the 'Manage tasks' screen in every instance. Tasks can be ticked on or off depending on the instance. Weight validation occurs on the ticked on tasks, so ticked on tasks must total 100. | CIS: SO, Assessment Tasks tab / Manage tasks | No | Yes |
| Assessment tasks: Heading | Add the heading. Note: 'Assessment task #: ' will be automatically inserted before the heading on generation so only add the actual heading, e.g. 'Interactive photo-essay', which will be displayed as, for example, 'Assessment task 2: Interactive photo-essay'. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: SO, Assessment Tasks tab / Manage tasks CIS: SO, Change Request tab | No | Yes |
| Assessment tasks: Type | What type of assessment is the task? Choose a type (i.e. 'Essay', 'Report', 'Exam', 'Test', etc.) from the drop-down list in the 'Type' column, if required. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: SO, Assessment Tasks tab / Manage tasks CIS: SO, Change Request tab | No | No |
| Assessment tasks: Groupwork | Does the assessment task involve groupwork? Choose 'Group', 'Individual', or 'Combined', etc., from the drop-down list in the 'Groupwork' column, if required. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: SO, Assessment Tasks tab / Manage tasks CIS: SO, Change Request tab | No | No |
| Assessment tasks: Intent | Add the purpose of the assessment item. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: SO, Assessment Tasks tab CIS: SO, Change Request tab | No | Yes |
| Field group: Assessment tasks: Objectives | Data displayed under the 'Objectives' heading is automatically drawn from data held in the task's 'Criteria linkages' table (SLO and CILO columns) and the 'Assessment task SLO lead-in sentence' and 'Assessment task CILO lead-in sentence' | No | Yes | |
| Assessment tasks: Weight (%) | Add the weighting as a whole number, i.e. a percentage out of 100, e.g. '35'. Do not include the percentage symbol. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: SO, Assessment Tasks tab / Manage tasks CIS: SO, Change Request tab | No | Yes |
| Assessment tasks: Task | In this field provide details about the nature of the assessment task. Students need to be given enough information so they can undertake the task. This can either be provided in this field, or a reference can be made to an ancillary document that contains the information. The information about the task given in the outline can be split between this field and the 'Further information' field. The 'Task' field should not contain information for which a specific field exists. Information about length and assessment criteria can be given here, provided these fields are blank, i.e. so information isn't duplicated in the subject outline. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Assessment Tasks tab | No | No |
| Assessment tasks: Length | Add the length of the assessment task, as applicable, e.g. '4000 words', '30 minutes', etc. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Assessment Tasks tab | No | Yes |
| Assessment tasks: Criteria | If the criteria linkages table is not being used, the assessment criteria can instead be added to this field. Data is often presented as a bulleted list. If the criteria linkages table is being used, this field can be left blank or it can contain data that introduces/explains the criteria linkages table. If there is data in this field it will appear above the 'Criteria linkages' table (if any) in the subject outline PDF. It should therefore not duplicate data held in the criteria linkages table. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: SO, Assessment Tasks tab CIS: SO, Change Request tab | No | Yes |
| Assessment tasks: Criteria linkages | The criteria linkages table is where the assessment criteria is set up and then linked to the subject's SLOs and the parent study package's CILOs. Each assessment criterion is entered as a row in the criteria linkages table. There is no maximum number of assessment criteria per assessment task. The criteria linkages table comprises the following columns: 'Criteria', 'Weight (%)', 'SLOs', 'CILOs', 'Level', 'CR' (see the documentation for an explanation of what data is required). If the criteria linkages table is set for display, only the 'Criteria', 'Weight (%)', 'SLOs', and 'CILOs' columns are displayed. If there are linked CILOs in the criteria linkages table and there is a CILO lead-in sentence stored in Course Area, then the CILOs are displayed as a bulleted list with a lead-in sentence, after the SLOs under the 'Subject objectives' heading in the Subject Outline PDF. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: SO, Assessment Tasks tab CIS: SO, Change Request tab | No | No |
| Assessment tasks: Due date | Add the due date by choosing from a series of drop-down lists. Specify the due date type (i.e. 'Custom', 'Date', 'Date/Time', 'Week', 'Week range', 'In Class', 'Exam period', 'Progressive', 'Negotiated', 'Practicum period'); depending on your choice, you'll then be able to specify the date, time, week, etc., and/or add free text data. Ticking the checkbox beside 'See Further information', will add '; see Further information' to the data, e.g. if you choose 'Negotiated' and tick the checkbox, 'Negotiated; see Further information' will be displayed in the PDF. Any substantial further information about the due data can then be added to the 'Further information' field. Alternatively, you can use the 'Free text' field to add further information about the due date. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Assessment Tasks tab | No | No |
| Assessment tasks: Further information | This field can be left blank. If required, add any further information that applies to the assessment item, e.g. further information about the details of the due date, which is not covered in the other assessment task fields. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Assessment Tasks tab | No | No |
| Assessment task approved nominal summary | Updates to this table are made via the 'Assessment Tasks' tab. The table uses the following limited set of assessment task fields: Heading Objectives (drawn from the criteria linkages table and including lead-in sentences, as required) Weight (%) Length Task Assessment criteria/Criteria linkages The nominal summary table appears only in the 'Detailed subject description' page in the online handbook. | CIS: SO, Assessment Tasks tab | n/a | n/a |
| Minimum requirements | Provide details, covering all modes of attendance, of any minimum requirement to pass the subject, such as attendance, practicals, compulsory assessment items, etc. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | CIS: CI, Subjects CIS: SO, Change Request tab | No | Yes |
| Program: Week/session | The first column of the Program identifies the week/session described in that row (it is not required, but recommended). Add the session week number for weeks other than VC's week; and a '-' for VC's week. Where a subject has two sessions a week they can be labelled 1A and 1B. For block mode subjects the session number can be given, or the time span of the session (the date should be added in the 'Date' field, not here). Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Program tab | No | No |
| Program: Date | The second column of the Program allows the date to be specified. The autofill function can be used, or subject coordinators can manually enter the dates. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Program tab | No | No |
| Program: Description | This field (column 3) describes what the student will experience for this attendance session. It may be appropriate to have headings such as: Lecture; Laboratory; Tutorial; Pre-reading; References; etc., with text under each heading. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Program tab | No | No |
| Program: Notes | Coordinators can use this field (column 3 under 'Description') for the reading list, or for information about tutorials when the description field has been used for lecture descriptions. Assessment task submission dates should not be given here as they should have already been specified under each assessment task. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Program tab | No | No |
| Content: additional | The text entered in this field appears without a heading immediately below the Program table or below the heading if no data has been added to the table fields. It can be used, for example, to explain the division of material between the Description and Notes fields, to give a key to abbreviations used in the Program table, to explain why there is no Program table, or to refer students to further documentation. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Typical availability | A list of each session and location that the subject is usually offered. This field is different to the CASS stored 'Availability' field, in that you can use it to indicate the typical offering pattern, without necessarily committing to that offering. 'Typical availability' is defined in the handbook as 'while the subject is usually offered according to the specified pattern, there is no guarantee'. The field should be amended as required, using the following formatting guidelines. Specify the session when the subject is typically offered (possible values are 'Spring session', 'Autumn session', 'Summer session', 'Winter session', etc.), insert a comma and a space and then specify the location the subject is typically offered at (possible values include 'City campus', 'China', 'Hong Kong', 'Japan', etc.). Separate each session/location entry with a soft paragraph return. If required, an explanatory sentence beginning on a new line can be included, e.g. Autumn session, City campus Spring session, City campus May be offered in Summer session, City campus depending on student numbers. Information must be written in the following order: (where offered) City campus, Kuala Lumpur, China, Hong Kong, Singapore, Taiwan, Indonesia, Thailand; (when offered) Autumn session, Spring session, Summer session, Winter session. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | CIS: CI, Subjects | Yes | Yes |
| First-year experience videos | If available, the links to YouTube commentary videos from students and academics about the first-year subject are provided, e.g. 'View commentary from students and academics about this first-year subject at: * Student video: www.youtube.com/user/utschannel#p/u/9/nKP5qjt2s4I * Academic video: www.youtube.com/user/utschannel#p/u/7/wo_aZQqpM3w Updated by APO: CIS as required. | Contact APO: CIS | n/a | Yes |
| Footnote(s) | Add any general subject notes to this field that cannot be included in the subject description text paragraph or any other fields. The 'Note(s)' heading will be auto-generated so just include the text of the note in this field. If there is more than one note, add the number followed by a full stop and a space and then the note text, e.g. The subjects 33112 and 33113 replace the full-year subject 33106 Statistical Design and Analysis. or 1. This subject replaces the Spring session of 99619 Clinic – Level 2 and Point Location 2. Always use a capital letter to start and end with a full-stop. This field was formerly the 'Footnote(s)' field. Limit of 80 words (600 characters) Note(s) • Changes must go through the APO:CIS approval process before they can be published. | CIS: CI, Subjects | Yes | Yes |
| Required texts | This field is for resources that students are expected to use. The resources may take the form of notes prepared by the coordinator, or text books that the student is expected to have access to, either by purchase or through the library. The data in this field is normally a short list of resources, each of which will be of value to students for a substantial part of the subject's coverage. Resources that are relevant to a very specific area of the subject are better placed in the 'References' field. Add the list of set texts and other learning resources required for the subject. Citations must be written using the referencing system preferred by your faculty, e.g. Hill, C, Maritime Law, 3rd edn, Lloyds, 1989 Australian Industrial Law Reports, loose-leaf, CCH Pearson, G & Fisher, S, Commercial Law Commentary and Materials, LBC Information Services, 1999 Van den Berg, J (ed.), Yearbook of Commercial Arbitration, Vol 1 & 2, Kluwer, 1976 Limit of 150 words (1,125 characters) Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | Yes |
| Recommended texts | This field is for resources that students may find useful but it is left to the student to decide. The data in this field is normally a short list of resources each of which are of value to students for a substantial part of the subject's coverage. Resources that are relevant to a very specific area of the subject are better placed in the 'References' field. List any recommended texts and other learning resources which students would benefit from buying, but which are available in the UTS: Library, via UTS: Online or as reading materials prepared by the subject coordinator. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | Yes |
| References | This field is used to list the resources that the student is either expected or may wish to access in order to achieve the subject aims in specific topics or to meet specific objectives. However, there are three acceptable fields in which to specify references: 1. They can be listed with full bibliographic information in this field. The advantage of this method is that a code or abbreviation can be used when specifying what references are to be used in specific weeks in the Program section of the outline. A key to the codes used can be given in the 'Content: additional' field. 2. The 'References' field can be left blank and instead full bibliographic details can be provided in the 'Description' field in the week/session of the Program where the materials will be used. 3. Where the reference list is very long, or there is an extensive array of readings for each week, it is acceptable in this field to refer to a separate document, such as a study guide, where full reference information is provided. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | Yes |
| Other resources | This field can be used in addition to, or instead of, the 'References' field. It is provided to enable the separate listing of text-based and other types of resources, as required. The guidelines for the 'References' field also apply to this field as well. Add the list or details of other resources available for the subject, e.g. websites, journals, library resources, etc. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | Yes |
| Additional information for students | An entry in this field is not normally necessary and is discouraged given the array of specific information fields available. If required, provide details of any additional information for students that isn't covered by any of the other fields. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Fee information (contribution for CSP students and Subject EFTSL) | Fee information drawn directly from CASS/SAU | CASS | n/a | Yes |
| Access conditions | Explanatory text and link to the Access conditions stored in Student One. Not editable by faculties. Contact APO: CASS via the Service Desk. | CASS | n/a | Yes |
| Additional guidance | This field should be used only for subjects that have enforced requisites in CASS. It is not displayed in the print handbook. It appears in the online handbook via the [Access conditions] link on the subject description page. Its purpose is to explain to students whether there are any circumstances that would constitute sufficient grounds to make an application to have the requisite waived using e-Request, e.g. When referring to Academic requisites, the data might indicate that the requisite could be taken at the same time as the subject in question, provided the student had completed one of a list of subjects, or if the student had previously attempted the requisite and obtained a mark of at least 45, or details of an alternative way of satisfying the requisite, such as a Credit grade in a specific subject. A student meeting these conditions would need to be advised to submit an e-Request. When referring to Admission requisites, the data might say that the rule was strictly enforced, the only exception being for a student enrolled in a specific course who may be granted access provided a space was available, following submission of an e-Request. When referring to Other requisites, the data might indicate what evidence the student needed to submit or the process that he or she needed to follow to be permitted to enrol in the subject. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | CIS: CI, Subjects | Yes | Yes |
| Use of plagiarism detection software | If plagiarism detection software is used, there should be a statement to that effect in the outline. It can either be made here to cover all relevant assessment tasks, or it can be made in the 'Further information' field of each relevant task. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Edit Main tab CIS: CI, Subjects | No | No |
| Moderation of marks | This field is provided to give subject coordinators a place to make a statement about mark moderation. It can be left blank. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Edit Main tab CIS: CI, Subjects | No | No |
| Assessment feedback | Some information should be provided covering when feedback will be given and what form it will take. This field can be used if a generic statement is appropriate, otherwise the information can be provided in the 'Further information' field of each separate task. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: SO, Edit Main tab CIS: CI, Subjects | No | No |
| Faculty workload metrics | Faculties may use this field to specify the contribution that teaching this subject would make to a staff member's workload allocation. | CIS: CI, Subjects | No | No |
| Examination material or equipment | Students need to be clear about what they are permitted to take into the examination room. This field can be used if a generic statement is appropriate, otherwise the information can be provided in the 'Further information' or 'Task' field of each separate task. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Date last modified/confirmed | The date of the most recent change or validation check was made. | CIS: CI, Subjects | No | No |
| Supplementary assessments | Use this field to make a statement about supplementary assessments or examinations. It can be left blank. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | CIS: CI, Subjects CIS: SO, Edit Main tab | No | No |
| Risk assessment: date | The date the risk assessment occurred. | CIS: CI, Subjects | No | No |
| Risk assessment: name | The name of the person who conducted the risk assessment. | CIS: CI, Subjects | No | No |
| Risk assessment: status | This field should contain one of the following two statements: EHS risks assessed and mitigation strategies identified. or There are no EHS risks in need of a mitigation strategy. | CIS: CI, Subjects | No | No |
| X grade | This field should say 'Yes' if the subject is approved to be awarded a Fail (X) grade by the relevant faculty board. If left blank, it means no X grade has been approved for the subject. No other data should be added here. | CIS: CI, Subjects | No | No |
| Publish (Yes or No)? | All Active subjects are by default 'Yes' so they are available for publication. If you don't want a subject to be available for publication it needs to be marked as 'Publish No'. Only APO: CIS staff can make this change. Note: If you want to phase out a subject, it must be done in CASS, via the APO, not by using this field. | Contact APO: CIS | n/a | n/a |