Instructors can now align individual criteria listed in the row of a Rubric to course Goals, providing a more granular level of aligning a specific criterion to course Goals using a Rubric.
Goal managers can create relationships between individual Goals within Goal Sets to demonstrate how Goals from different sets relate to one another. By creating related Goals, an institution can show how learning outcomes for courses relate to program goals or accreditation standards. After the relationships are established, the View Related Goals report can be generated to show all the relationships that exist within the system for a selected set of Goals.
A source of frustration for students, instructors, and test proctors is the inability to confirm whether students began a Blackboard Test or ran into problems during a Test. Teachers and proctors had no way to verify student activity or lack of activity during a Test. Students had no way to prove that they did begin a Test and when. If students reported problems occurring during a Test, they were either given the benefit of the doubt and the test was reset, or they were penalized for circumstances beyond their control.
Service Pack 13 addresses this issue by providing detailed information on student Test attempt interactions. Instructors and other users, who are granted permission, can view the Access Log for a Test from the Attempts page of the Test. The access log shows a detailed list of every interaction that students engage in when taking a Test. If a student claims to have started a Test, the log will show the time the Test was started. If a network or Internet disruption occurred during the Test, for example, the log would show an unusual gap in the time.
A new privilege for System Roles has been added to allow a System Administrator to override a setting in a lower level Node that was inherited from a higher level Node. This allows the System Administrator to set the Tool Availability to Always Off for all of the Nodes, and override that setting for one or more individual Nodes that would not have been editable in the current implementation.
When System Administrators install or update a Building Block using Software Updates, they are informed of any dependencies that Building Block has on other Building Blocks. If the installation is approved, the Building Block dependencies are also updated. When all the installations are complete, the System Administrator receives an email with details of the operation. If there is an error, the email message will contain sufficient information to triage or to provide to Blackboard Support for resolution.
Manually installing Building Blocks using the Administrator Panel respects the dependencies of Building Blocks. When a Building Block with dependencies is manually installed, and those dependencies are available through Software Updates, the dependencies are automatically installed by Software Updates as part of the manual install process.
When Blackboard Learn is processing large sets of data such as copying a course; the process takes place in the background so that users do not have to wait until it is completed before going on to another task. It is difficult to know when the process is complete without some type of indicator. The Progress Tracker provides a visible indicator for processes that take place in the background. This visual indicator can appear in different forms, but the intention is to let users know a process is taking place and when it is complete.
The Cloud Connector establishes a link between a Blackboard Learn instance and the cloud. Blackboard has established a separate parallel Staging instance of the Blackboard cloud services. The staging instance creates a separate testing cloud instance so that test data can be entered into the Blackboard cloud and remains separate from production data.
The first time a cloud connection is established to a server, select Test, Development, or Stage to identify the Blackboard Learn server and connect to the new Staging instance of the cloud. If the Blackboard Learn server can call back to Blackboard cloud services, the connection status will display a success message. At this point the Blackboard Learn server is connected to the Staging instance of Blackboard cloud services. To connect to the Production instance of Blackboard cloud services, the System Administrator needs to move their connection to Production by clicking Move to Production.
To complete the move, enter an External URL and Display Name for the Blackboard Learn server in production. Moving the Staging server to the Production server deletes all of the staging data associated with that Blackboard Learn server in the staging instance of Blackboard cloud services. If the external URL is not valid, the move will fail and the Blackboard Learn server will remain as a Staging instance.