POPREBEL Ethnography Team Call Notes

Use this thread for notes on all POPREBEL Ethnography Team calls.

@Wojt @Jan @SZdenek we are here, sorry – the room was taken again for some reason.

Team Call 23 October 2020

Whole @rebelethno team present!

First, we discussed the new ethnographer outreach positions. We are accepting applications for all 3 platforms, and will be running initially for 3 months. Disseminate the call far and wide! Closes on the 5th of November and we will discuss candidates on the 6th of November.

Second, we did code review (thanks @SZdenek for the detailed review). @Wojt will resolve the far/extreme/radical right typology and @Jan will create a typology for forms of action/activism/direct action, which we can then co-code with political alignments, ideologies, topics etc like feminism, LGBT rights, economic reform, etc. This also means that we have emotions like apathy or emotional investment that we can co-code with political alignments/ideologies and forms of action to paint a more nuanced picture of the situation and maintain rigorous coding categories.

We will also have the Graphryder meeting to discuss:

  1. Representation of hierarchies
  2. Creating visualisations of different subforums (@alberto, on Tulip perhaps, we would love this as soon as possible to compare each subforum ssna to the connected co-occurrence network).
  3. Teaching everyone to update Graphryder.

Thanks everyone for a great meeting!

1 Like

Sure. Let’s talk early next week, so we can prepare a description of what you exactly want.

@alberto @amelia As I explained to the team today, the next three weeks will be busy for me, as the annual (online) convention of ASEEES (The Association for Slavic, East European, & Eurasian Studies) is scheduled for November 5-8 and 14-15 and I have a great fortune to be the president for this year… But I will do my best to participate in that meeting on Graphryder. I also would like to schedule a meeting with you, just to review where we are and discuss some ideas. Here I want to signal: (1) I created a continuous reporting spreadsheet to keep an eye on everybody’s progress. Edgeryders look good, but please have a look: https://liveuclac-my.sharepoint.com/:x:/g/personal/uczisgi_ucl_ac_uk/EXrITj5axcZBnFl8Q57rfK0BUFyZnMV3oja9ujhK_3KUSg?e=izFtvC. (2) Please think how you would like to present Edgeryders’s contribution to POPREBEL at a conference we will have with the two other consortia in February 2021. (3) And you may want to have a look at a preliminary report @Wojt prepared with a bit of my input. We have a way better view of what is going on in the Polish community (all threads are now coded). Ciao.


Agenda for Team Call Friday 6 November:

  1. Review of ethnographer applications and interview schedule.
  2. Update on code review process.
  3. Generate requests for @alberto re Tulip visualisations.

Call Notes Friday 6 November:

@rebelethno present (minus @Jirka_Kocian)

@alberto showed us some awesome visualisations of the subforum graphs. Now we are going to learn how to use them using Tulip! Link here:

We are going to schedule a meeting for a Tulip tutorial. Here’s the doodle poll, please fill it out!

For next meeting, we are all going to do code review. Navigate to the backend (edgeryders.eu/annotator), click on “Codes” in the sidebar, and change the drop down menu from “Tree” to “Translate” (make sure you also select “Any Creator” rather than your own name in the top bar. I recommend sorting by “Newest”

In the Translate view, add an asterisk to any codes that you think need reviewing or changing.

Add a note in the code description saying why you think it needs attention.

Then press “Save” on the right and a “Saved!” will appear in green text to show you it has saved.

When you’re done with review, make sure to also review the codes that have been asterisked by other ethnographers in case you need to edit or change them. You can do this by searching for the * in the search box.

Thanks all!


Hi @rebelethno ,

As most of you know, I’m currently recovering from COVID. I think we should still have a meeting tomorrow to check in.

Also, only @Richard and @SZdenek filled out the doodle to schedule the Tulip tutorial with @alberto, so we were unable to schedule that. Please make an effort to fill these things out. @alberto, if you’re free tomorrow during our bi-weekly, we could dedicate the time to the tutorial. Otherwise, we’ll do another doodle.

Agenda for tomorrow is either:

Tulip tutorial/workshop


  1. Update on interviews / @Wojt and @Jan update with the call I hope they’ve had with Mania, as discussed at the last meeting and in follow-up.
  2. Planning milestones and targets for the new ethnographer hires.
  3. Code review.

Thanks all!

Call Notes:

Code Review

  1. We will address and resolve all asterisked codes in the next 2 weeks.
  2. Once finished, make a post in the POPREBEL Coding Memos thread with the codes you want to discuss in the meeting.
  3. In the next bi-weekly, we will discuss all remaining asterisked codes mentioned in the memos.
  4. Especially mark any codes that are too big (eg “politics”) – we will break them up by each going through the annotations associated with them and either recoding or deleting.


  1. @Wojt and @Jan to meet with Mania asap.
  2. We will continue to interview for Czech and German ethnographers.
  3. New start date likely Jan 1st.

Tulip tutorial
I will send out a doodle for the first week of December that everyone will fill out :wink: (if @alberto confirms that he can teach us at some point that week – is that a good week for you?)

Team Call Notes 15 Jan 2020

Present: @rebelethno

We mostly discussed @Wojt and @Jan’s analysis framework:

Next steps from this meeting:

  1. For next meeting, bring a paragraph of text that you want to analyse with the group that is illustrative of any coding decisions that you are struggling with/ that is representative of the kind of analysis you want to do.
  2. We’ll decide what categories of codes we want to solidify based on this (e.g. ideology, emotions, institutions, organisations, actions, actors).
  3. Keep narrowing down the list of codes we primarily use and merging together codes that have the same or very similar meaning.

Explore abductive reasoning as an analytical frame for the analysis that we do (@Jan can post reading homework).


Coding Categories:

Institutions – the set of rules of the game. E.g. healthcare system.

  • Things can be more or less institutionalised. Or well-institutionalised (the rules work) vs badly institutionalised (lots of breakdown).
  • a social movement may work well but be less institutionalised. A healthcare system can be highly institutionalised but poorly institutionalised (has a lot of rules but it doesn’t work very well).

Organisations – places that have rules, when you walk in you have to follow them (e.g. hospital).

  • institutionalised group of actions (social movement theory)

  • usually has more resources

  • (What is the state?)

  • Border

    • not a group of people (so NOT an org), but something highly institutionalised
    • guard, and rules of engagement that if you breach things will go very badly

Actors (human) - e.g. doctors, administrators. What actors make up the organisation?
Actors (non-human) - objects that have meaning, like medicine
Scale - level of affective identifications (do I primarily see myself as a global citizen or as a Polish person, or as someone from the countryside?)

Place/location- as contextual information

Goal: break down into a smaller list of codes used more frequently that should be shared. Based upon:

  • what came before (first pass coding)
  • theoretical interests as narrowed down

Abductive Reasoning

  • Peirce
  • Read: Abductive Analysis: Theorising Qualitative Research (@alberto)
  • Collingwood: the key is the question and how you frame it

Culture both names and evaluates things

  • semiotic (meaning)
  • axiomatic (value)

Discussion about value and how to capture it:

  • via SSNA descriptive codes and what they are in a web of associations with, contextual. It’s about the story (e.g. words like fear, uncertainty, dissatisfaction co-occurring with the above categories).
  • or impose sentiment analysis layer? hot debate here.

evaluation may be implicit

  • key word: “want”

emotional “valence”

  • sliding scale colours superimposed upon codes
  • to show in forum what is mostly positive and what is mostly negative
  • sentiment analysis layer
  • how to avoid "anti "+ “not happy” codes
  • make a list of emotion codes
  • add valence to those codes (add a positive or negative value)
  • colour what it touches in the SSNA
    (but lots of disagreement here!)

@rebelethno Dear all, as we planned the call today, I would like to tell you all that our son was born a little bit ahead of plan, yesterday, early in the morning and because of this, I cannot contribute with anything new to the discussion today…I will see if I can join the call for a sec as well as about my efficiency in the weeks to come:)

However, I would also like to invite you all to our annual conference of the Malach Center for Visual History on Monday 25, which might be of some interest. Link to ZOOM and the program are here.



Congratulations! That’s great news. Have you decided on a Czech-Chilean name yet?

1 Like

Leonardo Antonio Kocián Davis


Do we need a link for today’s call?


I’m sorry guys, I couldn’t and thus didn’t make it to today’s meeting. Family matters.
Are there any minutes from it?


<3 Congraaaattssss, very happy for you!

Thank you so much!

1 Like

Hi @rebelethno !
Since we now have been OKed to introduce hierarchies into our backend we would like to suggest a meeting this Friday (February 5th) to go through our spreadheet, compress and refine what we can, and introduce the hierarchies we agree on into the backend.
What say you?

If you can make it, please make sure to go through the document and read the comments so that we don’t have to do all this when we meet, ok?

Hello, unfortunately, I am still off my usual tempo, I could not make any contribution for tomorrow - I will catch up next week and do what is due

I can’t make it today (I’m doing a mock viva!) but I support your efforts and look forward to contributing at our bi weekly next week :slight_smile:

@SZdenek @Wojt looks like it is just the three of us:https://rutgers.zoom.us/j/94640481106?pwd=a0Z3SGJIT1JhVjhtckI1QUpFMkpMUT09