Curriki undertakes a basic file check for every resource when it is first contributed to the resource repository. The purpose of basic file checking is to ensure the baseline appropriateness of every resource in the Curriki repository for access and use by an educational audience.  This is a manual, editorial process that takes place after publication of the content in the Curriki system.

This check deals with assets in the repository that are patently offensive, harmful (viruses), not educationally focused, or otherwise objectionable (vandalism).  File Check is separate from the CRS process, which undertakes to judge curricular content based on criteria relating to instructional design and content accuracy. CRS judges quality and value for instruction, while file check judges basic suitability for Curriki's repository.

Basic File Check Standards
A resource is given a File Check Status other than OK if:

• It is clearly objectionable (porn, hate, vandalism, etc.).
• It is a link to a commercial web site where no free educational resource is clearly available on the entry page.
• It is not educational content, and it is not contextualized (i.e., used within a lesson) to make it educationally useful.
• It is a broken link or file.
• It breaks the display or functionality of the Curriki.org site, or is an attachment that has a virus.
• It shows incomplete content (aka the “empty template” syndrome).

In addition, resources may be marked for special review if:

• It is a Zip file attachment in which case it may need technical review.
• It appears that it might be copyrighted content, not cited appropriately, or not provided by the copyright holder, and requires editorial review.

Although the File Check status is not displayed to most members, any resource that is not deemed OK is hidden from the user base until the issue is resolved.

Members who contribute content that does not appear to offer value in the educational arena will be contacted regarding their contributions. Please see Curriki's Terms of Use for more information about contributing content on Curriki.

What File Check does NOT do:

• The File Check process does not automate the identification of excellent resources or contributors that should be considered for featuring on the site.
• The basic file check does not address resources that have been updated; it only addresses resources that have been created or added to the repository. Curriki will depend on the CRS process and “Flagging” functionality to capture and react to inappropriate content that members input upon editing/updating a resource.
• The File Check process does not check resources that have an Access Privilege of “Private”. These resources are considered to be in draft format, and therefore most likely they represent sample content or works in progress.
• The File Check process does not check resources in languages other than English. Curriki hopes that speakers of other languages will use the "Flagging" functionality to capture and react to any issues with this content.

 

The Flag function enables community members to bring to Curriki’s attention any resources which may be inappropriate. For information on best practices for using this function, please see the Flagging section of the Help Collection.