Last updated: September 6th, 2022.
Before we start with the whole document and you start developing your own application, We have noticed that sometimes the terminology can end up in a confusion, that is why we want to make sure that all the terminology is clean and ready for everyone to start developing using our API.
Please keep in mind that this only applies to Class Collaborate Ultra
Need credentials for a sandbox? We got you!
If you need credentials in order to start developing (whether you are a client or a partner), please write us an email at email@example.com letting us know the following:
- Institution or company you are writing us from
- Introduce yourself! (Name, what do you do at the company)
- Let us know what you need!
We will respond as soon as possible with the credentials!
Note: Please keep in mind that all credentials are reviewed first internally before being provided.
1. This is a test environment, hence, it is completely empty (it is not possible to move information from one environment to another)
2. The environment has specific limitations (due to its nature, however, Collaborate in production has none of them)
3. There is no GUI available in this environment.
About key, secret and URL!
Please keep in mind that the credentials that you use for the scheduler are not the same to access using REST, they are completely different, when logging in to the scheduler you use username + password on a specific URL, on REST we use a KEY + SECRET on a specific URL.
If you need your key + secret + URL from your instance to start developing, please create a ticket in order to receive this information.
This document is based on a presentation that we did to a client and we noticed that they vastly improved their questions and input on their own applications!
We will group these concepts into 3 parts:
– Optional attributes or characteristics
Here you will find a couple of terms that may be kind of confusing, but we will try to explain them as easy as possible:
We use Sessions, this is defined correctly on this post, however, there is another term, and this is Instances.
A Session can have multiple instances, a Session can exist without an instance, but there are no instances without a session, meaning Instances depend on Sessions to exist.
The way Sessions and Instances co-exist and depend in one another, is that, When you create a Session, but no one has ever joined to it, there are no instances. Let’s say for example that you are an instructor on the Python 101 course, and you have 3 different groups:
- Morning group – has class from 8:00 am to 9:00 am
- Afternoon group – has class from 1:00 pm to 2:00 pm
- Night group – has class from 6:00 pm to 7:00 pm
You have your course on learn with course id CS-PYTHON101 and you use the same course for all students, you also have a course room that is already set up on your course and ready to use.
From the course room, you can create new Sessions, this instructor decided to create only one session, open session for all the classes for all 3 groups. When the first student (or the instructor) joins the session at 8:00 am (or before if early entry is enabled ) an instance of the session is created! Then, when the last student leaves, there is a 5-minute “grace” period for the instance to be finished, then the instance is completed and stored.
For this part, we have 3 concepts that need to be reviewed:
This happens ONLY when you use the integrated enrollment tool within Blackboard Ultra, when using a course room, all the students within the course are automatically enrolled.
This happens ONLY when you allow Guest Access, meaning that users will see a window asking for their name when using a guest link.
When an Enrolled user or an User join a Collaborate session, they both become attendees.
Optional attributes or characteristics
There are several attributes or characteristics (OAC) that apply for the Who and the Where.
When using collaborate, you may want to organize your Sessions per functional area if you are a company or per course if you are an institution.
This is possible by using Context!
Contexts allow you to group your sessions by a specific criteria, this is completely optional and when using Collaborate integrated with Learn it is automatically populated with the course id data.
The recordings are as easy to create by clicking a simple button when attending a collaborate session (instance), but how are they organized?
Well, it is quite simple, a Session can have multiple Instances, an instance can have multiple recordings!
Why? well, let’s say you click on the record button on your current instance, but by mistake you clicked the stop recording button, well, the instance recording will be saved and if you hit the record button again, the new recording will be correlated to the current instance + session. Meaning that you will have two recordings on the same instance!
Recording is completely optional!
When a user is enrolled in a session* it is possible to set a parameter for the user in order to link the user to an external source, for example, learn uses user_id, it is possible to send from learn (or grab from there) the user id and store it on the user enrollment for future queries.
*This applies only for REST API / LTI only, not available on the GUI.
These are some video resources that we have been working on to explain how REST API works:
Spanish (Some of them)
Rest API in Collaborate is quite easy to use once all these concepts are clear!
If you have further questions, please do not hesitate and contact us!