# \#roadmap

**URL:** https://forum.openrefine.org/tag/roadmap/2.md

[Latest](https://forum.openrefine.org/latest.md) · [Categories](https://forum.openrefine.org/categories.md) · [Tags](https://forum.openrefine.org/tags.md)

---

## [OpenRefine 2024 Barcamp: Strategizing OpenRefine Roadmap](https://forum.openrefine.org/t/openrefine-2024-barcamp-strategizing-openrefine-roadmap/1633)

<div class="topic-metadata">

**Author:** [@Martin](https://forum.openrefine.org/u/Martin)\
**Replies:** 5\
**Last updated:** [April 1, 2025, 6:02pm UTC](https://forum.openrefine.org/t/openrefine-2024-barcamp-strategizing-openrefine-roadmap/1633 "2025-04-01T18:02:30Z")

</div>

This session (see Barcamp page) was highly productive, and help us strategize how we can continue the work on the different topic discussed during the Barcamp. We proposed using high-level epics or goalposts to effective…

---

## [User Interviews Results Part 2: Exploring Feedback Regarding OpenRefine Feature and User Experience](https://forum.openrefine.org/t/user-interviews-results-part-2-exploring-feedback-regarding-openrefine-feature-and-user-experience/1181)

<div class="topic-metadata">

**Author:** [@Martin](https://forum.openrefine.org/u/Martin)\
**Replies:** 0\
**Last updated:** [January 11, 2024, 7:55pm UTC](https://forum.openrefine.org/t/user-interviews-results-part-2-exploring-feedback-regarding-openrefine-feature-and-user-experience/1181 "2024-01-11T19:55:52Z")

</div>

This post explores suggestions I collected through the user and contributor interviews I did in 2023. This is the second post of a series of three. The first message focused on governance and is available here Propositio…

---

## [Results from the Feature Prioritization Survey 2024](https://forum.openrefine.org/t/results-from-the-feature-prioritization-survey-2024/1847)

<div class="topic-metadata">

**Author:** [@Martin](https://forum.openrefine.org/u/Martin)\
**Replies:** 5\
**Last updated:** [November 12, 2024, 12:59pm UTC](https://forum.openrefine.org/t/results-from-the-feature-prioritization-survey-2024/1847 "2024-11-12T12:59:25Z")

</div>

Presentation This post focuses on the results of the feature voting done along with the survey using the all-our-ideas platform. The vote took place between August 1, 2024, and October 7th, 2024 and out of the 226 survey…

---

## [Prioritisation of Wikimedia Sverige's development work](https://forum.openrefine.org/t/prioritisation-of-wikimedia-sveriges-development-work/1803)

<div class="topic-metadata">

**Author:** [@Sebastian](https://forum.openrefine.org/u/Sebastian)\
**Replies:** 7\
**Last updated:** [October 15, 2024, 8:07am UTC](https://forum.openrefine.org/t/prioritisation-of-wikimedia-sveriges-development-work/1803 "2024-10-15T08:07:31Z")

</div>

We, @Andre\_Costa, @Alicia\_Fagerving and myself, have done some planning for Wikimedia Sverige's development work on OperRefine. We had a look at the open issues on Github and some other places where bugs and feature requ…

---

## [OpenRefine support for Lexemes in Wikidata: how would you use this?](https://forum.openrefine.org/t/openrefine-support-for-lexemes-in-wikidata-how-would-you-use-this/216)

<div class="topic-metadata">

**Author:** [@Sandra](https://forum.openrefine.org/u/Sandra)\
**Replies:** 12\
**Last updated:** [October 15, 2024, 6:17am UTC](https://forum.openrefine.org/t/openrefine-support-for-lexemes-in-wikidata-how-would-you-use-this/216 "2024-10-15T06:17:53Z")

</div>

At this moment, OpenRefine doesn’t yet support creating or editing Wikidata Lexemes (Lexicographical data). This has been a long-term request from the Wikidata community though: Support Wikidata lexemes · Issue #2240 · O…

---

## [Open source onboarding libraries](https://forum.openrefine.org/t/open-source-onboarding-libraries/1124)

<div class="topic-metadata">

**Author:** [@thadguidry](https://forum.openrefine.org/u/thadguidry)\
**Replies:** 2\
**Last updated:** [September 11, 2024, 7:33pm UTC](https://forum.openrefine.org/t/open-source-onboarding-libraries/1124 "2024-09-11T19:33:13Z")

</div>

I wanted to give my quick evaluation on onboarding libraries and how we might use them in OpenRefine to address the need for better user guiding of features, in app help, and onboarding such as mentioned in another comme…

---

## [OpenRefine 2032 ... what direction does OpenRefine want to go?](https://forum.openrefine.org/t/openrefine-2032-what-direction-does-openrefine-want-to-go/272)

<div class="topic-metadata">

**Author:** [@Sandra](https://forum.openrefine.org/u/Sandra)\
**Replies:** 9\
**Last updated:** [October 21, 2023, 10:11am UTC](https://forum.openrefine.org/t/openrefine-2032-what-direction-does-openrefine-want-to-go/272 "2023-10-21T10:11:51Z")

</div>

Which kind of work, which features, which direction will OpenRefine prioritize, going forward? Which use cases and communities will the tool serve in the next 10 years? I’ll be bold… I want to propose an OpenRefine stra…

---

## [Hosted uses of OpenRefine](https://forum.openrefine.org/t/hosted-uses-of-openrefine/909)

<div class="topic-metadata">

**Author:** [@antonin\_d](https://forum.openrefine.org/u/antonin_d)\
**Replies:** 7\
**Last updated:** [October 9, 2023, 8:38pm UTC](https://forum.openrefine.org/t/hosted-uses-of-openrefine/909 "2023-10-09T20:38:39Z")

</div>

OpenRefine is designed to run on a local machine and our documentation about running it as a remote server features some prominent warnings: At the moment I see: quite some interest from users in hosted versions: for…

---

## [A new start for the 4.0 architecture](https://forum.openrefine.org/t/a-new-start-for-the-4-0-architecture/51)

<div class="topic-metadata">

**Author:** [@antonin\_d](https://forum.openrefine.org/u/antonin_d)\
**Replies:** 0\
**Last updated:** [November 2, 2022, 1:11pm UTC](https://forum.openrefine.org/t/a-new-start-for-the-4-0-architecture/51 "2022-11-02T13:11:36Z")

</div>

Hi all! It’s November already! And that means the WMF sponsored project to develop integration with Wikimedia Commons is over. I was initially not supposed to be actively developing for it, but things turned out differe…
