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
* A course-specific guide if one exists.
* Else if the department can be identified, a subject/department
* 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.
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.