Further I propose these other items as part of a regular data profile:
"content evaluator" -- this tags content focused on supporting those who are evaluating the materials and might include reviews and other non-core supporting materials related to the content.
"grader" -- this is material for those who are grading a specific exercise. It might include rubrics, answer sheets and other data
"leader" -- for materials such as a group exercise where there is no teacher but someone is leading the session
"participant"-- for other participants where a leader is described.
John Fontaine
I am the project manger for the LRMI Tagger and Search tools. I've been monitoring (lurking) this group to see how progress is made on this topic as it affects our design and development of future versions of the LRMI Tagging Tool. After speaking today with Michael Jay of Educational Systemics about how to modify Tagger to support both age and grade level, I thought it may be beneficial to circulate the approach here for your feedback.
What we are contemplating is:
For publishers who may typically align their content to grade level, especially in the US, they would be able to leverage their existing metadata. For smaller publishers or those creating OER, they would have a choice to make of specifying age or grade, at their discretion. If they are using Tagger, than they would be sure to have their tagged content properly aligned to LRMI such that their selection would be immaterial as far as Tagger is concerned. If not using Tagger, we would still be able to publish our best practices for tagging. It also retains a significant level of granularity which I believe is desired by publishers and content creators to make their content discoverable for very specific searches.
Looking forward to your feedback.
Eric Weiss
LRMI Search and Tagger Project Manger
Agilix Labs Inc.
Do you think autocompletion facilities offer scope for improving the
situation here? i.e. something that looks like a text field box, but
in fact when they start typing, it's matching against remote database
entries and recording a canonical URL ID "behind the scenes"?