...
- Make sure your terms can stand alone. While context within the tree enhances subject terms, there are some places within Mandala where terms won't be shown within the tree. Avoiding vague terms like "yes" or "no" make your terms easier to find and use.
|
|
|---|---|
|
|
- Consider both specific terms (Andean sheep farmers) and general terms (wool). Remember, your terms can really enhance the Mandala project as a whole, and other people may eventually want to use your broader terms.
Make sure the group of subject in a single level is cohesive . This means every subject in that group has a similar "type" and "scope." Don't put very specific subjects alongside general subjects.
Make sure there's a clear flow for each path in the tree . There should be a logical progression from the topmost point of the tree to each individual subject at the bottom.
Make sure the flow goes from broadest to narrowest concept.
- Remember that other people can (and will) use your terms . Consider thinking briefly about future use cases alongside your own use case.
Avoid repetitive tree structures . Remember, you can use two tags on an asset to suggest a relationship that isn't represented in the ontology. Using the example below, you could tag assets with both the Education Stage and the Interventions.
Try
AvoidEducation
Education Stage
Preschool
K-12
Higher Education
Interventions
Counseling
Tutoring
Education
Preschool
Interventions
Tutoring
Counseling
K-12
Interventions
Counseling
Tutoring
Higher Education
Interventions
Counseling
Tutoring
Place Trees
Use the places viewer (by searching or browsing ) to determine whether an existing place suits your needs.
This can be tricky to decide, especially if there's a place that seems close to what you 're need. There aren't any "right" or "wrong" reasons to create a place, and these decisions will depend on your project. But here are some things to consider:
...
Knowledge Map hierarchies in Mandala are built with tree data structures. Each knowledge map term is a node on the tree. You can place a knowledge map term using its parent — that is, the higher-level term the knowledge map falls under. Nodes that fall under a parent are its children its children. If a node doesn’t have a parent — that is, it’s the highest possible level of the tree – we call it the root node. A node may have many children, but it only has one the parent. In the example above:
- Architecture is the root, since it has no parent
- Architecture is the parent of two children: Building materials and Building dimensions
- Building dimensions is the parent of three children: Building layout, courtyards, and Stories
- Building materials is the parent of three children: Mud, Mudbrick, and Stone
- Building layout is the parent of three children: courtyard structure, Mansion, and Massive structure
- Mansion is the parent of one child: Large Mansion
To format your tree in a spreadsheet, every row represents a node. In the first column, write the node's name. In the second, write the name of the node's parent. If the node is a root, the parent will be blank. Make sure you use consistent names, with consistent capitalization. Here's a table for the sample tree:
...