life-itself / life-itself/secondrenaissance
[inbox] Visualization
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 11
- Forks
- 19
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
## Old (2022) Visualisation Ideas
**2024-01-04 @catherinet1 reviewed all open issues in ecosystem repo and added all visualisation ideas below.**
- [ ] ➕2022-01-22 Org page: a word cloud based on text on the orgs' front page see e.g. https://github.com/jasondavies/d3-cloud
- [ ] #47
- [ ] #24
- [x] #46
- [ ] #75
- [ ] #4
## Sensemaking Methods Brainstorm
- [ ] Text scraping and analysis
- [ ] Analysing transcripts from podcasts could also be interesting
- [ ] Generating a knowledge graph showing key terms / thing they tend to talk about, e.g. https://stephenreid.net/k
## Dec 2021 - Method for embedding and/or downloading vis
so that can be used on e.g. front page or downloaded by users ...
* [ ] Embed our logo
* [ ] Decide if we need anything special
### Notes
Crudely a d3 vis is just an svg so can just embed the svg. For downloading we might want a png and also to embed our logo somehow.
For embedding across into another page maybe we just have the code as a raw component ...
Found https://github.com/exupero/saveSvgAsPng via https://stackoverflow.com/questions/36303964/save-d3-chart-as-image but repo is marked as archived and no changes in 2y.
# Meeting Notes
## 🚚 PROCESSED 🚚 2023-12-21 Ecosystem Visualisations Meeting
- [x] 🧘 Meditation
- [x] 👋 Check-in
- [x] 📝 Create agenda
- [ ] Review next steps from last meeting
- [ ] Post about visualisation options https://github.com/life-itself/ecosystem/issues/180
- [ ] Related tribe/centre mapping efforts: https://github.com/orgs/life-itself/discussions/969
- [ ] Plan of work/next steps
- [x] Consolidate all the old (2022) random visualization ideas into an inbox https://github.com/life-itself/ecosystem/issues/208 **2024-01-04 @catherinet1 reviewed all open issues in ecosystem repo and added all visualisation ideas below.**
### Where we should go ...
Meta-Goal: share this work early and often and get more attention as that is part of helping the sensemaking in the area ...
- [ ] "Previous work/Literature review" Write up 1-2 blog posts (or do live chat and then post that with a write-up of it, or ... )
- [ ] The visualization inspirations
- [ ] Approaches to sensemaking and some previous inspiration (either in our area or outside) e.g. memetic tribes, liminal web piece, even our own sensemaking efforts etc
- [ ] Draw 2d maps a lot starting with landmarks we know e.g. people, thinkers, podcasts, blogs and seeing to identify "regions" (emergently potentially)
- [ ] Reflect on other options e.g. text-driven analysis
**Publish early, publish often** 😉
- [ ] Building up directory
### Next actions
- [x] Catherine add meta tribes (https://www.joelightfoot.org/post/the-liminal-web-mapping-an-emergent-subculture-of-sensemakers-meta-theorists-systems-poets) to tribe/centre mapping efforts (NB: this came out at same time as our original mapping - and we talked with Joe about it) **Added to: https://github.com/orgs/life-itself/discussions/969**
- [x] Matt share with us the memetic tribes essay **Shared PDF in https://github.com/orgs/life-itself/discussions/969**
- [ ] Matt post notes on nodes/relations as a discussion thread
- [ ] Catherine process today's meeting notes
- [ ] Schedule a sprint end of Jan
- [ ] Elisa read ecosystem.lifeitself.org/sensemaking
### Notes
- [x] Matt's and Catherine's discussion about tribe mapping
- [ ] At ~ 1101 (probably 20m in) Catherine explains why tribe-mapping could be useful. 🚩
- [ ] If we can't see our differences we can't work constructively with them
- [ ] Maybe use an alternative word to 'tribe', e.g. 'interest' but something stronger... affinity?
- [x] Suggestion of how we could move forward
- [ ] Ship one map sketch and share a week (or a day)
- [ ] Flag it is incomplete/a sketch -- knowing that it's going to be "wrong"/incomplete gives us freedom
- [ ] Constraint of the 2D geographical map, can represent landmarks and group them into areas - https://slatestarcodex.com/2020/02/02/map-of-effective-altruism/
- [ ] Can cycle through different possibilities, e.g. different categories of things we might map, e.g. of sub-areas of the territory, like engaged spirituality, or eco-sprituality, or metamodernists etc
- [ ] Share on Twitter and ask for feedback
- [ ] Map can show several things e.g. the major regions and the "hubs/campfires" etc on that map
- [ ] Matt: suggest focusing on a few more focused maps instead of putting everything on one big map
- [ ] Have a sprint week mid to late January
- [ ] Ship blog post with existing material ahead of sprint
- [ ] Sensemaking is broad. Can we define our focus/intention more?
- [ ] Meta-goal: share more, get more attention for the work we're doing. Even if it's critical attention (helps us get feedback and generate discussion). We can't make people connect or not connect, or align etc.
- [ ] Text scraping and analysis would be a novel and interesting thing to do here
- [ ] Matt has written scrapers before, might not be too hard to do... a couple of days
- [ ] Take various thinkers in this space: where would we plot them?
- [ ] Podcasts could be a concrete area to do
- [ ] Analysing transcripts from podcasts could also be interesting
- [ ] Generating a knowledge graph showing key terms / thing they tend to talk about
- [ ] e.g. https://stephenreid.net/k
### Asides
- [ ] archive a copy of memetic tribes post
- [ ] 📜 Could write a blog post ...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files, entry points, or tests are identified. Start by reviewing the unchecked visualization ideas and linked issues, then define one focused visualization and its completion criteria before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- d3
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100