• Concept Mapping Group
Skip to end of metadata
Go to start of metadata
Unknown macro: {encore-collaboration-header}


  • Concepts must be able to be hyperlinks that result in direct action or menu pop-up.
  • Concept mapper must be small, lightweight, plug in to various applications.
  • Concept mapper must be collaborative, meaning that two or three or 12 students would see the same map and contribute to it, based on permission settings.
  • Concepts must have full metadata schema to let them be tagged automatically (e.g., with all of a parent's tags) as well as with new semantic codes, social tags, etc.

Pedagogical Purposes:

  • Students would have two kids of concepts in the map. The first would be a set of evidence pages and the second would be questions. The questions would reduce to just the first few words with an ellipsis, but would be grouped around the evidence pages. COmments could be added to the questions as maybe a third kind of concept.
  • Concept mapper would hold the entire map of the classroom, but then give individual students their own subset of concepts they had contributed, or pairs of students would get their joined set of concepts. Like Google Earth layers
    -Concepts could be re-mapped based on different queries to the semantic metadata, e.g., show me all the concepts that are related to greenhouse gases and agriculture. etc.

Examples of Concept mappers


Development strategy

I think what we're really thinking of here is a new tool, maybe not an extension of CC-map, but I'm not sure.
Remember, this is research, so we need to design the most flexible object-oriented tool we can. Its not rocket science to make java objects that fill a screen and are linked to a database.

But to start, lets specify the tool, then think about the best way to build it so that it interoperates with SAIL.

Resources, papers, etc.




Unknown macro: {metadata-list}



  • No labels