What's this? Open Ethnographer is a software to add ethnographic coding right into live online content. It is an open source plug-in for Drupal, and we use it to add semantic markup to edgeryders.eu content, empowering both our ethnographic research, website visitor's navigation and discovery, and semantic search engines. Open Ethnographer is developed by the Edgeryders LbG company, with the support of the Rockefeller Foundation.

What's innovative? In contrast to existing QDA software, semantic markup ("coding") is not inserted into an offline copy of the online conversation, but right into the live content. This preserves the context, enabling extended analysis later. In addition, the semantic markup can be created collaboratively, the saved coding effort allowing more detailed research later. Lastly, the semantic markup can be public, enhancing the original author's content with semantic web integration "for free". We believe this innovation to have potentially disruptive applications for how ethnography is done and what role it plays in societal advancement – see also our more detailed explanation.

This project is open! Which means, you are invited to browse through our project workspace below, contribute to the discussion, to software development, and of course to using the free and open source software application when it's ready (about end of 2015-01). The Antiheroes project is already interested to use Open Ethnographer as well. Core documents and tools for collaborating here:

like5

Heads up: new Ethnographer role, content managers and site admins can no longer see and add annotations

Alberto's picture

OpenEthnographer introduces a long delay in loading pages (only for users with the relevant privileges). While we wait for a more permanent solution, we have adopted a workaround. Its implications are that users with content manager and site admin privileges can no longer see or create OE annotations, and can not see the OE sidebar. 

Where are the coding data in Open Ethnographer saved?

Alberto's picture

I am sketching a data management plan for OpenCare and need to know where we store the coding data. I know they are no longer stored in the full text field. Is it in some taxonomy term table in the database? @danohu, you would know the answer to this...

Also: I seem to remember we were using RDFa standard in the first version. Is this true of the current version too? Does this mean codes have URIs? 

OE still on track -- taking advantage of Opencare H2020

@Alberto @Matthias @noemi @inga

Hi all, I am browsing OE posts to figure out the state of things on OE. We have scheduled tasks aiming at possible improvements to OE in the context of OpenCare. I understand there has been lots of work done. I am just curious to hear OE users, to get a sense of possible improvements and/or changes.

Can networked communities steward public assets at scale?

Nadia's picture

This is the question we set out to answer through our conversations with one another before, during and after LOTE4. After months of developing the Open Ethnographer software to help us go through all the content and identify patterns in it, producing a first ethnographic report, running it through another round of analysis and synthesis, and producing a visualisation of the conversation.... this is what we came with:

Implement storing annotations relative to content, not content display

I've got annotator/annotation set up, and I like it.w

I think we need to modify it, though, to make sure that annotations are stored relative to the content we are annotating, not the details of how it is presented on the ER website.

Currently, you annotate anything on the page, regardless of what node/field it is. The data stored looks like:

Check this thing out

I think you should check out Metamaps. I like the way they present the project, and invite others to use and develop the software.

Also, I think they get some stuff right about the tagging, visual tagging (some symbols) for community use in addition to just text.

Maybe something to learn from for how we present edgesense and OpenEthnographer as products?

I'd also like to know how we can ensure that we are differentiated from what they are doing or develop some difference.

Install Annotator into edgeryders.eu and document how to do it

We want to base Open Ethnographer on Annotator (not on eComma any more, @Matthias is sorry for the mess … but eComma was not a good fit after all). So the task is here to install the existing Drupal integration modules annotator (frontend) and annotation (backend storage) on edgeryders.eu. Not on the live site directly of course, but on a local copy or on dev.edgeryders.eu.

Add config options to hide parts of the eComma UI

Open Ethnographer will use eComma as its base, but does not need (or: want) to show all features of its user interface since the purpose is different. So the task is here to add configuration options allowing to hide the word cloud, comments and comments word cloud tabs (first, third and fourth tab currently). While we're at it, options to hide all tabs that can meaningfully be hidden should be added.

This is a paid task and welcome to be picked up by Edgeryders community members!

Heads up: new Ethnographer role, content managers and site admins can no longer see and add annotations

Alberto's picture

OpenEthnographer introduces a long delay in loading pages (only for users with the relevant privileges). While we wait for a more permanent solution, we have adopted a workaround. Its implications are that users with content manager and site admin privileges can no longer see or create OE annotations, and can not see the OE sidebar. 

Where are the coding data in Open Ethnographer saved?

Alberto's picture

I am sketching a data management plan for OpenCare and need to know where we store the coding data. I know they are no longer stored in the full text field. Is it in some taxonomy term table in the database? @danohu, you would know the answer to this...

Also: I seem to remember we were using RDFa standard in the first version. Is this true of the current version too? Does this mean codes have URIs? 

OE still on track -- taking advantage of Opencare H2020

@Alberto @Matthias @noemi @inga

Hi all, I am browsing OE posts to figure out the state of things on OE. We have scheduled tasks aiming at possible improvements to OE in the context of OpenCare. I understand there has been lots of work done. I am just curious to hear OE users, to get a sense of possible improvements and/or changes.

Can networked communities steward public assets at scale?

Nadia's picture

This is the question we set out to answer through our conversations with one another before, during and after LOTE4. After months of developing the Open Ethnographer software to help us go through all the content and identify patterns in it, producing a first ethnographic report, running it through another round of analysis and synthesis, and producing a visualisation of the conversation.... this is what we came with:

OE user feedback

- Intuitive and easy to use

- I've spent twice less time using OE, than coding manually for STF. Time efficient! :)

- Drop-down menu is great

- For some reason, about 10% tags did not export to .rqda file. It didn't skew the results too much (as I remembered +/- where those tags were in original text online), but it made it harder to find and refer to the original quotes. 

No documents have been added to this group.

Deliverables: Narrative Reports (Interim and Final)

As part of the grant agreement the Rockefeller Foundation for OpenEthnographer we are producing two reports. The ambition is to use the opportunity afforded by the grant to produce a high-quality synthesis that is useful to everyone who participated in the conversation leading to, during and in the aftermath of LOTE4. As well as anyone wishing to learn from them.

Narrative Report #1: DEADLINE JAN 20

Executive summary

[add here]

Notes for testing

It's useful, as we implement OpenEthnographer, to collect notes on what needs to be tested. This helps to:

  • Remind developers what needs to work
  • Show us where we can use automated tests
  • Guide manual testing, during the test phase

 

Recent activity in this group

Group contributors

Organizers

Contributors