{"id":37863,"date":"2010-09-24T11:36:06","date_gmt":"2010-09-24T15:36:06","guid":{"rendered":"http:\/\/www.bu.edu\/tech\/?page_id=37863"},"modified":"2012-01-24T19:21:42","modified_gmt":"2012-01-25T00:21:42","slug":"section-schedule-information","status":"publish","type":"page","link":"https:\/\/www.bu.edu\/tech\/services\/cccs\/websites\/www\/non-wordpress\/how-to\/coursedescription\/section-schedule-information\/","title":{"rendered":"Section and Schedule Information"},"content":{"rendered":"

Section and schedule information can be included for scheduled courses by including the attribute show_sections=”Y” specified in your course container’s bub_course or bub_base tag. You can indicate whether to include or exclude unscheduled courses by using the show_unscheduled_courses attribute (see the course container section for details). If you do include section and schedule data, you must set the semester in the bub_base tag – otherwise, the system won’t know which semester’s sections to show.<\/p>\n

Once you instruct the system to retrieve section information, it can be included in the course template by using a set of section_block tags within the course description, like so:<\/p>\n

<!– BEGIN section_block –>
\n{!section_name!}
\n<br \/>
\n<!– END section_block –><\/p>\n

Creating a section block will display each section (A1, B1, etc.) of the course or display nothing if no sections are scheduled. The section_block block only contains information about the section name and instructor. In order to display the times and locations, a schedule_block needs to be created inside of the section_block. For example:<\/p>\n

<!– BEGIN section_block –>
\n{!section_name!}
\n<ul>
\n<!– BEGIN schedule_block –>
\n<li>{!schedule_days!} {!schedule_time_start!}-{!schedule_time_end!}<\/li>
\n<!– END schedule_block –>
\n<\/ul>
\n<!– END section_block –><\/p>\n

The reason for the block structure is that a course can have multiple sections, and a section can have multiple schedules. As with the course templates, you can mix and match special variables (described below) and arbitrary HTML; each block will be parsed once for each section or schedule. The following special variables can be used in section or schedule blocks:<\/p>\n

Section Block Template Elements<\/h3>\n\n\n\n\n\n\n\n
Element<\/strong><\/td>\nDescription<\/strong><\/td>\nSample Output<\/strong><\/td>\n<\/tr>\n
section_name<\/strong><\/td>\nLetter\/number section code<\/td>\n“A1”<\/td>\n<\/tr>\n
section_title_abbrev<\/strong><\/td>\nAbbreviated section title<\/td>\n“JO INTERNSHIP”<\/td>\n<\/tr>\n
section_instructor_uc<\/strong><\/td>\nLast name of instructor, in caps<\/td>\n“KLARFELD”<\/td>\n<\/tr>\n
section_instructor<\/strong><\/td>\nLast name of instructor<\/td>\n“Klarfeld”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Schedule Block Template Elements<\/h3>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Element<\/strong><\/td>\nDescription<\/strong><\/td>\nSample Output<\/strong><\/td>\n<\/tr>\n
schedule_class_type<\/strong><\/td>\nType of class, written fully<\/td>\n“Independent”<\/td>\n<\/tr>\n
schedule_class_type_abbrev<\/strong><\/td>\nType of class, abbreviated<\/td>\n“IND”<\/td>\n<\/tr>\n
schedule_building<\/strong><\/td>\nThree letter building code<\/td>\n“SAR”<\/td>\n<\/tr>\n
schedule_room<\/strong><\/td>\nRoom number<\/td>\n“218”<\/td>\n<\/tr>\n
schedule_days<\/strong><\/td>\nDays of section, as single letters<\/td>\n“MW”<\/td>\n<\/tr>\n
schedule_days_1<\/strong><\/td>\nDays of section, as single letters separated by a comma<\/td>\n“M, W”<\/td>\n<\/tr>\n
schedule_days_3<\/strong><\/td>\nDays of section, as three letters<\/td>\n“Mon, Wed”<\/td>\n<\/tr>\n
schedule_days_full<\/strong><\/td>\nDays of section, written fully<\/td>\n“Monday, Wednesday”<\/td>\n<\/tr>\n
schedule_time_start<\/strong><\/td>\nStart time<\/td>\n“6:00 PM”<\/td>\n<\/tr>\n
schedule_time_end<\/strong><\/td>\nEnd time<\/td>\n“7:30 PM”<\/td>\n<\/tr>\n
schedule_time_start_24<\/strong><\/td>\nStart time written in military time<\/td>\n“18:00”<\/td>\n<\/tr>\n
schedule_time_end_24<\/strong><\/td>\nEnd time written in military time<\/td>\n“19:30”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Below is a sample course description template that uses both the “section_block” and “schedule_block” tags. For readability’s sake, this example omits HTML markup; in a production environment, you would probably style the fields below to make them appear like you want them to.<\/p>\n

{!college!} {!department!} {!course_num!} – {!title!}
\n—————————————————–
\n<!– BEGIN section_block –>
\nsection: {!section_name!}
\ninstructor: {!section_instructor!}
\nmeets:
\n<!– BEGIN schedule_block –>
\n{!schedule_days!} {!schedule_time_start!}-{!schedule_time_end!}
\n({!schedule_building!} {!schedule_room!})
\n<!– END schedule_block –>
\n<!– END section_block –><\/p>\n

This template will be parsed to produce something like:<\/p>\n

COM FT 310 – Screenwriting I
\n—————————————————–<\/p>\n

section: A1
\ninstructor: Tba
\nmeets:
\nM 2:00 PM-4:30 PM
\n(SAR 218)
\nF 1:30 PM-3:00 PM
\n(COM 213)<\/p>\n

section: B1
\ninstructor: Tba
\nmeets:
\nW 2:00 PM-4:30 PM
\n(CAS B18A)
\nF 1:30 PM-3:00 PM
\n(GCB 203)<\/p>\n

section: C1
\ninstructor: Thompson
\nmeets:
\nF 10:00 AM-12:30 PM
\n(KCB 107)
\nF 1:30 PM-3:00 PM
\n(KCB 103)<\/p>\n

Note that the section and schedule blocks are repeated in the output, despite appearing in the template only once.<\/p>\n","protected":false},"excerpt":{"rendered":"

Section and schedule information can be included for scheduled courses by including the attribute show_sections=”Y” specified in your course container’s bub_course or bub_base tag. You can indicate whether to include or exclude unscheduled courses by using the show_unscheduled_courses attribute (see the course container section for details). If you do include section and schedule data, you…<\/p>\n","protected":false},"author":3321,"featured_media":0,"parent":37730,"menu_order":6,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/37863"}],"collection":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/users\/3321"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/comments?post=37863"}],"version-history":[{"count":7,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/37863\/revisions"}],"predecessor-version":[{"id":52734,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/37863\/revisions\/52734"}],"up":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/37730"}],"wp:attachment":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/media?parent=37863"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}