We are thrilled to share with you some updates from our end, new and exciting developments that have been happening with the community in September, the buzz around the new online OpenRefine Foundation course.
Did you took a break from OpenRefine in August, fear of missing something? No worries, the August update got you covered.
It is time to look back at developments who happened in the community through July. Plenty of new tutorials in English, French, German and Czech, and an update on progress on the 2.6 release.
Read below if you what happenned within OpenRefine community in June
OpenRefine offers an innovative workflow from data ingestion to consumption, with a capacity to reconcile information consistency and work with remote data processing services. It integrates with over 16 reconciliation services and has 8 community contributed plugins that extend its capability. You can interact directly with the API of 4 other platforms within the context of tasks in OpenRefine alchemyAPI, Zemanta, dataTXT and Crowdflower. The following map lists the different services and plugins working with OpenRefine, as well as projects that have done heavy customization to add OpenRefine in their data manipulation processes.
Following the 2012 survey which gather 99 answers, I wanted to have a fresh picture on who are OpenRefine users. The 2014 survey received 129 answers on the span of two weeks. The goal of this second survey was to understand who is OpenRefine audience and what are they relationship with the official community tools (mailing list and Github issue trackers.)
From its inception until October 2012 Refine development was driven mainly by corporations. Metaweb and Google have committed resources to support and grow Refine for more than two years until Google Refine 2.5 release. With the end of Google support 18 months ago, OpenRefine is working as an indepedant community, relying only on volunteer to maintain the code and support user and contributors.
In Fall 2012, I wrote an article on the history of OpenRefine and the need to build a framework for the community. At this time the discussion was focused more on the technical aspect to structure the community (ie moving the code base and documentation to Github) and less on defining a way to work together.
“How do I get started?” is the question we received most during our hands-on workshops on data cleaning and enhancing. OpenRefine is a very powerful tool in the hands of a skilled user, but how do you become one?
Yesterday David Huynh announced that Google will soon stop its active support of Google Refine and count of community to get more involved to growth Refine.
Refine is already a mature data cleaning tool, this change in leadership will be a major challenge for the tool continuity. But first I'd like to clarify what I have read on twitter yesterday night. Google Refine has always been an open source tool and anyone can commit changes, develop an extension or update the wiki.
Through this post I'd like to give my insight on the reason of this decision and what will be the short terms consequences of it.