You can now fully embed Credo content directly into your LMS (Learning Management System), VLE (Virtual Learning Environment) or other guides/website with Credo's embed codes. Any article may be embedded, including those with images, audio, or videos. Topic Pages may also be embedded, but only the main article and the definition from the Topic Page will be embeddable. See examples of embedded content in Blackboard and Canvas below:
- Credo Topic Page Embedded in Blackboard
- Credo Entry Embedded in Canvas
Copying an article/entry from Credo into an LMS or VLE
To embed an article/entry from your Credo reference database into an LMS, VLE or other guide/website, do the following:
In the user interface, find an article you wish to embed.
Click on the Embed icon at the top right of the article text (highlighted in orange in the figure below.)
Copy the full Embed Code.
Copy that embed code and paste it into your LMS or VLE.
To change the size of your embedded object, simply change the pixel value in the “height” parameter of the code. (Leaving the width as 100% will maintain the correct height/width ratio). For example, to double the size, change the height value to 800 as below:
<iframe src="/http://beagle.credoreference.com/entries/10254437.embed" style="position: relative; height: 800px; width: 100%;"></iframe>
Behavior of links and embedded entries in open web page
**Authentication behavior when linking to an entry/article or topic page:
Scenario 1: Link to a Topic Page If the user is authenticated or rides in on a proxy, he gets to the Topic Page in Credo and can link to his other content from there. If he's not authenticated, he gets to see the Topic Page and links to other Topic Pages but doesn't get into more content. If the open web page has been set up as a “known source” by Credo’s support team, the usage of the entry gets counted even if the user doesn't authenticate.
Scenario 2: Link to an entry/article If the user is authenticated, he gets to the entry (assuming it's in his account) and can navigate to his other content from there. If the user isn't authenticated, he goes to Credo’s login screen. If the user is authenticated but doesn't have the entry in his account, he gets a suggestion for a similar entry and, from there, he can navigate to other content in his account. The link only counts as an entry viewed when the user gets to the entry in Credo.
**Authentication behavior when embedding an entry/article or topic page:
Scenario 3: Embedded Topic Page The entry-view counts against the user's account if the open web page is set up as a “known source”, but the user doesn't automatically authenticate if he links from the open web page to Credo. If the user is on campus or if the embedded topic page link contains a proxy, and the user links from the embedded TP on the open web page, he gets into his account. If he's not authenticated, he can access the Topic Page and link to other TPs from there on CORS but can't access content in his account until he authenticates.
Scenario 4: Embedded entry/article The entry-view counts against the user's account if the open web page is defined as a “known source” by Credo’s support team, but the user doesn't automatically authenticate if he links from the open web page to Credo. If the user is on campus or if the embedded entry link includes a proxy and the user links from the embedded entry to CORS, he gets into the account subscription. If not, the user gets access to the entry and to Topic Pages but would have to authenticate to access any more content in his account.