Adding Libguides to Blackboard

Options to be Determined

Setting up the LTI requires the choice of name, description and whether custom headers and CSS are to be enabled. If using custom code, be sure the https, (rather than http), protocol is in use. Our header and custom code are enabled, otherwise they would not display inside Blackboard.

You also have to decide how the Library landing page is to be integrated, sometimes, always, or never, as described below. Currently the library is using Option 2.

Option 1: Load a specific guide or course if there's a single exact match on either metadata or friendly URL (guides only), otherwise load the Library LTI Page (which you define in the next section).

If there are multiple guide or course matches, or if there is a single guide and a single course match, the Library LTI Page will load, displaying all matches.
If there is a match on Subject Category (either by metadata or friendly URL), the Library LTI Page's A-Z link and Subject Librarians (if displayed) will be customized to that subject.

Option 2: Always load the Library LTI Page. Part of this page is displaying any related guides / E-Reserves courses, so it's the best of all worlds!

Any / all matching guides will display, matching either metadata or friendly URL.
Any / all matching courses will display, matching on metadata.
The A-Z link and/or Subject Librarians (if displayed) on the page will be customized to a matching subject, matching on either metadata or friendly URL.

Option 3: Load a specific guide or course if there's a single exact match on either metadata or friendly URL (guides only). If there are multiple matches, load the Library LTI page. Otherwise display a guide from your System that you select from a dropdown.


Parameter Matching

Parameter Matching is how you match up courses from your LMS to content in LibGuides. You'll tell the tool which field to look for from your LMS and which Metadata field to match it to in your LibGuides site. (Metadata can be assigned to Guides, E-Reserves, and Subject Categories.)

When the student clicks the link in the navigation, the LMS sends data to the LibApps LTI tool. The tool then searches for the defined parameter in the data and matches that value against the value of the Metadata field defined in your LibGuides system. If it finds a match, it returns that guide / course.

►We are using the three letters lti, small case, as our metadata name, (see illustration above).

This is the name of the Metadata field the tool should look for in your LibGuides site. Since you can have any number of Metadata fields added, you need to tell the tool which one to pay attention to in order to send content to your LMS.

​It really doesn't matter what you choose to call this...the important part is that you use it consistently in your LibGuides system. Everyone must use the same, exact name when adding metadata to guides, e-reserves, or subjects.

Once you've decided on a name, you'll use that to add Metadata values to your LibGuides content in order to match things up with the various courses in your LMS and send over appropriate content.

Guides, e-reserves and subjects can have multiple Metadata listings / values for this Name, too! So one guide could have multiple course numbers associated with it (ART100 and ART150) or a course number and a general subject designation (ART150 and ART).

Stepped Search vs. Translation Table

There are two ways the LTI can search, described below. Thu UML set up is utilizing the Stepped option.

Stepped: This option is a search powerhouse, searching until there's either a match or nothing left to search! It's a super flexible search, allowing matches to be found on an exact value or a portion of the value.

It starts off with an "exact" search, based on the value passed from your LMS.
If it doesn't find a match, it removes a character from the end and looks for that value.
It keeps going and going and going until either a match is found or there are no characters left to search! (And it's super fast - even if it's a super long value to get through. ;)

You have a guide that relates to course ART150 - all sections of it. So you add ART150 to the guide metadata. A student in section 3 of the course clicks the link in the navigation. The value ART150.03.Jones.SPR16 is sent to the LTI tool...the Stepped search looks for that full value, then ART150.03.Jones.SPR1, and keeps taking characters off until it searches for ART150 and finds your guide!
Similarly, if you have a general subject guide for Art, but no specific course guide for a given Art class, you can add ART as the metadata for the subject guide. The Stepped search will keep taking off characters until it gets to ART, finds that subject guide, and displays that for the student!

Translation Table: This option allows you to tell the tool match this value from the LMS, to this other value in the Metadata in you're telling it exactly what to look for. In addition, you can assign subjects to a course, which allows you to narrow down the A-Z Database list link / Subject Librarians listing on the Library LTI page...more on that later. The Translation Table is discussed on the next page, but here's how it works:

The value from the LMS is found in the uploaded table.
The tool then takes the Metadata value associated with that exact LMS value and finds the appropriate content in LibGuides.
If there is an associated subject, it also limits the Databases link / Librarian Profiles area by that subject, if the Library LTI page is shown.