The UW Libraries does a similar thing. We have a service called the Guide Linking App that connects library guides our librarians make for subjects or specific courses. The linking app maps a guide's URL to either a curriculum code (for subject guides) or a course number (for course guides). A REST API is then available for various campus services to use. 

In our Canvas course pages, the REST API provides JSON that is used to fill in a page on how to use library resources for research. The content of the page depends if there's a course guide for that course. If not, a subject guide is provided. If there is no subject guide (usually due to a new curriculum code having been introduced), a default guide for that campus is listed. 

The API is also used by a service called MyUW, which is a portal to various UW resources. On a student's schedule page, each course gets a library link to the most appropriate guide.

All of this is managed through a Django app. Each university service is responsible for caching the data as to not overload it.



-- 

Kate Deibel, PhD | Web Applications Specialist
Information Technology Services & Digital Strategies
University of Washington Libraries
--

"When Thor shows up, it's always deus ex machina."


-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Gary Thompson
Sent: Monday, January 23, 2017 8:38 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Looking for libraries present in their campus' LMS

UCLA uses Moodle, branded as the Common Coollaboration & Learning Environment (CCLE). Eight years ago, Library IT tried to develop a Moodle block for courses, but that didn't work out -- we didn't have time to become effective Moodle developers.

After that failure, we took an approach of cooperating with the campus CCLE development team, providing resources and letting them expose course-specific resources in the Moodle user interface.

Library currently has three ways to support the CCLE:

 1. A link to library-managed electronic reserves for each course.
 2. A referral link between a course and the best LibGuide. The link
    simply send the registrar's course ID to our Drupal site, which then
    resolves and redirects to the most specific guide according to these
    priorities:
      * A course-specific guide if one exists.
      * Else if the department can be identified, a subject/department
        guide.
      * Otherwise a generic guide about conducting research.
 3. A web service exposes data about streaming audio and video, mostly
    for music reserves. The CCLE shows the titles and composers for the
    tracks that have been assigned to the course, along with a link to
    the library's streaming server. The CCLE uses JWPlayer to stream the
    resource within the Moodle course.

So after a false start, we focus on what we know (resources, data, web
services) and collaborate with the CCLE team so they can integrate the resources in the most effective way.

Gary


On 1/23/2017 5:38 AM, Kyle Breneman wrote:
> Does your library have some kind of presence within your campus' 
> learning management system (LMS)?  If so, what does that presence look like?
>
> Here at the University of Baltimore, we use Sakai and all users have 
> access to a tab, within Sakai, for the library.  The tab leads to a 
> page that is like an alternate portal to library services; very 
> stripped down from what you would get on our website, and in need of rethinking.
>
> Kyle