Capture Context relating to a 3rd party tool

We like to be eco-friendly!

If only everything were in one system! These days, a core application has numerous interfaces for all the clever things we can now do online. From media to security to webinars, it’s almost impossible to get a real overall view of your users’ activity.   Well, it was…until now!


If you use plug-ins like the applications above, you may want to create a Context which, if we’re being technical, sits outside of your core LMS system. When you see these tools appear in your LMS webpages and they are not fully integrated, the tool is embedded within an IFRAME HTML element.   When a section of a page is within an IFRAME, anything within that section cannot be selected as it doesn’t really belong to your LMS webpage. However, there are some tricks in creating a Context and Recognition Rules which allow us to get pretty close.  

CREATE A CONTEXT FOR COLLABORATE ULTRA


Although Collaborate Ultra is a Blackboard Tool, it’s content and functionality are hosted from a separate application. Here are 2 ways to capture it’s use from your LMS:   Capture the Collaborate Ultra page in your LMS

1. Open up the EesyProducer and log into the relevant environment.

TIP! It’s a good idea to practice in your staging environment first.

2. Select the folder in which you want to save your Context in the Navigation Panel and click on the

icon.    

3. Enter the web address of your LMS application, log in, and navigate to a Collaborate Ultra page.   Click on Capture to name and save the page.

4. A new window will open prompting you to select Context Parameters for the page.  


We can see here that the Path is directly related to Collaborate Ultra. Therefore, this selection alone will ensure that whenever a user accesses Collaborate Ultra from your LMS, this Context will be triggered.   However, the above example only tells us when a user goes to the page and not if they actually take action whilst there. So let’s look a bit closer.  

Capture the IFRAME containing Collaborate Ultra in your LMS   For this example, we will work from the Context we just created.  

1. Click on the area of the Screen Capture which relates to Collaborate Ultra.  

You will see that, in the Windows Structure on the left, an HTML Element of IFRAME is highlighted and below, in the Details section, 4 Recognition Rules are available. As this is an externally hosted tool, the most appropriate Recognition Rule Attribute to use is the Source URL of the tool.

2. Update the Recognition Rule to suit your requirements.

  Looking more closely at the src Attribute value, we can see that there is a CourseID specified. Unless we are only interested in Collaborate Ultra use for one Course, we need to amend the parameters of our Recognition Rule to extract this.

By updating the Text and changing the Rule type to Contains, this Recognition Rule will now ensure that the Context is triggered when a user clicks in an area of a page, the contents of which originate from Collaborate Ultra.  

Don’t forget to name your Recognition Rule and Publish this Context for use with Monitors or Help Items.

CREATE A CONTEXT FOR TURNITIN


We are always working to be more inclusive. If your version of turnitin is fully integrated, then read no further. You can capture Contexts for it just like any other part of your LMS. If, however, your version of turnitin is not fully integrated, it’s content and functionality will still appear in an IFRAME.  

Capture a turnitin page in your LMS

1. Open up the EesyProducer and log into the relevant environment.

TIP! It’s a good idea to practice in your staging environment first.

2. Select the folder in which you want to save your Context in the Navigation Panel and click on the

icon.    

3. Enter the web address of your LMS application, log in, and navigate to a turnitin page.   Click on Capture to name and save the page.

4. A new window will open prompting you to select Context Parameters for the page.  


We can see here that the Path is directly related to turnitin. Therefore, this selection alone will ensure that whenever a user accesses a turnitin page from your LMS, this Context will be triggered.   However, the above example only tells us when a user goes to the page and not if they actually take action whilst there. So let’s look a bit closer.  

Capture the IFRAME containing turnitin in your LMS   For this example, we will work from the Context we just created.  

1. Click on the area of the Screen Capture which relates to turnitin.  

You will see that, in the Windows Structure on the left, an HTML Element of IFRAME is highlighted and below, in the Details section, 4 Recognition Rules are available. As this is an externally hosted tool, the most appropriate Recognition Rule Attribute to use is the Source URL of the tool.

2. Update the Recognition Rule to suit your requirements.  

Looking more closely at the value of the src Attribute, we can see that there is all sorts of junk in there which could mean anything. Therefore, we need to amend the parameters of our Recognition Rule to remove this.

By updating the Text and changing the Rule type to Contains, this Recognition Rule will now ensure that the Context is triggered when a user clicks in an area of a page, the contents of which originate from turnitin.   Don’t forget to name your Recognition Rule and Publish this Context for use with Monitors or Help Items.

CREATE A CONTEXT FOR EXTERNAL CONTENT LIKE YOUTUBE


Course content comes in all shapes and sizes from all sorts of places. Here are 2 suggestions on how to keep track.   Capture content types by their listing in the Course Content section

1. Open up the EesyProducer and log into the relevant environment.

TIP! It’s a good idea to practice in your staging environment first.

2. Select the folder in which you want to save your Context in the Navigation Panel and click on the

icon.    

3. Enter the web address of your LMS application, log in, and navigate to a Course Content list page.   Click on Capture to name and save the page.

4. A new window will open prompting you to select Context Parameters for the page.  

  We can see here that the Path is related to the Course Content list page. The Parameters also specify a courseID. For this example, we will make the Context valid for all Course Content list pages.   Now we can zoom in on the different types of content we see in this page.  

5. Select relevant identifying criteria for the content types you are interested in.

Here are a few examples:   You can use your own assigned icons which relate to the type of content in your LMS.  

By using the Connect to Sub-Context function, you can make sure that whether listed first or last, this content type is always recognized. To learn more, please see our Guide to Recognition Rules and Context Parameters.    

You can zoom in on a specific type of content or the application that the content originates from.

Screen Shot 2019-01-15 at 16.26.24

Selecting the Anchor HTML Element, we see an href attribute pointing to a specific YouTube video. Updating the value of the Attribute and changing the Rule to Contains allows us to pick up all videos sourced from YouTube.   However, just because an item is listed does not mean it is being viewed.   Capture a content item in action   We can capture menu dropdowns and popup windows in our screencapture and assign Recognition Rules to the items that appear within them. For this example, a new page Context was created with the YouTube video popup window open.  

1. Click on an area of the Screen Capture which relates to the popup window. This will usually appear towards the bottom of the Windows Structure.  

You can use the Windows Structure to find the HTML Elements that relate to the popup window content. In this case, it is the now familiar IFRAME.   When the IFRAME Element is selected, we can see that 5 Recognition Rules are available in the Details section. As this is an externally hosted website, the most appropriate Recognition Rule Attribute to use is the Source URL.    

2. Update the Recognition Rule to suit your requirements.  

Looking more closely at the value of the src Attribute, we can see that there is all sorts of junk in there which could mean anything. Therefore, we need to amend the parameters of our Recognition Rule to extract this.

By updating the Text and changing the Rule type to Contains, this Recognition Rule will now ensure that the Context is triggered when a user opens any video from YouTube listed on any Course Content list page in your LMS.   Don’t forget to name your Recognition Rule and Publish this Context for use with Monitors or Help Items.

We hope that these examples have helped you get to grips on how to use our tools on your tools. If you have a particular tool for you would like to capture a Context and you’re struggling, please don’t hesitate to get in touch so we can get stuck in and help you out!


CONGRATULATIONS! YOU HAVE NOW CREATED AND SAVED YOUR 3RD PARTY TOOL CONTEXT. BUT DON’T STOP THERE!