LibraryCarpentry / lc-open-refine

Library Carpentry: OpenRefine
https://librarycarpentry.org/lc-open-refine/
Other
52 stars 133 forks source link

Using examples in scripts other than Latin #241

Open addedcopy opened 2 years ago

addedcopy commented 2 years ago

Libraries catalogue items in many different scripts. It would be good to see data in spreadsheets represented in those scripts in order to demonstrate how they survive (or not) various operations with data. In particular, it would be interesting to see how diacritics and ligatures in the Library of Congress transliteration will be reflected in OpenRefine. This can be very useful when using OpenRefine in reconciliation services (for example, using WorldCat data for WikiData).

emcaulay commented 2 years ago

Excellent recommendation. I can agree that the problem of moving non-ASCII characters in and out of different applications is always something that needs instruction and attention.

jas58 commented 2 years ago

Thank you for proposing a way to bring criticality into the lesson, @addedcopy. Forgive my tardy response as the fall term crashed upon me.

May I explore several follow up questions with you and @emcaulay? Given the upcoming (next year or so) changes to how lessons will appear ([Workbench] (https://carpentries.org/blog/2022/01/live-lesson-infrastructure/)), would you propose a sentence or paragraph for the instructor notes (which will be embedded at this point in the lesson)? There also doesn't seem to be room in the lesson (time or metacognitive load-wise) for another episode.

  1. Create two lists.

If it is an instructor note, might it mention the strength of MarcEdit to work with the mislabeled or mixed encoded files of MARC8?

You mention WorldCat or Wikidata; can you highlight a specific non-UTF-8 file?

We look forward to this discussion.

jas58 commented 1 year ago

@addedcopy @emcaulay Happy New Year! We are trying to wrap up 2022's outstanding issues. Would either of you have time in the next 60 days to clarify your requests for us?

jas58 commented 10 months ago

Hi Lisa and Cody! I learned how to search open issues by date!
updated:>=2013-02-01

I saw your handle, @emcaulay , and wondered if this issue would be worth organizing a Discussion session in Q2 or mentioning at an upcoming Maintainer meeting?

Or should I check with Cody @chennesy : Is this enhancement achievable this year or part of any discussions in the wider curriculum?

chennesy commented 10 months ago

Thanks Jennifer! I don't think CAC would need to weigh in on this, even though it would involve a small update to the dataset. But if the OR team have time/interest in this enhancement, it would be a great task to take on. I don't see that it fits into any broader updates being planned necessarily... I'd be happy to beta-test something though, it you set it up!

Cody

On Fri, Dec 15, 2023 at 9:40 AM Jennifer Stubbs @.***> wrote:

Hi Lisa and Cody! I learned how to search open issues by date! updated:>=2013-02-01

I saw your handle, @emcaulay https://github.com/emcaulay , and wondered if this issue would be worth organizing a Discussion session in Q2 or mentioning at an upcoming Maintainer meeting?

Or should I check with Cody @chennesy https://github.com/chennesy : Is this enhancement achievable this year or part of any discussions in the wider curriculum?

— Reply to this email directly, view it on GitHub https://github.com/LibraryCarpentry/lc-open-refine/issues/241#issuecomment-1858078806, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANCQPHDPWHOU4FWLQQFGZ3YJRVNPAVCNFSM56246IF2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBVHAYDOOBYGA3A . You are receiving this because you were mentioned.Message ID: @.***>

-- Cody Hennesy (he/him) Computational Research Librarian / Interim Journalism Librarian University of Minnesota Libraries @.***