Utah Valley State College was facing challenges with distributing online course content across multiple platforms and devices. They developed a "Shadow System" to organize course content into packages that could be imported into different learning management systems and content management systems. This allowed a single source of course content that could be accessed on different systems and devices, solving problems around version control and platform migration. The Shadow System organized content into open and private sections and generated navigation for linear access on different platforms.
19. Shadow Files Packaged Navigation Created Cast Shadows Script Import Shadows into LMS/CMS Process Phase 2
20.
21.
22.
23.
24.
25.
Hinweis der Redaktion
Introduction to system we are experimenting to control versions and distribute content across platforms An experiment in philosophy as much as technology, you see course content delivery has always be of static copies of original, sometimes outdated content, not dynamic delivery of living versions
ask who's who ask who teaches mltpl separate sections who IDs multiple sections w/ multiple instructors versioning? who knows ocw (explain) who's involved duplication who's heard of educommons migration from version to version--painless? who's course content is available on handheld devices? who want's their content to be?
This is how one normally might attempt to solve these problems, with 3 or more copies of content on 3 or more systems.
This actually exacerbates the problem of version control, and version control is a big issue
Clip from City of Lost Children shows how multiple copies of an original can become confusing. 5 clone brothers and one “orginal”. Note at the end one clone says, I’m the original!
Mmm, leech
Shadow Files is like Web content leeching
This slide is kind of dumb.
Shadow solution 3 or more platforms get content from single host Basic web server Like a repository, but different—repos is for scos/los. Shadows can do scos but meant for photocopying Instead, host content is referred to by systems…
Highlight may be the handheld devices; this is something most LMSs still fall short of doing Survey in MCT class showed consensus on desire for mobile content, some wanted text on mobile phone or pda, some wanted audio for download
This is what some pages will look like on mobile browser if the mobile connection doesn’t work
, Web content living, breathing Could foster community; Multiple instructors in a dept working on a single source
Shadow Process. This is what you would do anyway in one sense or another Instead of ON lms we do this on the local computer—a critical step—even if shadows don’t work for you this should be part of every process: Offline development helps with backups, templates, not internet dependent, mass changes (search and replace) liberation from LMS, fosters organization of courses and content
These additional steps: 1. create an independent, web-based navigation of course content; 2. create simple and IMS-compliant shadow files packages; 3. allows simple referencing of shadow source from any number of diverse platforms. So the LMS platforms still exist, they just use shadow files rather than copies of source files. Easy to implement
Process Walkthrough Show digital files Upload to server Show mkshadow script View navigation Download IMS package Login to WebCT Vista Upload and Import package View files
Maybe I’ll talk about this and non-semantic file naming LMSs should alread do real file sharing, opencourseware support, version control, import/export, handheld
Moodle, eduCommons, Sakai, Desire2Learn, et c. of private content
of private content (semantic file naming) Searchable, open