Project overview: Collaborative Graph-based Methods for Distributed Research (working title) #6
Labels
No Label
discussion
draft
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: DGF/dao-governance-framework#6
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Suggested (working) project title
Proposed project overview
Collaborative research is hard, but necessary - knowledge has expanded way beyond the ability of any single human to make sense of it all. The complex, wicked challenges facing humanity require complex answers, and thus coordinated, distributed and large-scale R&D efforts. However,the tools supporting distributed research are far and few between; even relatively preliminary tasks such as literature surveys are unexplored territory in terms of tooling and methodology for distributed teams.
This project will attempt to simultaneously research and develop tooling and methodology for distributed research, by “dog-fooding” our own tools and processes. Research being a broad term, the particular areas of focus we set will out with are:
(1) Distributed sensemaking: how to synthesize “raw” information into research questions, claims, and the evidence that supports them? How to create coherence and shared understanding in a distributed group setting?
(2) Value distribution: value is an important incentive driving distributed efforts. Value may include credit, reputation, or monetary remuneration. What computational tools support fair, accurate and contextually sensitive value distribution methods that help guide and incentivize cohesive group action?
Drawing on existing literature, the project will be built upon collaborative graph-based methods for distributed research:
mentioned in issue #7
marked this issue as related to #7
marked this issue as related to #8