[CLOSED] No access to complex release conditions in Blackboard Ultra

(21/11/24)This issue was addressed in a patch from Blackboard. Full functionality has now been returned to Blackboard Ultra’s Release Conditions.

Access to complex, multiple-rule release conditions in Blackboard Ultra courses is currently unavailable. This is preventing the establishment of new rules and the review and verification of existing rules. We understand the potential impact of this and the concern it may cause.

Alongside Blackboard, we’re urgently investigating the cause of this issue and seeking a resolution as soon as possible. We will provide updates here when they are available.

If you have any concerns or questions about this, please contact digital-education@bristol.ac.uk

 

 

[Closed] Slow document conversion when submitting to Blackboard Ultra

(Update: 21.11.24: This issue has now been addressed by Blackboard and normal service has resumed)

We have been made aware that the document preview interface for submitting a Blackboard Ultra assignment is currently taking longer than usual to load. Please note that this does not affect students’ ability to submit their files.

If, when uploading a file, a student encounters delays in the document preview loading, or the message “The conversion needs more time. Please try again later,” they can proceed with the submission without waiting for the conversion to complete, provided they are confident they have attached the correct file.

After submission, they should return to the submission point and click the download icon to verify that their work has been uploaded correctly. If everything appears as intended, they can consider their work submitted and record their receipt number as usual.

This issue is currently affecting multiple universities. We have reported it to Blackboard and will provide updates once it has been resolved.

If you have any questions or concerns, please email digital-education@bristol.ac.uk.

Student Developers to work on Ultra wave 1

The DEO has recently recruited and trained a team of Student Developers (SDs) to support the move to Blackboard Ultra. Our SDs are an important part of how we will support this move.  

The overall objectives for the SDs are to: 

  1. offer hands-on help to staff moving to Ultra 
  2. review courses, content and workflows to identify ways to improve the student experience 
  3. identify and develop Ultra support materials for students 
  4. realise opportunities to strengthen their digital skills.  

In wave 1, SDs will be working with faculties and the project to establish how best to use SDs in the major move to Ultra planned for academic year 25/26.  

Allocation and management 

Each of the six old faculties will be allocated two dedicated student developers, with two back-up developers who can be drawn on if demand or skills require it.

Each student developer can work up to 15 hours per week. 

For wave 1, the project will trial two management approaches for SDs: 

  1. Allocation: in Health Sciences and Arts, dedicated student developers will be allocated to embedded digital education leads, who will determine which units the students work with. 
  1. Central management: In Engineering, Life Sciences, Social Sciences, and Science, student developers will be managed by the Ultra project.

Allocation of back-up student developers will be managed by the project. 

Key activities of Student Developers 

SDs will be able to: 

  • Move content such as documents, videos, MCQs 
  • Resolve common issues when moving content 
  • Run Ally reports and make changes to materials to make them more accessible 
  • Review Ultra courses from a student’s eye view for good design, usability and accessibility. 

They will also be asked to: 

  • Keep a log of actions they have been asked to perform to enable quality assurance and create a change management audit trail in the event of any issues 
  • Provide peer support for other SDs to offer advice and guidance on good approaches. 

Roles and responsibilities 

The Ultra project will:

  • Recruit SDs, collate activity and process payslips 
  • Provide training and support, including back-up support from other SDs, the project and the DEO  
  • Troubleshoot any issues collaboratively with faculty, school and unit staff 
  • Manage allocation in faculties that are not self-managing. 

Faculties and schools will:

  • Identify units and areas for SD activity 
  • Ensure tasks fit within the SD role 
  • Flag tasks which do not fit in the SD role to the project 
  • Quality assure all actions of the SD to ensure that the work is completed to a good standard before it is released to students 
  • Report issues to the project team. 

More information 

The project will take steps to ensure that SDs are providing good, useful support but it is important that faculty staff check work undertaken by the SDs as part of their review/refresh of unit and programme courses before they are released to students. 

It’s anticipated that faculty staff will engage in a dialogue with their SDs, to fine-tune the support offered. Any major suggestions, issues or concerns should be raised with the project in the first instance and not with the SD. 

DEO faculty liaison roles to support the move to Ultra

To support faculties moving to Blackboard Ultra for the 2024/25 Academic Year, the DEO and the Ultra project are establishing dedicated faculty liaison roles. The aim of these roles is to be a named contact in the DEO for Ultra wave 1 participants – someone who can direct staff to the support they need and ensure the project better understands faculty and school needs and any blockers or barriers. The role will advise on customisation of central training and guidance to better fit with local needs, encourage the dissemination of good practice, and provide guidance to Ultra student developers. 

Faculties involved in wave 1 will be receiving more information on their faculty liaison shortly. For all general project enquiries, please contact blackboard-ultra@bristol.ac.uk.