Good Morning Anons. I work professionally communicating concepts and information between different groups, explaining complex ideas in general and in detail. I am considering getting involved here (I'm already memeing and twatting) but I understand how much work this concept mapping is going to be to do this right - both for research purposes, and communicating outside the chan to help educate the general public. I'm first going to offer some advice to all mappers as I decide how much further I can get involved right now.
-
A project this big will require a team effort - this is much bigger than and cmap I've seen - so pick a tool that allows secure collaboration but also allows you to save your work offline to avoid corruption/sabotage by others. I have used a tool called "CMAP" to do this - it's free and there are a few ways to collaborate. ( https:// cmap.ihmc.us/ )
-
The nodes ("concepts" or "bubbles") on the chart are where the data is summarized as a label. This label should link off-chart to supporting documentation, or to another cmap that "drills down" into that data label. That more detailed map should repeat the process, drilling down and down until every single node of importance has a link off-map to supporting documentation (web page, wiki, blog, qpost archives, youtube videos, tweets, other anon's hard work, etc).
-
Relationships 101: The REAL value of a cmap is in the METADATA between the major nodes. In many cases this is represented by a line - the "connection" - but that connection should be labeled with a "relationship type" using "linking words". Relationship types should be descriptive. (A)–is supported by–(B) || (B)–has a–(C) || (C)–is a part of–(D). These relationships are how you describe the concept you are conveying. Many times these relationships are directional, so label them ("linking words") like that, optionally use arrows to describe direction.
-
Relationships 102: Sometimes the nature of this relationship is complex enough to warrant it's own node, with a link to reference materials, or even another cmap to explain the relationship process. A good example of this is a very complex bidirectional or conditional relationship. These can get tricky and confusing.
-
Categories will develop. Tagging will be helpful. Color-coding the nodes will help visually organize categories.
-
You map is a guide for the reader. It's best to link to the supporting documents and let your reader mentally map the little details themselves. There are several reasons for that. 1) Your map is a guide for the reader. 2) The reader will learn more by absorbing the details on their own. 3) If your map is too detailed it is cumbersome and overwhelming. 4) You'll never finish a map that is overly detailed.
I'm travelling for work next week, and may have time to get started on mapping. I do not want to do this alone (I can't)… if I set-up a system for collaborating on maps - can I count on you to take a part of the map and start diagramming? Literally ANYONE can create these maps with a little practice, following some basic "best practices", and working together.
The mapteam will also have to defend our work from shills. Given the nature of this project, I'm not yet sure how to do this and keep everything as anonymous as possible. (I think it's important to be as anonymous as possible, for our own personal safety) I'll do some research on this before getting to far into the mapping effort. (We may need specialist help here).
This is not a game. Anyone participating is potentially at risk - because the product of this work (when done correctly) will be of GREAT REAL THREAT to the subjects of the map. We are citizens, with families, and jobs, and we don't have bodyguards and cyber warefare specialists keeping us safe.
If you think you'd like to map with the mapteam, send a quick reply to this please so I know you are out there and you are interested.
Apologies for the length of this read.