31:T810,> ### CONTRIBUTING AN IDIOM > Once you have logged your proposed idioms **fully** in the [RAMPVIS PhilTransA IDIOMS spreadsheet](https://docs.google.com/spreadsheets/d/1X46r1SVBUhYfS1tcA7pg1yziTqU75aFKCfBMIZge0CI/edit#gid=0) ... > > **FORK** this template to create an Observable notebook for your RAMPVIS idiom. > Edit it to describe your idiom and add your reflections as exlpained in the _Instructions_ and the [Phil Trans A - Plan for Paper Submission](https://docs.google.com/document/d/1cefY0rA8COyM5J7d-thSn3zvgP9osj4lzJSCnqOt63U/edit#) document. > Retain the _structure_ with ## Section Titles and --- hard returns before them.
> Please keep all sections! > Use [markdown](https://observablehq.com/@observablehq/markdown-quick-reference?collection=@observablehq/notebook-fundamentals) for text and we will transfer what is needed to the Overleaf document.
> We will use _some_ of Section 6 in the paper, but are likely to need to summarise this as we introduce the idioms, their context and our experiences briefly in there. > > Assume that everything written in here is for public consumption, the idioms will be a resource of (hopefully interactive) supplementary materials. So be sure to gain permission for any names, quotes or identifying context. > We'd like JavaScript to show the idiom in Section 6, but images will do - _as long as they are legible_. > Please keep things _as atomic as you can_. Don't describe a system, but try to focus on the VIS contribution that you have taken from the paper.
**How does this one thing that we know about VIS work (or fail) in the RAMP context**? > Publish it with a name of the form **rampvis_idiom_IDIOMNAME**
> The add the notebook URL to the [RAMPVIS PhilTransA IDIOMS spreadsheet](https://docs.google.com/spreadsheets/d/1X46r1SVBUhYfS1tcA7pg1yziTqU75aFKCfBMIZge0CI/edit#gid=0) > Please _publish early_ and then _republish_ up until the deadline. > Remember ... all idiom Observable notebooks must be complete by **20 August** - with reflection! 32:T4d4,> This is the key text about where you explain your use and development of the idiom in this context - the _RAMPVIS application_ of the thing we knew about VIS. > Be sure to relate this short description, with example graphics, to the **User Story** as clearly and consistently as you can. > > This should be _quite a short_ **what did we do** section. > But you do need to draw attention to _things you found_ from an epidemiological perspective. Do get these discussed and validated by members of the team. The better we are able to find, show, and annotate, examples of effective VIS in use the better. This is core work!
> These discussions may help with your subsequent reflection! > > Use _JavaScript_ for interactive examples that pull the data from above if you are able. > Otherwise, **legible** imagery will suffice -- see [Markdown / Images Section](https://observablehq.com/@observablehq/markdown-quick-reference?collection=@observablehq/notebook-fundamentals#cell-315) to see how to include images in a _markdown_ block. > > We are likely to use the description to introduce the idiom in the paper, and would like to create PNG or PDF figures from the JavaScript blocks that you add in here to show the idiom working.33:T561,> A chance to talk through the experience by adding examples or thoughts that take us in to the shorter statements on _successes_, _failures_ and _recommendations_ that follow! > There may be more examples of reactions, issues, findings, insights, etc. ... > e.g. pinch points, pressure points, successes, things you remember! > You may also find it useful to think about the specific idiom and wider aspects of the engagement / project. > For example, I found it helpful to think about my experiences with : > * the **idiom** itself > * the **emergency situation** in which we found ourselves - this is important context and we may have something to say about emergencies > * the **digital workplace** that we worked in - there were no labs, no lab visits, there was no `place' in RAMP and this may have had interesting effects that we can learn from > * the **design process** and how this was helped and hindered by, and adapted in light of the above > * **visualization** more generally - what did you learn about vis from this focussed experience with the selected idiom? > **This is where we really need the detailed thinking ...**
> Please spend time thinking about and discussing what you think you know, given the use of this idiom in RAMP. > > Log your thoughts here!
Add some quality and depth to the evidence base. (**Remember, this is our data**).34:[] 2f:{"title":"RAMPVIS Idiom : TEMPLATE","cells":[{"id":0,"value":"md`# RAMPVIS Idiom : TEMPLATE`","pinned":false,"hidden":false,"mode":"ojs"},{"id":290,"value":"---\n> # Introduction","pinned":false,"hidden":false,"mode":"md"},{"id":114,"value":"> ### INSTRUCTIONS\n\n> _Instructions_ for how to create the idiom from this template look like this.
\n> You'll see a set in each section.
\n> Please read through carefully and do your best to comply!\n> Start off by reading the instructions in this **Introduction**","pinned":false,"hidden":false,"mode":"md"},{"id":297,"value":"> ### PLAN\n\n> Please see the [Phil Trans A - Plan for Paper Submission](https://docs.google.com/document/d/1cefY0rA8COyM5J7d-thSn3zvgP9osj4lzJSCnqOt63U/edit#) for details on what we are trying to achieve **before you start**. Please contribute and please stick to the _plan_ and _schedule_!","pinned":false,"hidden":false,"mode":"md"},{"id":302,"value":"> ### SCHEDULE\n\n> * **02 Aug**\t\t**Idiom cut-off - NO MORE IDIOMS!** \n> * **20 Aug**\t\t**Idiom cut-off - ALL IDIOM Observable NOTEBOOKS complete!** \n\n> So log your proposed idioms in the [RAMPVIS PhilTransA IDIOMS spreadsheet](https://docs.google.com/spreadsheets/d/1X46r1SVBUhYfS1tcA7pg1yziTqU75aFKCfBMIZge0CI/edit#gid=0) before **02 August** and work on your idiom contributions until **20 August**.\n>\n> #### IMPORTANT\n>\n> It is more important that we get the _reflection_ logged early than the _JavaScript_ working, which can come later. So please can you get idiom sections completed with this priority?\n>\n> 1. **Section 7** (reflection) - by 4th August if possible\n> 1. **Sections 1 & 6** - by 6th August if possible\n> 1. **Section 4** - by 20th August\n> 1. **Sections 2, 5 & 6** (6 may depend upon 2) - by 20th August ","pinned":false,"hidden":false,"mode":"md"},{"id":308,"value":"$31","pinned":false,"hidden":false,"mode":"md"},{"id":559,"value":"> ## OBSERVABLE\n>\n> It's pretty straightforward and D3 compatible / friendly.
\n> Try this [Five-Minute Introduction\n](https://observablehq.com/@observablehq/five-minute-introduction?collection=@observablehq/notebook-fundamentals) to get started.","pinned":false,"hidden":false,"mode":"md"},{"id":573,"value":"> ## STYLING\n>\n> Use the > symbol to add _instructions_ or _comments_ in a markdown block, like this:
\n> > This is an instruction or comment in markdown:\n\n> Show or hide them with the CSS Styling of blockquote at the bottom of the page :\n> \n> display:block; - will **show** blockquote comments and instructions
\n> display:none; - will **hide** blockquote comments and instructions \n> \n> Or just toggle the **Instructions Toggler** below!\n> **block** is on, **none** is off.","pinned":false,"hidden":false,"mode":"md"},{"id":360,"value":"---\n## 1. TASK & USERS - User Story","pinned":false,"hidden":false,"mode":"md"},{"id":4,"value":"> So, _what was the problem_?
\n> _What were they doing before_?\n\n> Who were _they_?
\n> Who was this intended for - how involved were they and _were they using_ it - really?! _How?!_\n\n> These kinds of questions and some thinking around them are key to valid claims about use of visualization on applied contexts and important for supporing efforts to transfer knowledge across user, task and context.\n\n> We can capture TASK and USER quite effectively in a [User Story](https://www.gov.uk/service-manual/agile-delivery/writing-user-stories) ...\n\n> They have a common form ...\n> * As a... _**who** is the user?_\n> * I need/want/expect to ... _**what** does the user want to do?_\n> * So that ... _**why** does the user want to do this?_\n>\n> this is probably all that you need to know, but [Mountain Goat Software](https://www.mountaingoatsoftware.com/agile/user-stories) provide a few more details.","pinned":false,"hidden":false,"mode":"md"},{"id":334,"value":"> ### For example ... \n> \n> * As **an epidemiological model builder**\n> * I would like to\n * **understand the spatial and temporal patterns of commuting among different employment sectors and see how these differences vary spatially**\n> * so that I can **select appropriate spatial interaction matrices for my simulation models**\n>\n> Please be a sspecific as you can in describing tasks and users - and please check with your user friends!\n> This should involve some discussion and clarification.","pinned":false,"hidden":false,"mode":"md"},{"id":128,"value":"---\n\n## 2. DATA","pinned":false,"hidden":false,"mode":"md"},{"id":339,"value":"> _Add direct links to data files in our open source repositories - data are then accessible through the Observable Notebook._
\n> Describe data briefly - what do they capture.","pinned":false,"hidden":false,"mode":"md"},{"id":346,"value":"> ### For example ... \n\n> #### Spatial Data - for N units\n\n> Grid positions and populations for each of the spatial units:\n> * https://raw.githubusercontent.com/gicentre/scrc/main/data/grid/scotLAsGrid.csv\n\n> #### Relationship Data - for < N*N relationships\n\n> Pairs of spatial unit identifiers and any number of numeric values representing relationships between them:\n> * https://raw.githubusercontent.com/gicentre/scrc/main/data/flows/scotLAsFlows.csv","pinned":false,"hidden":false,"mode":"md"},{"id":7,"value":"---\n\n## 3. NAME - and description","pinned":false,"hidden":false,"mode":"md"},{"id":43,"value":"> Add the idiom _name_.
\n> I don't want to start with this!\n> Let's describe the **problem**, **context** and **data** that we have first, as we are mapping VIS knowledge to the domain that we are encountering and learning about.\n\n> This section should be short and generic - not about the SCRC context!","pinned":false,"hidden":false,"mode":"md"},{"id":365,"value":"> ### For example ...\n\n> OD maps are a rearrangement of the classic origin destination matrix to show the spatial variation in relationships between spatial units. Flows, correlations, proximities are examples.\n\n> In OD matrices, cells representing pairs of zones are positioned in rows according to orign and columns according destination. In OD maps, the destination cells are used to produce small maps of the destinations of each origin, with each of these destination maps placed at the origin position of a larger map. \n\n> OD maps work particularly well with regular (square) grids, and so transformation from uneven zones into a regular (square) grid may precede this process. ","pinned":false,"hidden":false,"mode":"md"},{"id":371,"value":"---\n## 4. ORIGIN & CONTEXT","pinned":false,"hidden":false,"mode":"md"},{"id":10,"value":"> Describe the source in which the idiom is presented - what is the VIS kowledge nugget that suggests that this approach might work. Where is is described, tested, evaluated, used?\n>\n> This is our **EVIDENCE BASE**\n\n> We need a primary source paper, but may need to add secondary sources for _evaluation_ and _use_.\n> Please add and describe with links - _DOIs_ or _URLs_ to papers that evidence the idiom and its likely utility.\n\n> This section may end up being part of the above, but here is where we make direct reference to the research. \n>","pinned":false,"hidden":false,"mode":"md"},{"id":376,"value":"> ### For example ...\n\n> OD Maps were introduced by [Wood et al (2010)](https://doi.org/10.1179/000870410X12658023467367) as a likely intuitive and effective spatial means of representing the geography of geographic variation.\n\n> [Yang et al (2016)](https://doi.org/10.1109/TVCG.2016.2598885) found them to be as effective, or superior to alternatives for complex map tasks in their study, in which they were deemed '_most readable_' by participants.","pinned":false,"hidden":false,"mode":"md"},{"id":13,"value":"___\n\n## 5. EXAMPLES","pinned":false,"hidden":false,"mode":"md"},{"id":383,"value":"> Add (online) examples of where the idiom has been used elsewhere with brief introductory and critical commentary.\n> \n> To be honest, this is communicative / indicative and **can come later**, even post submission!","pinned":false,"hidden":false,"mode":"md"},{"id":388,"value":"> ### For example ...\n>\n> **City Intelligence** us an OD Map to show how commuter flows vary in the burroughs of London\n * [_London Commuter Flows_](https://maps.london.gov.uk/commuter-flows/) ","pinned":false,"hidden":false,"mode":"md"},{"id":53,"value":"---\n## 6. DESCRIPTION & USE","pinned":false,"hidden":false,"mode":"md"},{"id":170,"value":"$32","pinned":false,"hidden":false,"mode":"md"},{"id":400,"value":"> ### For example ...\n>\n> We have an example in development for [OD Maps](https://observablehq.com/@jsndyks/rampvisexample_odmap)","pinned":false,"hidden":false,"mode":"md"},{"id":410,"value":"---\n## 7. REFLECTION","pinned":false,"hidden":false,"mode":"md"},{"id":90,"value":"> **The most important bit!**\n> \n> Add structured reflection here. **This is our data** for the paper.\n>\n> We will use the combined **7. REFLECTION** sections to try to synthesize some broader, high level claims from these idiom-related claims and experiences.
\n> **This is essentially the data source for the paper, so please fill it with useful information!**\n>\n> This should include learnings (_what you think you found out_) & recommendations (_what you think you would do doing forwards_) and should be based upon experience, subsequent thinking and discussion, and be based as much as possible on the **User Story**. How well was this achieved, given the way in which the idiom was applied?\n>\n> Use the notes and questions that follow to stimulate discussion.
\n> Schedule a Zoom meeting with your group to talk the idiom through and reflect on what you might have learned. **Take notes!** Summarise them and say something about how confident you are in any thoughts that you suggest. ","pinned":false,"hidden":false,"mode":"md"},{"id":419,"value":"> **Please use the following structure:**","pinned":false,"hidden":false,"mode":"md"},{"id":446,"value":"### 7.0 Reflective Discussion ","pinned":false,"hidden":false,"mode":"md"},{"id":451,"value":"$33","pinned":false,"hidden":false,"mode":"md"},{"id":415,"value":"### 7.1 What Worked","pinned":false,"hidden":false,"mode":"md"},{"id":427,"value":"> Add some things that worked, or seemed to work - **successes** - in a short section of 3-5 bullets.\n>\n> These may be positive reactions, new requirements, changing user stories (refinement), new connections.\n> What good came of the application of the idiom to this domain? ","pinned":false,"hidden":false,"mode":"md"},{"id":434,"value":"### 7.2 What Didn't Work","pinned":false,"hidden":false,"mode":"md"},{"id":438,"value":"> Add some things that didn't work well - what were the stumbling blocks, the tension points, the problems that we needed to try to overcome, or that limited success. Were they insurmountable? \n>\n> This should be another short section of 3-5 bullets based on the discussion above.\n> \n> There is plenty to learn here. Be as specific as you can, and again, relate all of this as closely to the **User Story** as you can - this is our **target / baseline**.\n","pinned":false,"hidden":false,"mode":"md"},{"id":461,"value":"### 7.3 Recommendations & Opportunities","pinned":false,"hidden":false,"mode":"md"},{"id":425,"value":"> **Given all of the above** what do we think we can claim about this idiom, not we have used it in the wild?\n>\n> Let us know what you think you know and why.\n>\n> What would (did?) you do next, given what you now know!_
\n> Where does this take us?
\n> What other VIS (and other) problems emerge from this work - what do we need to do next?
\n> Where else in the project, or other related situations might these apply?","pinned":false,"hidden":false,"mode":"md"},{"id":624,"value":"### 7.4 Who Was Involved?\n","pinned":false,"hidden":false,"mode":"md"},{"id":628,"value":"> **We need a lead for each idiom, but please get others involved in the detailed thinking ...**
\n\n> I hope that people will have discussions within and around these idiom documents, sections 7.1-7.3, **before 20th Aug** and hold meetings at which the potential reflections on and claims about the idiom are discussed. **This is the rigor in our research**.\n>\n> Please get your modelling friends involved in this activity and remember that you should list those involved in the discussions herre and in the [RAMPVIS PhilTransA IDIOMS spreadsheet](https://docs.google.com/spreadsheets/d/1X46r1SVBUhYfS1tcA7pg1yziTqU75aFKCfBMIZge0CI/edit#gid=0) ","pinned":false,"hidden":false,"mode":"md"},{"id":16,"value":"---\n\n## 8. REFERENCES","pinned":false,"hidden":false,"mode":"md"},{"id":489,"value":"> Add formal references to the literature cited here, styled as shown!
\n> Use DOIs to link, as shown. ","pinned":false,"hidden":false,"mode":"md"},{"id":27,"value":"> ### For example ...\n> \n> **Wood, J., Dykes, J., & Slingsby, A. (2010).**
\n> _Visualisation of origins, destinations and flows with OD maps._
\n> The Cartographic Journal, 47(2), 117-129.
\n> https://doi.org/10.1179/000870410X12658023467367","pinned":false,"hidden":false,"mode":"md"},{"id":484,"value":"> **Yang, Y., Dwyer, T., Goodwin, S., & Marriott, K. (2016).**
\n> _Many-to-many geographically-embedded flow visualisation: An evaluation._
\n> IEEE Transactions on Visualization and Computer Graphics, 23(1), 411-420.\n> https://doi.org/10.1109/TVCG.2016.2598885","pinned":false,"hidden":false,"mode":"md"},{"id":57,"value":"---\n### Imports","pinned":false,"hidden":false,"mode":"md"},{"id":468,"value":"> Add any imports that are required here - describe them briefly if you can.","pinned":false,"hidden":false,"mode":"md"},{"id":542,"value":"> ### For example ...\n>

import { exampleODmatrix, animTimer } from \"@jsndyks/rampvis_exampleodmatrix\"

","pinned":false,"hidden":false,"mode":"md"},{"id":549,"value":"import { exampleODmatrix, animTimer } from \"@jsndyks/rampvis_exampleodmatrix\"","pinned":false,"hidden":false,"mode":"ojs"},{"id":202,"value":"---\n\n### Styling","pinned":false,"hidden":false,"mode":"md"},{"id":474,"value":"> Show or hide instructions with the CSS Styling of blockquote as described here :\n> \n> display:block; - will **show** blockquote comments and instructions
\n> display:none; - will **hide** blockquote comments and instructions \n>\n> Or just toggle the **Instructions Toggler** below!\n> **block** is on, **none** is off.","pinned":false,"hidden":false,"mode":"md"},{"id":601,"value":"viewof instructionsOnOff = Inputs.radio([\"block\", \"none\"], {\n label: \"Instructions Toggler (on/off)\",\n value: \"block\"\n})","pinned":false,"hidden":false,"mode":"ojs"},{"id":207,"value":"","pinned":true,"hidden":false,"mode":"html"},{"id":521,"value":"> Ignore everything from here down to keep styling consistent:","pinned":false,"hidden":false,"mode":"md"},{"id":514,"value":"","pinned":false,"hidden":false,"mode":"html"}],"files":"$W34","stdlib":"1","titling":"auto"}