Difference between revisions of "Mapping"
Jump to navigation
Jump to search
| Line 28: | Line 28: | ||
== Ecosystems == | == Ecosystems == | ||
| − | * [[mapping/Finland|Finland]] {{Q|564}} | + | * [[mapping/Finland|Finland]] (item {{Q|564}}) |
| − | * [[mapping/Japan|Japan]] {{Q|681}} | + | * [[mapping/Japan|Japan]] (item {{Q|681}}) |
Revision as of 09:11, 13 May 2019
Introduction
This page is focused on mapping efforts for MyData ecosystems.
Get started
To get started: - open an account (not necessary, but helps in tracking afterwards your contributions); - go to preferences -> gadgets, and activate all of them.
Structure
The following categories have been identified as important:
- project project (Q567)
- organization organization (Q401)
- group (really, seems redundant with organization)
- individual human (Q355)
- concept (ill-defined at the moment)
Tasks
The tasks are ordered for maximal efficiency, both in learning (autonomy) and data entry. If the whole mapping project is thought of as a map, then:
- the nodes are best entered in batch, via CSV and [qs.personaldata.io | Quick Statements]
- the edges are sometimes best entered via a batch, sometimes better manually through GUI (depends on sizes)
- categorization and interdependency modeling of more complex things (like "concepts") is best done through the GUI with constant feedback of visual [query.personaldata.io|query] outputs (actual graphs).
We will use ad hoc processes to enter organisations, individuals and groups. Then we will figure out what to do for projects. Then for concepts. Then link all this together.
Ecosystems
- Finland (item Finland (Q564))
- Japan (item Japan (Q681))