OpenRefine lesson updates #3205
Conversation
I went through the tutorial and fixed a few inconsistencies I found.
wetneb
force-pushed
the
openrefine_lesson_updates
branch
from
17c8a0c
to
a2fdd6f
Compare
| meaning to *OpenRefine*. Additionally, select the 'Parse cell text into | ||
| numbers, dates, ...' checkbox to let OpenRefine automatically detect | ||
| meaning to *OpenRefine*. Additionally, select the 'Attempt to parse cell | ||
| text into numbers' checkbox to let OpenRefine automatically detect |
There was a problem hiding this comment.
This reflects an update that we made in the tool, changing the name of this option to match its actual behavior (it doesn't actually parse dates).
| @@ -292,7 +292,7 @@ cells**, **Join multi-valued cells**, **OK**. Choose the pipe character (|) as a | |||
| separator. The rows now look like before, with a multi-valued Categories | |||
| field. | |||
|
|
|||
| ### Applying ad-hoc transformations through the use of regular expressions | |||
| ### Applying ad-hoc transformations through the use of GREL expressions | |||
There was a problem hiding this comment.
This section does not use regular expressions at all, only GREL expressions, so I think it's worth avoiding this confusion.
| @@ -379,7 +379,7 @@ Once your data has been cleaned, you can take the next step and explore | |||
| other exciting features of *OpenRefine*. The user community of | |||
| *OpenRefine* has developed two particularly interesting extensions which | |||
| allow you to link your data to data that has already been published on | |||
| the Web. The [RDF Refine extension][] transforms plaintext keywords into | |||
| the Web. The [RDF Transform extension][] transforms plaintext keywords into | |||
There was a problem hiding this comment.
The RDF Transform is the successor of this extension. It should work with recent versions of OpenRefine.
|
Hello Antonin Delpeuch @wetneb. Many thanks for making contact, and offering to support an update of the lesson cleaning-data-with-openrefine and its subsequent translations. We actually prefer outside contributors not to create direct Pull Requests from their forks of our repo. Updates to our site are so regular that knots in forks are very frequent. I'll transfer this to an Issue, create a branch on our side and replicate the changes you suggest. I'll then seek the support of our ES and PT teams to update their translations, and ask our Managing Editors to review and approve these changes. Thank you for sharing your expertise ✨ |
Hello, thank you so much for maintaining this fantastic OpenRefine lesson, which is still a reference.
I went through the tutorial and fixed a few inconsistencies I found, mostly updating for changes that we have made in OpenRefine itself.
I haven't touched the Spanish and Portuguese translations because I don't master those languages but I could update the links already if that's welcome.
Checklist
Closes #ISSUENUMBERto your summary above