Understanding how the translation table is used for content matching

The Translation Table requires you to upload a CSV file defining the values to be searched. The template has 4 columns: LTI Parameter Value, Guide, Course, and Subject Values. 

When using this option, the tool takes the LTI Parameter Name field value passed from the LMS and searches for that in the first column of data in the Translation Table. Once it finds it:

  • It looks at the Guide value and searches for that value only in Guide metadata.
  • Then it does the same for the Course and Subject values, searching E-Reserves Course metadata and Subject metadata, respectively.

So you could potentially have the tool search on 3 completely different values to find various pieces of content in your LibGuides system. This is especially useful if your course numbers are set up in a particularly complex way, if you're using a non-standard (or custom) field from your LMS for matching, or if you have very broad subject guides and very specific E-Reserves course information.

Once the tool finds all of the matches, it displays those matches based on the Content Display Behavior options you've selected...or uses the defaults, if you haven't opted to use any of the options in the Content Display Behavior area.

Example: Broad Subject Guides & Specific E-Reserves Courses

You'd set up the translation table to match many different courses to the same guide (adding just the one piece of metadata to the guide itself vs. however many it takes to match on all of those individual course numbers), but still have each course match up with the right E-Reserves course (if/where applicable).

  • LTI Parameter would list all possible values from your LMS. You'd get this data from your LMS administrators or possibly your Registrar.
  • In the Guides column, add all possible values. For example, all of the courses whose course number value starts with ART1 (denoting all foundation level Art courses) may have the Guide column value of ART1. You'd then add ART1 to your foundation level Art research guide in LibGuides and it will match to all of those courses in your LMS.
  • In the Courses column, add all possible values. For example, for ART150.03.JONES.SPR18 you might add that same string to the Courses column for that one course and the metadata for the E-Reserves Course in LibGuides. That way you're matching as specifically as possible to get the exact course match.
  • In the Subjects column, add all possible values. For example, you could limit your A-Z Database link to all Databases in the Art subject by adding ART to the translation table and to the Subject metadata.

Example: All LTI Parameter Data Changes Every Semester

For some sites, we've learned that the custom field they use for matching means that the data for every course changes every semester. The translation table is the perfect tool for this scenario!

Each semester:

  • Get the data from your LMS Admins - both the actual course information and the custom field data.
  • Add the custom data values to column 1 in the Translation Table.
  • Add the related metadata for the other fields. (Use as many or as few of the other columns as you wish.)
  • Upload the Translation Table file to the system.
  • Make sure your metadata in LibGuides is added / updated. Using the metadata upload option is a great way to initially upload and edit your metadata!

Related Articles