OpenRefine / OpenRefine/openrefine.org

OpenRefine ecosystem map

Open
#325 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
161
Forks
142
Avg merge
6h 10m
Merged PRs (30d)
9

Description

Issue created from this conversation https://github.com/OpenRefine/openrefine.org/pull/303#discussion_r1543522725. The diagram discussed is available on this branch: https://github.com/OpenRefine/openrefine.org/blob/ecosystem_page/src/pages/ecosystem.md


In this diagram I struggle a bit to understand what is a node and what is an edge.
The type of concepts that go into nodes doesn't seem to be uniform to me. For instance there are nodes about:

  • "user support" (an activity)
  • "support forum" (an online space)
  • "advisory committee" (a group of people)

Are those meant to always refer to a specific group of people? Maybe the phrasing of the nodes could be adapted to make that clearer ("translators" instead of "translation", and so on)

Then I have the same sort of problem with edges. What does an edge mean?

  • "reports to"? (such as in "project manager" - "advisory committee")
  • "is included in"? (such as in "reconciliation services" - "third-party developers")
  • "communicates with"? (such as in "advisory committee" - "CS&S")

And then it's not clear to me why certain edges are there and others not. For instance, why is there an edge between "funding partners" and "advisory committee" but not between "funding partners" and "project manager"? Why an edge between "code of conduct committee" and "advisory committee"?

Also I have the feeling that the light blue box is meant to circle where the OpenRefine project starts and ends - but then do we need the central "OpenRefine project" node? Can't that be a label added to the box itself?

Originally posted by @wetneb in https://github.com/OpenRefine/openrefine.org/pull/303#discussion_r1564516933

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with ecosystem_page/src/pages/ecosystem.md and read the linked discussion in pull request 303. Resolve what nodes, edges, and the light blue boundary represent before revising the ecosystem map. Done means the diagram has consistent concepts and relationships that readers can understand, with the rationale reflected in the discussion.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
design, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.