-
Notifications
You must be signed in to change notification settings - Fork 113
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #303 from OpenRefine/website_restructure
#291 update header and footer, update community page, add ecosystem, usage and history page
- Loading branch information
Showing
17 changed files
with
223 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
--- | ||
title: OpenRefine Ecosystem | ||
description: OpenRefine Ecosystem | ||
hide_table_of_contents: true | ||
--- | ||
# OpenRefine Ecosystem | ||
|
||
The OpenRefine ecosystem comprises the OpenRefine project, which maintains the [OpenRefine software](https://github.com/OpenRefine/openrefine), [user forums](https://forum.openrefine.org/), [documentation](/docs) and [translation](/docs/technical-reference/translating-ui), and user groups that contextualize OpenRefine for their communities' usage. | ||
|
||
Those user groups include data journalists, semantic web enthusiasts, Galleries, Libraries, Archives, Museums (GLAM), researchers, or members of the Wikimedia Movement. Each community provides advocacy, training, and support activities via mediums relevant to its members, with little coordination between them. For instance, libraries host training sessions for archivists, librarians, and researchers; workshops are organized during data journalism conferences; and a dedicated Telegram channel is available for Wikimedians seeking support. | ||
|
||
Third-party developers create [extensions](/extensions) and [reconciliation services](/extensions#reconciliation-services) compatible with OpenRefine. Reconciliation services allow users to link their datasets with a external data sources, while extensions add domain-specific features or integrate OpenRefine into a particular workflow. These services expand OpenRefine's capabilities, enabling users to accomplish their tasks more efficiently. | ||
|
||
Finally, the Advisory Committee is responsible for OpenRefine funding and administrative tasks to support the ecosystem. It coordinates with [Code for Science and Society](https://www.codeforsociety.org/), our fiscal host, and OpenRefine [funders](/funding). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
--- | ||
title: OpenRefine Project History | ||
description: A brief overview of OpenRefine History | ||
hide_table_of_contents: false | ||
--- | ||
# OpenRefine History | ||
|
||
Over the last ten years, OpenRefine has undergone significant transformations, including changes in its name and development model. It has transitioned from an enterprise-led open source model to a community-based open source model, with later support from occasional grants. | ||
|
||
```mermaid | ||
%%{init: { 'theme': 'forest', 'timeline': {'disableMulticolor': true}}}%% | ||
timeline | ||
title OpenRefine timeline | ||
. : Project Name | ||
: Main Release | ||
: Development Model | ||
2008 - 2010 : Freebase Gridworks | ||
: Version 1.0 | ||
: Lead by Metaweb Technologies, Inc. with open source contributors | ||
2010 - 2012 : Google Refine | ||
: Version 2.0 and 2.5 | ||
: Lead by Google with open source contributors | ||
2012 - 2018 : OpenRefine | ||
: Version 2.6 | ||
: Solely with volunteer open source contributors | ||
2018 - 2019 : OpenRefine | ||
: Version 3.0 | ||
: First grants with Google News Initiatives and CZI with open source contributors | ||
2020 - Today : OpenRefine | ||
: Version 3.3+ | ||
: Grant based model with CS&S as fiscal sponsor with open source contributors | ||
``` | ||
|
||
## 2008 - 2010: Freebase Gridworks | ||
<img src="/img/logo/freebase.png" alt="Freebase Gridworks" height="50"/> | ||
The history of OpenRefine dates back to May 2010, when Metaweb Technologies, Inc. initiated the development of an open-source data cleansing tool named Freebase Gridworks. Freebase Gridworks, conceived by David Huynh, simplified data cleaning and transformation data to import into Freebase, a large collaborative knowledge base built by Metaweb. Freebase Gridworks offered a user interface for editing and reconciling large datasets. | ||
|
||
## 2010 - 2012: Google Refine | ||
<img src="/img/logo/google-refine.png" alt="Google Refine" height="50"/> | ||
In July 2010, Google acquired Metaweb Technologies and with it, Freebase Gridworks. Following this acquisition, the tool was renamed "Google Refine". Under Google's stewardship, Google Refine 2.0 was released, featuring enhanced data cleaning capabilities. This version established the tool's reputation for handling various data-related tasks, such as cleaning messy data, transforming data formats, and extending data sets with web services. | ||
|
||
## 2012 - 2019: OpenRefine | ||
<img src="/img/logo/open-refine.png" alt="OpenRefine" height="50"/> | ||
In 2012, Google transferred leadership of the project to the open source community, who renamed it "OpenRefine" and moved it to GitHub. The following years saw OpenRefine continuing to gain a diverse user base, including scientists and researchers, journalists, semantic web practitioners, librarians, and cultural heritage specialists. | ||
|
||
In 2017, OpenRefine began integrating with Wikidata thanks to the availability of a reconciliation endpoint and a process to publish data to the Wikimedia project. | ||
|
||
In December 2018, Google News Initiative donated $100,000 to support OpenRefine development. The same year the project's logo was updated. | ||
|
||
## 2019 - today: OpenRefine, part of Code for Science & Society | ||
<img src="/img/logo/OpenRefine.png" alt="OpenRefine" height="50"/> | ||
|
||
In the following years, OpenRefine confirmed its grant-based sustainability model by receiving recurring funding from the Chang Zuckerberg Initiative, the Wikimedia Foundation, and NFDI. To help manage funds, OpenRefine became a fiscally sponsored project of Code for Science and Society (CS&S), a 501(c)(3) charitable organization in the USA, in 2020. | ||
|
||
During that time, OpenRefine experienced tremendous growth by doubling the number of active contributors (both paid and volunteers), increasing the number of translated languages, adding native integration with Wikimedia Commons and Wikibase, and seeing more users rely on it. The project also became more organized with the creation of an Advisory Committee and participation in internship programs like Google Summer of Code and Outreachy. |
Oops, something went wrong.