diff --git a/source/_images/Educators_subsection_settings_basic.png b/source/_images/Educators_subsection_settings_basic.png index 5815ffa0c..2c2b3ded0 100644 Binary files a/source/_images/Educators_subsection_settings_basic.png and b/source/_images/Educators_subsection_settings_basic.png differ diff --git a/source/_images/educator_concepts/section_release_date.png b/source/_images/educator_concepts/section_release_date.png new file mode 100644 index 000000000..ccc1f0ba4 Binary files /dev/null and b/source/_images/educator_concepts/section_release_date.png differ diff --git a/source/_images/educator_concepts/section_three_dot_menu_configure.png b/source/_images/educator_concepts/section_three_dot_menu_configure.png new file mode 100644 index 000000000..4fe2faf15 Binary files /dev/null and b/source/_images/educator_concepts/section_three_dot_menu_configure.png differ diff --git a/source/_images/educator_concepts/unit_hide_from_learners.png b/source/_images/educator_concepts/unit_hide_from_learners.png new file mode 100644 index 000000000..8549e7f1d Binary files /dev/null and b/source/_images/educator_concepts/unit_hide_from_learners.png differ diff --git a/source/_images/educator_concepts/unit_three_dot_menu_configure.png b/source/_images/educator_concepts/unit_three_dot_menu_configure.png new file mode 100644 index 000000000..9a97df226 Binary files /dev/null and b/source/_images/educator_concepts/unit_three_dot_menu_configure.png differ diff --git a/source/_images/educator_how_tos/studio_grading_configuration.png b/source/_images/educator_how_tos/studio_grading_configuration.png new file mode 100644 index 000000000..3249be7af Binary files /dev/null and b/source/_images/educator_how_tos/studio_grading_configuration.png differ diff --git a/source/_images/educator_how_tos/studio_visibility_configuration.png b/source/_images/educator_how_tos/studio_visibility_configuration.png new file mode 100644 index 000000000..6ff5004cc Binary files /dev/null and b/source/_images/educator_how_tos/studio_visibility_configuration.png differ diff --git a/source/_images/educator_how_tos/subsection_three_dot_menu_configure.png b/source/_images/educator_how_tos/subsection_three_dot_menu_configure.png new file mode 100644 index 000000000..ee258e9ca Binary files /dev/null and b/source/_images/educator_how_tos/subsection_three_dot_menu_configure.png differ diff --git a/source/_images/educator_references/Units_LMS.png b/source/_images/educator_references/Units_LMS.png index 6d4f53ccd..2e83348fe 100644 Binary files a/source/_images/educator_references/Units_LMS.png and b/source/_images/educator_references/Units_LMS.png differ diff --git a/source/_images/educator_references/progress_page_assessment_before_due.png b/source/_images/educator_references/progress_page_assessment_before_due.png new file mode 100644 index 000000000..df87cc361 Binary files /dev/null and b/source/_images/educator_references/progress_page_assessment_before_due.png differ diff --git a/source/_images/educator_references/studio_settings_grading.png b/source/_images/educator_references/studio_settings_grading.png new file mode 100644 index 000000000..d32a77fc8 Binary files /dev/null and b/source/_images/educator_references/studio_settings_grading.png differ diff --git a/source/_images/educator_references/unit-page.png b/source/_images/educator_references/unit-page.png index 51edaaccb..d89f6ad1c 100644 Binary files a/source/_images/educator_references/unit-page.png and b/source/_images/educator_references/unit-page.png differ diff --git a/source/developers/references/aspects_home.rst b/source/developers/references/aspects_home.rst index 5b0a49915..5583320f6 100644 --- a/source/developers/references/aspects_home.rst +++ b/source/developers/references/aspects_home.rst @@ -1,3 +1,5 @@ +.. _Aspects Home: + #################################################### Aspects: Learner analytics for the Open edX Platform #################################################### diff --git a/source/educators/concepts/open_edx_platform/about_course_sections.rst b/source/educators/concepts/open_edx_platform/about_course_sections.rst index 38c36b67d..0d1b29105 100644 --- a/source/educators/concepts/open_edx_platform/about_course_sections.rst +++ b/source/educators/concepts/open_edx_platform/about_course_sections.rst @@ -6,8 +6,6 @@ About Course Sections .. tags:: educator, concept -To develop sections in your course, you must first understand the following topics. - .. contents:: :local: :depth: 2 @@ -16,14 +14,15 @@ To develop sections in your course, you must first understand the following topi What Is a Section? **************************** -A section is the topmost category in your course. A section can represent a -time period in your course, a chapter, or another organizing principle. A section contains one or more subsections. +A section is the topmost category in a course. A section can represent a time +period in a course, a chapter, or another organizing principle. A section +contains one or more :ref:`subsections `. ******************************** Viewing Sections in the Outline ******************************** -For more information see :ref:`About the Course Outline` +For more information see :ref:`About the Course Outline`. .. _Sections and Visibility to Learners: @@ -42,13 +41,40 @@ if: * The unit is not hidden from learners. ************************************************ -Release Statuses of Sections +Setting the Release Date for Sections ************************************************ -As an course author, you control the release status of sections. For the -content of a section to be visible to learners, the section must be released. -See the following topics for more information about the possible release -statuses of sections. +For the content of a section to be visible to learners, the section must be +released. To set the release status for sections, follow these steps. + +#. From the three-dot menu at the section level, choose **Configure**. + + .. image:: /_images/educator_concepts/section_three_dot_menu_configure.png + :width: 600 + +#. On the **Basic** tab, locate the **Release date and time** section. + + .. image:: /_images/educator_concepts/section_release_date.png + :width: 600 + +#. For **Release Date** and **Release Time in UTC**, enter or select a due date and + time for problems in this section. + + .. note:: The time that you set is in Coordinated Universal Time (UTC). You + might want to verify that you have specified the time that you intend by + using a time zone converter such as `Time and Date Time Zone Converter`_. + + Learners who have specified a time zone in their account settings see + course dates and times converted to their specified time zone. Learners + who have not specified a time zone in their account settings see course + dates and times on their dashboards, in the body of the course, and on + their **Progress** pages in the time zone that their browsers specify. + Learners see other course dates and times in UTC. + + +************************************************ +Understanding Section Statuses +************************************************ .. contents:: :local: @@ -58,16 +84,16 @@ statuses of sections. Unscheduled ======================== -If you do not change the :ref:`course start date` -default value, ``1/1/2030 00:00:00 UTC``, when you create a new section, its +If the :ref:`course start date` is unchanged from its +default value, ``1/1/2030 00:00:00 UTC``, when a new section is created, its release date will appear as ``Unscheduled``. When the section release date is unscheduled, learners cannot see any content in that section, regardless of the publishing status of that content. -If you have modified the course start date, when you create a new section, the +If the course start date has been modified, when a new section is created, the default release date is the course start date. -To make the content available to learners, you must schedule the release date. +To make the content available to learners, the release date must be scheduled. ========== Scheduled @@ -91,10 +117,10 @@ published. Released with Unpublished Changes ================================== -If you change a unit in a released section but do not publish the changes, +If a unit in a released section is changed but the changes aren't published, learners see the last published version of the modified unit. -You must publish the unit for learners to see the updates. +The unit must published for learners to see the updates. =========================== Staff Only Content @@ -136,5 +162,5 @@ regardless of the release date of the section or subsection. +--------------+-------------------------------+----------------+--------------------------------+ | Review Date | Working Group Reviewer | Release |Test situation | +--------------+-------------------------------+----------------+--------------------------------+ -| | | | | +| 2025-11-16 | sarina | Ulmo | Pass | +--------------+-------------------------------+----------------+--------------------------------+ diff --git a/source/educators/concepts/open_edx_platform/about_course_subsections.rst b/source/educators/concepts/open_edx_platform/about_course_subsections.rst index 3fdc86fff..1f7569a86 100644 --- a/source/educators/concepts/open_edx_platform/about_course_subsections.rst +++ b/source/educators/concepts/open_edx_platform/about_course_subsections.rst @@ -6,9 +6,6 @@ About Course Subsections .. tags:: educator, concept -To develop subsections in your course, you must first understand the -following topics. - .. contents:: :local: :depth: 2 @@ -17,23 +14,23 @@ following topics. What Is a Subsection? **************************** -Sections are divided into subsections, which in turn contain one or more units. -A subsection may represent a topic in your course, or another organizing -principle. Subsections are sometimes called "lessons" or they might represent a -week's worth of material. +:ref:`Sections ` are divided into subsections, which in +turn contain one or more :ref:`units `. A subsection may +represent a topic in a course, or another organizing principle. Subsections are +sometimes called "lessons" or they might represent a week's worth of material. *********************************** Viewing Subsections in the Outline *********************************** -For more information see :ref:`About the Course Outline` +For more information see :ref:`About the Course Outline`. ************************************************ Subsections and Visibility to Learners ************************************************ -Learners cannot see any content in a subsection until you schedule a release -date, and that release date has passed. +Learners cannot see any content in a subsection until a release date is +scheduled, and that release date has passed. If a subsection's release date has passed, learners can see content in the subsection if the following conditions are met. @@ -43,16 +40,16 @@ subsection if the following conditions are met. * The subsection or the units are not hidden from learners. To control whether learners have access to the subsection and its units after -a subsection's release date, you can apply various visibility settings. +a subsection's release date, various visibility settings can be applied. By default, the subsection and its units are available to learners, except for -any units that you have explicitly hidden from learners. +any units that have been explicitly hidden from learners. -You can also choose to entirely hide a subsection so that the subsection and -its units are not visible to learners at all in the course navigation, or you -can hide the contents of a subsection after the subsection due date has passed. -For more information about subsection visibility settings, see :ref:`Hide a -Subsection from Students`. +A subsection can be entirely hidden so that the subsection and its units are not +visible to learners at all in the course navigation. Additionally, the contents +of a subsection can be hidden after the subsection due date has passed. For more +information about subsection visibility settings, see :ref:`Hide a Subsection +from Students`. .. note:: @@ -72,9 +69,8 @@ Subsection from Students`. Release Statuses of Subsections ************************************************ -As a course author, you control the release status of subsections. For the -content of a subsection to be visible to learners, the subsection must be -released. See the following topics for more information about the possible +For the content of a subsection to be visible to learners, the subsection must +be released. See the following topics for more information about the possible release statuses of subsections. .. contents:: @@ -85,7 +81,7 @@ release statuses of subsections. Scheduled with the Section ========================== -When you create a subsection, it is set by default to release on the same date +When a subsection is created, it is set by default to release on the same date and time as the section it is in. Therefore, published content in the subsection is visible to learners at the date and time the section is released. @@ -93,7 +89,7 @@ When a subsection is in the "Scheduled with Section" state, and the section is scheduled, the subsection is visible in the outline with a vertical green bar next to the subsection's display name. -You can change the release date for a subsection to be different from the +The release date for a subsection can be changed to be different from the section it is in. For more information, see :ref:`Set a Subsection Release Date`. @@ -101,7 +97,7 @@ Date`. Unscheduled ======================== -If the parent section is unscheduled, when you create a new subsection it +If the parent section is unscheduled, when a new subsection is created, it will also be unscheduled. Regardless of the publishing status of units within the subsection, no content @@ -110,14 +106,14 @@ in an unscheduled subsection is visible to learners. When a subsection is unscheduled, the subsection is visible in the outline with a vertical gray bar next to the subsection's display name. -Content in the subsection is not visible to learners until you set a release -date and the date passes. +Content in the subsection is not visible to learners until a release date is set +*and* the date passes. =================================== Scheduled Later than the Section =================================== -You can set a subsection to release on a date after the section releases. +A subsection can be set to release on a date after the section releases. Content in a subsection that is scheduled for release on a future date is not visible to learners, even if some or all of the units in the subsection are @@ -133,28 +129,28 @@ The scheduled date must pass for the subsection to be visible to learners. Scheduled with Unpublished Changes ================================== -You can make changes to a published unit before its parent subsection +Changes to a published unit can be made before its parent subsection is released. In this situation, when the release date for the subsection passes, the last published version of units within the subsection are made visible to learners. -The changes in units are not visible to learners until you publish them. +The changes in units are not visible to learners until they are published. When a subsection is scheduled but has unpublished changes, the subsection is visible in the outline with a vertical yellow bar next to the subsection's -display name. When you expand the subsection, the unit that has unpublished +display name. When the subsection is expanded, the unit that has unpublished changes is visible. ================================== Released with Unpublished Changes ================================== -If you modify a unit within a released subsection, those modifications are not -visible to students until you publish them. +If a unit is modified within a released subsection, those modifications are not +visible to students until they are published. When a subsection is scheduled but has unpublished changes, the subsection is visible in the outline with a vertical yellow bar next to the subsection's -display name. When you expand the subsection, the unit that has unpublished +display name. When the the subsection is expanded, the unit that has unpublished changes is visible. =========================== @@ -179,6 +175,7 @@ When a subsection contains a unit that has staff-only content, the subsection is visible in the outline with a vertical black bar next to the subsection's display name. +See :ref:`Staff Only Unit` for more detail on unit-level visibility. .. seealso:: @@ -211,5 +208,5 @@ display name. +--------------+-------------------------------+----------------+--------------------------------+ | Review Date | Working Group Reviewer | Release |Test situation | +--------------+-------------------------------+----------------+--------------------------------+ -| | | | | +| 2025-11-16 | sarina | Ulmo | Pass | +--------------+-------------------------------+----------------+--------------------------------+ diff --git a/source/educators/concepts/open_edx_platform/about_course_units.rst b/source/educators/concepts/open_edx_platform/about_course_units.rst index a593f65f4..d3e9630ad 100644 --- a/source/educators/concepts/open_edx_platform/about_course_units.rst +++ b/source/educators/concepts/open_edx_platform/about_course_units.rst @@ -6,15 +6,13 @@ About Course Units .. tags:: educator, concept -To work with units in the course outline and develop your course, you need to -understand the following concepts and complete the following tasks. +One or more units make up a course :ref:`subsection `. +Units are comprised of :ref:`course components`. .. contents:: :depth: 1 :local: -You add content to units with :ref:`course components`. - .. _What is a Unit: **************************** @@ -29,49 +27,48 @@ such as text with :ref:`HTML` markup, :ref:`problems`, or a :ref:`video`. -*********************************** -Viewing Subsections in the Outline -*********************************** - -For more information see :ref:`About the Course Outline` - **************************** Viewing the Unit Page **************************** -In Studio, when you select a unit name in the outline, the **Unit** page opens. +In Studio, when a unit name is selected in the outline, the **Unit** page opens. -The following example shows a unit page in Studio with two components, with -circles and text to show different areas and controls in the page. +The following example shows a unit page in Studio with one component, with +boxes and text to show different areas and controls in the page. .. image:: /_images/educator_references/unit-page.png - :alt: The unit page with numbered indicators. + :alt: The Studio unit page with numbered indicators. :width: 600 -#. A component in the unit. -#. Options for testing the unit. +#. A unit navigation bar that shows where in the subsection this unit is + located, and provides easy navigation options to nearby unit pages. +#. Options for testing the unit (View Live and Preview), and button to view + in-context analytics (if :ref:`Aspects Home` is enabled). +#. Navigation tools to quickly get to other units in the subsection. +#. The **+ New unit** button is a way to add new units to a subsection through + the unit navigation bar. #. Status panel for the unit. -#. A unit navigation bar that shows where in the subsection this unit is located, and provides easy navigation options to nearby unit pages. -#. A way to add new units to a subsection through the unit navigation bar. -#. Navigation tools to quickly get to other sections or subsections. +#. A component in the unit. +#. The "New Component" section at the bottom of the page, allowing authors to + add additional components to the unit. **************************** Viewing Units as a Learner **************************** -To a learner using the learning management system -(LMS), each unit in the -subsection is represented by an icon in the unit navigation bar at the top of -the **Course** page. The current unit is indicated with bold underlining in the -unit navigation bar. The components in the current unit appear below the unit navigation bar. +To a learner using the learning management system (LMS), each unit in the +subsection is listed in the collapsable navigation bar on the left side of the +**Course** page. The current unit is indicated with slight highlighting in the +sidebar. The components in the current unit appear to the right of the sidebar +navigation. The following image shows a subsection in the LMS that contains several units. .. image:: /_images/educator_references/Units_LMS.png - :alt: A unit in the LMS, with all of the unit icons in the unit navigation bar + :alt: A unit in the LMS, with all of the unit icons in the unit navigation sidebar indicated. Green check marks are visible for some units. - :width: 500 + :width: 750 A green check mark next to a unit icon indicates that a learner has completed the unit. A learner has completed the unit if the learner has completed all the @@ -81,6 +78,26 @@ following actions. * Submitted answers for all of the problems. * Viewed all HTML content for at least five seconds. +.. _Staff Only Unit: + +**************************** +Setting Units to Staff Only +**************************** + +To set a unit to be visible to only staff, follow these steps. + +#. From the three-dot menu at the unit level, choose **Configure**. + + .. image:: /_images/educator_concepts/unit_three_dot_menu_configure.png + :width: 600 + +#. Locate the **Unit visibility** section and select **Hide from learners**. + + .. image:: /_images/educator_concepts/unit_hide_from_learners.png + :width: 600 + +#. Select **Save**. + .. seealso:: :ref:`Manage Course Units` (how-to) @@ -126,5 +143,5 @@ following actions. +--------------+-------------------------------+----------------+--------------------------------+ | Review Date | Working Group Reviewer | Release |Test situation | +--------------+-------------------------------+----------------+--------------------------------+ -| | | | | +| 2025-11-16 | sarina | Ulmo | Pass | +--------------+-------------------------------+----------------+--------------------------------+ diff --git a/source/educators/how-tos/course_development/manage_subsections.rst b/source/educators/how-tos/course_development/manage_subsections.rst index c8159c301..8b3b40aca 100644 --- a/source/educators/how-tos/course_development/manage_subsections.rst +++ b/source/educators/how-tos/course_development/manage_subsections.rst @@ -262,7 +262,9 @@ To delete a subsection, follow these steps. +--------------+-------------------------------+----------------+---------------------------------------------------------------+ | Review Date | Working Group Reviewer | Release |Test situation | +--------------+-------------------------------+----------------+---------------------------------------------------------------+ -| 03/19/2025 | John (Curricu.me) | Sumac |Pass | +| 2025-11-16 | sarina | Ulmo | Pass | ++--------------+-------------------------------+----------------+---------------------------------------------------------------+ +| 03/19/2025 | John (Curricu.me) | Sumac |Pass | +--------------+-------------------------------+----------------+---------------------------------------------------------------+ | 03/05/2025 | Leira (Curricu.me) | Sumac |Fail (https://github.com/openedx/docs.openedx.org/issues/863 | +--------------+-------------------------------+----------------+---------------------------------------------------------------+ diff --git a/source/educators/how-tos/course_development/set_subsection_problem_date.rst b/source/educators/how-tos/course_development/set_subsection_problem_date.rst index e9bf1af08..47d4cc4e7 100644 --- a/source/educators/how-tos/course_development/set_subsection_problem_date.rst +++ b/source/educators/how-tos/course_development/set_subsection_problem_date.rst @@ -6,12 +6,13 @@ Set the Assignment Type and Due Date for a Subsection .. tags:: educator, how-to -You set the assignment type for problems at the subsection level. +The assignment type for problems is set at the subsection level. -When you set the assignment type for a subsection, all problems in the -subsection are graded and weighted as a single type. For example, if you -designate the assignment type for a subsection as **Homework**, then all -problem types in that subsection are graded as homework. +When the assignment type for a subsection is set, all problems in the subsection +are graded and weighted as a single type. For example, if the assignment type +for a subsection is designated as **Homework**, then all problem types in that +subsection are graded as homework. See :ref:`Gradebook Assignment Types` for +more on how to create custom assignment types. .. note:: Unlike other problem types, by default, ORA assignments are not governed by the @@ -21,13 +22,18 @@ problem types in that subsection are graded as homework. To set the assignment type and due date for a subsection, follow these steps. -#. Select the **Configure** icon in the subsection box. +#. From the three-dot menu at the subsection level, choose **Configure**. - The subsection settings dialog box opens. + .. image:: /_images/educator_how_tos/subsection_three_dot_menu_configure.png + :width: 600 #. On the **Basic** tab, locate the **Grading** section. + #. In the **Grade as** list, select the assignment type for this subsection. + .. image:: /_images/educator_how_tos/studio_grading_configuration.png + :width: 600 + #. For **Due Date** and **Due Time in UTC**, enter or select a due date and time for problems in this subsection. @@ -61,48 +67,36 @@ you administer a survey. You can do this by using the **Assessment Results Visibility** setting. .. note:: - The **Assessment Results Visibility** setting is a subsection setting. You - cannot change the visibility of individual problems. The **Assessment Results + + The **Assessment Results Visibility** setting is a subsection setting. The + visibility of individual problems cannot be changed. The **Assessment Results Visibility** subsection setting overrides the **Show Answer** setting for individual problems. Answers to problems are not visible when results are hidden. -The **Assessment Results Visibility** setting can be used with the following -common problem types. - -* :ref:`Dropdown` -* :ref:`Multi select` -* :ref:`About Numerical Input` -* :ref:`Single Select` -* :ref:`Text Input` - -The **Assessment Results Visibility** setting can be used with the following -advanced problem types. - -* :ref:`Annotation` -* :ref:`Circuit Schematic Builder` -* :ref:`Custom JavaScript Display and Grading` -* :ref:`Custom Python-Evaluated Input` -* :ref:`Image Mapped Input` -* :ref:`Math Expression Input` -* :ref:`Problem Written in LaTeX` -* :ref:`Problem with Adaptive Hint` - To change the results visibility for your subsection, follow these steps. -#. Select the **Configure** icon in the subsection box. +#. From the three-dot menu at the subsection level, choose **Configure**. - The **Settings** dialog box opens. + .. image:: /_images/educator_how_tos/subsection_three_dot_menu_configure.png + :width: 600 #. Select the **Visibility** tab, and locate **Assessment Results Visibility**. + .. image:: /_images/educator_how_tos/studio_visibility_configuration.png + :width: 600 + #. Select one of the available options. - * **Always show results**: This is the default setting. Problem results and + * **Always show assessment results**: This is the default setting. Problem results and subsection scores are visible immediately when learners and staff submit answers. - * **Never show results**: Subsection scores are visible, but problem results - are never visible to learners or to course staff. - * **Show results when subsection is past due**: For learners, results are + + * **Never show assessment results**: Subsection scores are visible, but + problem results are never visible to learners or to course staff. Problem + scores from this subsection are not counted toward the overall course + score. + + * **Show assessment results when subsection is past due**: For learners, results are not visible until the subsection due date (for instructor-paced courses) or the course end date (for self-paced courses) has passed. For course staff, results are always visible unless the staff member is @@ -113,8 +107,33 @@ To change the results visibility for your subsection, follow these steps. If the subsection does not have a due date, or the course does not have an end date, results are always visible. + * **Never show individual assessment results, but show overall assessment + results after due date**: Learners do not see question-level correctness or + scores before *or* after the due date. However, once the due date passes, + they can see their overall score for the subsection on the Progress page. + #. Select **Save**. +The **Assessment Results Visibility** setting can be used with the following +common problem types. + +* :ref:`Dropdown` +* :ref:`Multi select` +* :ref:`About Numerical Input` +* :ref:`Single Select` +* :ref:`Text Input` + +The **Assessment Results Visibility** setting can be used with the following +advanced problem types. + +* :ref:`Annotation` +* :ref:`Circuit Schematic Builder` +* :ref:`Custom JavaScript Display and Grading` +* :ref:`Custom Python-Evaluated Input` +* :ref:`Image Mapped Input` +* :ref:`Math Expression Input` +* :ref:`Problem Written in LaTeX` +* :ref:`Problem with Adaptive Hint` .. seealso:: @@ -157,5 +176,7 @@ To change the results visibility for your subsection, follow these steps. +--------------+-------------------------------+----------------+--------------------------------+ | Review Date | Working Group Reviewer | Release |Test situation | +--------------+-------------------------------+----------------+--------------------------------+ +| 2025-11-16 | sarina | Ulmo | Pass | ++--------------+-------------------------------+----------------+--------------------------------+ | 07/08/2025 | Leira (Curricu.me) | Sumac | Pass | +--------------+-------------------------------+----------------+--------------------------------+ diff --git a/source/educators/references/data/progress_page.rst b/source/educators/references/data/progress_page.rst index c3ef02bf9..9b65619a8 100644 --- a/source/educators/references/data/progress_page.rst +++ b/source/educators/references/data/progress_page.rst @@ -33,24 +33,46 @@ The :ref:`Subsection Visibility Setting