First look at Compliance auditing

I've watched our unit, colleagues and friends at other universities struggle with a complex issue that we are LEGALLY required to deal with; and that's navigating the tricky issues of compliance associated with production of digital media. The legal system and auditing complexities are only complicated by our LMS silos, file systems, dropboxes, and other distributed solutions that have things being produced all over the place and then worked into course content. Once there, the process slogs on in perpetuity as you or the next person never know when you'll uncover an accessibility issue or copyright violation unknowingly placed there by someone else who came in and "just tweaked" things.

Introducing ELMS Compliance Distribution (ECD). ECD has been in the roadmap awhile and I've expressed the idea but never had a working prototype, until now. With the comply.elmsln domain, you'll be able to have a central dashboard with dedicated process for the management of everything going on in your learning ecosystem. The biggest questions this allows you to answer are:

  • How much of our portfolio has had accessibility verified?
  • How much media are we using TeachAct to justify its use?
  • When was the last time we auditing course XYZ?
  • What items in course XYZ need verifying in the first place?

Comply is intended to help democratize the process of compliance management and auditing by leveraging the RESTful communications in ELMSLN to notify other systems when their material has changed. For example. You might have all the best excel sheets in the world indicating that you are in compliance, but they don't mean a thing if someone updates content after you've been combing through. With Comply, assets call home to report on their compliance status at the time of creation / update. This means that If you have a course with 200 pages that you've verified, a month from now you'll know exactly which 10 pages the faculty member updated and that you need to reverify since someone last went through.

This isn't finished, but it's working and should provide a great example of just some of the things you can do when you change implementation methodology of your projects.