--- tags: networks --- # Vaccines concept map ## Branching out > Using current [outline](https://docs.google.com/document/d/1SaGh7OKlC2QOs67uc8Mm_HIbHAJqAsT3DfF78uYQ1Qo/edit) We need define node attributes on a separate line, I think. >> Ahh yes that cleans it up! I'm trying to see if vaccines at the top or vaccines at the centre looks better as a hierarchy. ```graphviz strict graph ip_map { "History"[URL = "https://scibeh.org"] "Vaccines" -- { "History" "Uptake behaiour" "Public discourse" "Narratives" "Communications" "Misinformation" "Policy problems"}; "Public discourse" -- {"Monitoring" "Research" "Tips for engaging"} "Narratives" -- {"Channels" "Message design" "Sources"} "Channels" -- {"Social media" "Websites" "Broadcast" "Print media"} "Policy problems" -- {"Distribution" "Priorities" "Mandatory programmes"} } ``` > Maybe cleaner version: `neato` and `circo` look like nice [layout algorithms](https://forum.graphviz.org/t/layout-algorithms/59) for our purpose. We can also amend different [attributes](https://graphviz.org/doc/info/attrs.html). ```graphviz graph G { layout = circo node [ fontname = "helvetica" fontsize = 20 ]; vaccines[label = "Vaccines"][color = crimson] history[label = "History"][URL = "https://scibeh.org"][color = blue] behavioral_fatigue [ label = "behavioral fatigue\nclick on me!" URL = bwXpvWrcRKy7FdGdYKDyTQ fillcolor="red:green" style=filled color=yellow fontcolor = white fontname = "helvetica-bold" fontsize = 30 shape=diamond penwidth = 10 ] vaccines -- history; vaccines -- "Uptake behaviour"; vaccines -- "Narratives"; vaccines -- "Public discourse"; vaccines -- "Communications"; vaccines -- "Misinformation"; vaccines -- "Policy issues"; } ``` # Clickable nodes You can add links to nodes! See the example below (taken from [here](https://github.com/hackmdio/codimd/issues/1312)). ```graphviz digraph G { A[label = "Click on me!\nI'll take you to the scibeh website!"][URL="https://scibeh.org"]; B[label = "No, click on me!\nI'll take you to the Boosting website!"][URL="https://scienceofboosting.org"]; A -> B; } ``` # More stuff See https://hackmd.io/c/codimd-documentation/%2F%40codimd%2Fextra-supported-syntax ```sequence Alice->Bob: Hello Bob, how are you? Note right of Bob: Bob thinks Bob-->Alice: I am good thanks! Note left of Alice: Alice responds Alice->Bob: Where have you been? ``` ```flow st=>start: Start e=>end: End op=>operation: My Operation op2=>operation: lalala cond=>condition: Yes or No? st->op->op2->cond cond(yes)->e cond(no)->op2 ``` ```mermaid gantt title A Gantt Diagram section Section A task :a1, 2014-01-01, 30d Another task :after a1 , 20d section Another Task in sec :2014-01-12 , 12d anther task : 24d ``` ```vega { "$schema": "https://vega.github.io/schema/vega-lite/v4.json", "description": "A simple bar chart with embedded data.", "data": { "values": [ {"a": "A", "b": 28}, {"a": "B", "b": 55}, {"a": "C", "b": 43}, {"a": "D", "b": 91}, {"a": "E", "b": 81}, {"a": "F", "b": 53}, {"a": "G", "b": 19}, {"a": "H", "b": 87}, {"a": "I", "b": 52} ] }, "mark": "bar", "encoding": { "x": {"field": "a", "type": "ordinal"}, "y": {"field": "b", "type": "quantitative"} } } ``` https://markmap.js.org/ doesn't currently work here on hackmd, unfortunately. That would also be a great way to present things. ```markmap # markmap-lib ## Links - <https://markmap.js.org/> - [GitHub](https://github.com/gera2ld/markmap-lib) ## Related - [coc-markmap](https://github.com/gera2ld/coc-markmap) - [gatsby-remark-markmap](https://github.com/gera2ld/gatsby-remark-markmap) ## Features - links - **inline** ~~text~~ *styles* - multiline text ```
Last changed by  
 
SciBeh
544

Read more

Active SciBeh projects

Here you will see SciBeh's current projects. If you would like to get involved with any of these, please contact the lead SciBeh team member listed, or email contact@scibeh.org and we will put you in touch with the right person. If you have an idea for a project that would benefit from collaboration, do get in touch! We are happy to help you lead a collective intelligence project with us. SciBeh Knowledge Base What's this project about? <span style=background-color:yellow>Here a description of what the knowledge base project is currently doing What can I get involved in? We welcome volunteers interested in: <span style=background-color:yellow>Add here</span>

3/28/2023
Using the SciBeh Hypothes.is Knowledge Base

Video guide to SciBeh knowledge base You can watch the video below for a quick visual guide to using SciBeh's hypothes.is knowledge base. The video covers all the content covered below. About hypothes.is and the SciBeh knowledge base SciBeh maintains an eclectic knowledge base. Here you can find a wide range of items ranging from tweets, newspaper and blog articles, reports to preprints and peer-reviewed articles, all on the topic of behavioural science and responding to COVID-19. We use the tool hypothes.is to annotate each item in the knowledge base. This means that the curated items are tagged with key words, dates, and links to where the item has been referenced on the Internet. How the tool works SciBeh collects input from different sources: discussions on Twitter, Reddit, links sent to us by contributors. Our team of volunteers annotate all of these links---each volunteer annotates 100s each week!---using hypothes.is. When an item is annotated, it gets added to SciBeh's hypothes.is collection. That's the knowledge base you can search for COVID-19-related research and discussion. You can read more about the process of curating items for the knowledge here.

9/16/2022
manifesto documentation

Our process, in brief, has been: Workshop was held with notes taken by assistants. [I’m trying to find this---the SciBeh notion page got upgraded and so it’s moved!] We invited attendees to sign up as authors or CLAs, with the commitments laid out (specifically: minimally a paragraph of writing for authors) Three different structures proposed (Ulrike, Miso, Dawn). Miso + Dawn independently reviewed the workshop notes and highlighted relevant points. This is all the stuff in the initial outline after the << NEW STRUCTURE AFTER VOTING ENDS HERE >> line on the g-doc: https://docs.google.com/document/d/1xbWN9BwfKz4bzRKt0KHc9GaFjOUsPqmh/edit CLAs had a meeting to discuss structure, based on this proposal after people had commented as a springboard for discussion: • Establishing the problems that require CI as a solution o Current platforms/channels & limitations o External forces (“landscape” of SciComm and actors involved)

6/24/2022
test polis report embed

A Manifesto for Science Communication as Collective Intelligence Authors Join the conversation! Why citizens need reliable knowledge Many of the most pressing challenges societies face today—from climate change to global pandemics—require large-scale, collective decisions informed by the best available evidence. It is only when public beliefs are built on reliable knowledge, rather than poorly informed opinions, that we can successfully address these challenges. However, there are barriers to effective science communication, especially in rapidly evolving crisis situations or when evidence conflicts with political or commercial interests. Barriers: social media Social media notoriously prioritises emotion above evidence-based information and it is especially vulnerable to very active, extreme voices, which can skew users' perceptions of the opinion landscape. The rejection of authoritative sources can also create an "epistemic vacuum," leading people down the rabbit hole of conspiratorial sources and low-credibility content as they seek alternate sources and explanations.

5/5/2022
Read more from SciBeh
Published on HackMD