Installing and developing on UDOIT is actually quite easy, below is the documentation to help you get started!

Please see UDOIT_Release.pdf (distributed with the source code) for more information about licensing.

Copyright (C) 2014 University of Central Florida, created by Jacob Bates, Eric Colon, Fenel Joseph, and Emily Sachs.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

Primary Author Contact: Jacob Bates jacob.bates@ucf.edu

UDOIT uses the QUAIL PHP library, which has been heavily customized to suit the needs of UDOIT. This library requires distribution of tools developed with their library under the GNU General Public License version 3

PHP 5.4 is required to run UDOIT without any modifications. We have not tested it on 5.5 or 5.6, but some users have been able to modify the code to work on 5.3. In order for UDOIT to work on PHP 5.3, you will need to convert all empty array initializations from using the newer [] syntax to use the older array() syntax.

UDOIT uses Composer to manage its dependencies, so cd into your UDOIT directory and run this command before anything else:

$ php composer.phar update

UDOIT saves generated reports to disk for easy retrieval. Create a folder called reports in the root of the UDOIT project, and make sure PHP has permissions to create files and folders within that folder.

There are only two tables required to run UDOIT. They are:

reports

CREATE TABLE `reports` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `user_id` int(10) unsigned NOT NULL,
  `course_id` int(10) unsigned NOT NULL,
  `file_path` text NOT NULL,
  `date_run` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `errors` int(10) unsigned NOT NULL,
  `suggestions` int(10) unsigned NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=442 DEFAULT CHARSET=latin1;

users

CREATE TABLE `users` (
  `id` int(10) unsigned NOT NULL,
  `api_key` varchar(255) NOT NULL,
  `date_created` date NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Make a copy of config/localConfig.template.php, rename it to localConfig.php.

$referer_test This is a regular expression that lets UDOIT detect whether the user accessed UDOIT from the correct URL. For instance, UCF's value for this is: $referer_test = '/(webcourses.ucf.edu)/';

Please refer to the Canvas API Policy before using this application, as it makes heavy use of the Canvas API.

$base_url This is the URL of your Canvas installation

$consumer_key This is a consumer key you make up. It will be used when installing the LTI in Canvas.

$shared_secret This is a shared secret you make up. It will be used when installing the LTI in Canvas.

Since this application uses Oauth2 to take actions on behalf of the user, you'll need to sign up for a developer key

$oauth2_id The Client_ID Instructure gives you

$oauth2_key The Secret Instructure gives you

$oauth2_uri The "Oauth2 Redirect URI" you provided instructure. This is the URI of the oauth2response.php file in the UDOIT directory.

These value of these vars should be obvious:

$db_host

$db_user

$db_password

$db_name

$db_user_table

$db_reports_table

1. Under Configuration Type, choose By URL.
2. In the Name field, type UDOIT.
3. In the Consumer Key field, copy the value from $consumer_key in your config file
4. In the Shared Secret field, copy the value from $shared_secret in your config file
5. In the Config URL field, input the URL that points to udoit.xml.php.
6. Click Submit.

UDOIT relies on 3 libraries installed through Composer to function:

Httpful

HTML Minifier

mPDF

Please refer to the documentation for these three libraries for additional information.

File: lib/Udoit.php

This is the class which will scan a Canvas course's content and a return a UDOIT report if any problems are found.

See class definition

Iterates through selected content types to build the final report object.

This calls the Quail library to scan HTML and check it for accessibility problems.

Makes API calls to Canvas and retrieves HTML and other data from selected content types.

Increments the current page number for either Files or Pages in the event that their results are paginated.

File: lib/Ufixit.php

This is the class which will fix problem content and upload it to a Canvas course.

See class definition

Adds the alt text value to the image that's missing it.

Replaces the old color/background value with the one chosen by the user.

Converts the first row, first column, or both into th elements - It gives them the proper scope value as well.

Adds the col or row attribute to any th elements without them.

Gets a file from a Canvas course based on the $start_id parameter.

Renames an element to whatever name is specified in the $name parameter.

Fixes the HTML within assignments and uploads it back to the Canvas course.

Fixes the HTML within discussions and announcements - they are of the same content type - and uploads it back to the Canvas course.

Creates a temporary file, fixes the HTML within it, then uploads it back to the Canvas course.

Fixes the HTML within pages and uploads it back to the Canvas course.

Fixes the HTML within the syllabus and uploads it back to the Canvas course.

All of these files are located within the /lib directory.

This file is called when clicking the "View Old Reports" tab. It connects to the database using PDO, selects reports matching the course id, and outputs a table with the data.

This file decodes a a UDOIT report either from a JSON file or a JSON string (if not viewing a cached report). Then, the report HTML is echoed to be displayed to the user.

This creates a PDF from the HTML of a UDOIT scan and allows the user to download it.

The file is where all the magic happens, so to speak.

Increments a progress key in the global $_SESSION variable that some AJAX in default.js talks to in order to track the progress of a UDOIT scan.

• Jacob Bates
• Eric Colon
• Fenel Joseph
• Emily Sachs
• Karen Tinsley-Kim
• Joe Fauvel
• John Raible
• Kathleen Bastedo
• Nancy Swenson