Clarify Enter vs Return; demonstrate edit functionality in text facet

[Talishask]

I'm a member of The Carpentries staff and I'm submitting this issue on behalf of another member of the community. In most cases, I won't be able to follow up or provide more details other than what I'm providing below.

---

I would like to make a few suggestions to an existing lesson as part of my checkout process. The suggestions are rather small but something to consider potentially.

1. Replace the use of "hit return" to either "hit enter" or "hit return/enter" the use of this key varies by computer mac/pc but could be confusing to users who do not have a return key.

2. Facet edit https://datacarpentry.org/openrefine-socialsci/02-working-with-openrefine/index.html

Here we will use faceting to look for potential errors in data entry in the village column.

3. Scroll over to the village column.
4. Click the down arrow and choose Facet > Text facet.
5. In the left panel, you'll now see a box containing every unique value in the village column along with a number representing how many times that value occurs in the column.
6. Try sorting this facet by name and by count. Do you notice any problems with the data? What are they?
7. Hover the mouse over one of the names in the Facet list. You should see that you have an edit function available.
8. You could use this to fix an error immediately, and OpenRefine will ask whether you want to make the same correction to every value it finds like that one. But OpenRefine offers even better ways to find and fix these errors, which we'll use instead. We'll learn about these when we talk about clustering.

My suggestion would be to show learners how to make an edit here as well as "the even better way". Simply correcting one of the spelling errors in the variable list would add maybe 10 seconds to the lesson and provide additional context.

[bencomp]

These are good suggestions.

To the first point: the lesson style guide says

We use “Return” instead of “Enter”.

However, since OpenRefine uses "Enter" in many places within the user interface, I agree that this could be confusing. Would adding a note in the Introduction be good enough?

To the second point: I agree that explaining how you could do something, but then not doing it, may be confusing. We should make sure that any edit here does not make the clustering exercise superfluous.

Note: I found that OpenRefine does record changing values from a facet as "mass-editing cells" in the history, whereas it doesn't when you change a single value in a cell.

[bencomp]

Regarding demonstrating changing a value in the text facet: it helps to have a messier dataset, so that we can demonstrate this for one value, and use clustering to fix the others. See #108 for suggestions to make the dataset messier.