Create Hidden "Curriki Tags" Field & Apply Tags Based on Educational Level Selections

Spec can be found here: http://www.curriki.org/xwiki/bin/view/Project/MetricsSpecs

(3) Create Hidden "Curriki Tags" Field & Apply Tags Based on Educational Level Selections

(A) Create a new field/object for "Curriki Tags" to be attached to any repository resource, with content based on Educational Level selections.

This field should be invisible to the end user, e.g., contained within the header for the resource without any front-end display.

(ii) The contents of this field should be locatable by search engine indices/bots/spiders, both for Curriki's search system and those (like Google) from the wider Internet.

(B) For specific Educational Level selections during add and create processes and during editing of Information Settings, apply respective default Curriki Tags in the published/saved resource, as per the following chart:

Educational Level Selected
Hidden Curriki Tags
Preschool primary, early, childhood, pre-k, prek, pre-kindergarten, nursery, pre-school
K-2 primary, elementary, 1st, 2nd
3-5 elementary, 3rd, 4th, 5th
6-8 middle, 6th, 7th, 8th, tween
9-10 high, 9th, 10th, secondary, freshman, sophomore, teen
11-12 high, 11th, 12th, secondary, senior, teen

Curriki Tags should be applied for any new resource created in or added to the repository, including wiki and HTML resources created from forms/templates, as well as file uploads, VIDITalk-processed files, web links, collections, folders, etc.

(ii) The most current version of the Curriki Tags should be applied when an existing resource is edited and saved; in other words, on every Save action for an existing resource, apply the Hidden Tags field if not yet used, or overwrite the contents of a previously applied Curriki Tags with whatever field content is active in the system at the time of Save.

(iii) The Curriki Tags for a resource should be editable by an Admin in the Object Editor.

(C) Make it possible to editorially manage the table of Education Levels and their corresponding Hidden Curriki Tags.

Ideally, the table/list can be updated and saved without a formal release, i.e., via a Trans page.

(ii) Ideally, we will have access to a Revision History for the table/list.

(iii) The format of the table's information can be created however is simplest for implementation and to meet the other requirements; in other words, it needn't be a table, but could be a list.