1 / 5

Problem

Problem. Lack of centralized management of INFORMATION – PROCESS – ASSETS for E-learning courses Information for a course ( iContent , LMS, EES brochure, metadata) isn’t centralized in one location, is very difficult to gather.

marsden-talley
Download Presentation

Problem

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Problem Lack of centralized management of INFORMATION – PROCESS – ASSETSfor E-learning courses • Information for a course (iContent, LMS, EES brochure, metadata) isn’t centralized in one location, is very difficult to gather. • Courses in iContent submission process are only tracked on a spreadsheet: ELPs and PMs have no idea where their courses are in the process. • Assets for courses (especially legacy courses and source files) are difficult to locate. • Courses and assets aren’t currently tagged with metadata in a way that ensures optimum reuse and interagency sharing. • A lot of the information required by the iContent form/metadata LOM/EES system is redundant, must be entered multiple times

  2. General Solution Course Tracking System (CTS) for Information/Process/Assets • Primary users: PMs, ELPs, Cybrarians, and LMS personnel • Secondary users: representatives from other agencies Solution components • Database: for ALL course information • Web interface: for data entry/search (including metadata file creation) • Repository server: for ALL course assets (including source files)

  3. CTS System Overview Course tracking website (log in) View your assigned courses Search for courses, content Edit tracking info Add a new course Add/edit/ delete metadata Database (Initially Access,, but eventually SQL Server) • Holds all info: • For a course • All metadata, including medical • Tracking/status information • Users and roles Writes metadata XML Repository (file server, intiallymediadev but should some day be public for interagency purposes) • Holds all assets: • Final course packages (.zip) • Source files • Metadata XML Metadata search for courses, content Third party search facility, uses metadata XML to return results (from ADL?)

  4. CTS Sample Process Flow Creates or procures content Saves source files and testing package to repository Log in, views his/her past/ present courses Adds a new course, including known metadata Notified of new course, logs in, assigns ELP Log in, views his/her past/ present courses PM dave ELP Updates status of course, edits any relevant metadata Cybrarian morgan Notified of ready course, notifies 508 office Database (Access, initially) Course info/ tracking website mCMS system 508 office Repository (file server) Metadata search for courses, content Other agency rep Notified of ready course, accesses course, updates status Final packages (including metadata XML) Source files Testing packages Search for available courses, downloads ELP Uploads corrected, FINAL version of course Gets course info, copies final package to iContent Checks metadata, exports XML Cybrarian morgan Updates status

  5. CTS System Main (into, login box) Main (into, login box)

More Related