Request for QuoteProject: Moodle plugin for accessible import and display of IMS content packages
Description of work: Develop a plugin for the open source php-based Moodle Learning Management System that displays IMS content packages in an accessible, usable manner.
Specifications:(A prototype of import page and content display will be provided.)
- Assumes IMS packages to be imported meet IMS Global Learning Consortium Content Packaging Specification http://www.imsglobal.org/content/packaging/
- Plugin will be developed to be contributed code to the Moodle project and will follow moodle.org coding guidelines available at: http://docs.moodle.org/en/Coding and the contributed code guidelines: http://docs.moodle.org/en/Development:Guidelines_for_contributed_code
- Plugin does not use frames or iFrames for content display
- Content appears with main Moodle header visible
- IMS table of contents index displays as left navigation using divs (no table layout or frames)
- Navigation display options should include: sub-menu pages, buttons: next, previous, & up
- Javascript will not be required for any functionality in the display of the navigation or content
- Content packages can be shared between courses
- Activity can be tracked in Moodle for each user view of IMS contents (specifically the pages listed in the manifest)
- Content prints making use of full printed page, without Moodle header and left navigation
- Plugin code will be thoroughly documented (moodle documentation page, plus description of functions, variables, general methods, ‘help’ for each item in admin page)
- CSS and HTML must pass automated validation using W3C validators
- Accessibility: Shell of IMS content display must meet WCAG 2.0 specifications
- Development may occur on Landmark’s development moodle instance or elsewhere
Meetings: There will be bi-weekly 30-minute phone check-ins, including description of progress and problems identified. All meetings will be conducted via phone or Adobe Connect sessions.
Timeline, Deliverables & Benchmarks:
- March 1: Begin work
- March 16: Programming approach and unanswered questions identified and documented
- March 30: Description of progress and problems, timeline for sharing plugin in moodle.org contributed code space
- April 13: Plugin running on Landmark’s development Moodle instance, ready for testing. Documentation draft shared (including code and comments).
- April 30: Plugin running on Landmark’s production Moodle instance. Plugin shared on moodle.org
- April 30 – December 31: Warrantee period. Any defects will be fixed by contractor at no additional charge
Please provide a price quote for the work, as well as links to three examples of work and contact information for two references to:
Julie Strothman
Project Manager, User Researcher
Landmark College Institute for Research and Training
jstrothman@landmark.edu