Wikidata:Edit groups/OR/44452d5b0f4
< Wikidata:Edit groups | OR
Edit group OR/44452d5b0f4
Summary | Meetjeslandse Meesters | Author | Geertivp |
---|---|---|---|
Number of edits | 89 (more statistics) | Example edit | Q107171419 |
Discussion
[edit]@Geertivp: The precision of the dates seems to be off with this one. I just checked a few items, but they have a similar pattern: Instead of year precision, they have date precision with the date set to 1 January. Could you inspect and correct them? Thank you! --Emu (talk) 11:57, 26 June 2021 (UTC)
- Thanks for your remark, Emu. Exactly; apparently with OpenRefine it seems not possible to indicate the precision? Do you possibly know how to do this with OpenRefine? I would love to do it right! Geertivp (talk) 07:36, 27 June 2021 (UTC)
- @Geertivp: It has always worked for me automatically in OpenRefine – did you use normal text fields with 2000, 2000-01 or 2000-01-01 respectively? --Emu (talk) 10:42, 27 June 2021 (UTC)
- I had a problem to recognize 2000 as a year; as a workaround I converted it textually into 2000-01-01. I understand that there should be a better solution. Please let me know a way to handle this properly in the future. It should be possible to recognize and store "2000" as a year using OpenRefine... Thanks. Geertivp (talk) 11:34, 27 June 2021 (UTC)
- @Geertivp: Strange, 2000 works perfect for me if used with a text datatype in OpenRefine.
- Will you correct the existing items? --Emu (talk) 13:41, 27 June 2021 (UTC)
- I believe I have corrected all erroneous 1 January dates. Next time I will search how I can properly store the years with OpenRefine. Thanks for reminding me. Geertivp (talk) 19:07, 27 June 2021 (UTC)
- Thanks! :-) --Emu (talk) 19:20, 27 June 2021 (UTC)
- I believe I have corrected all erroneous 1 January dates. Next time I will search how I can properly store the years with OpenRefine. Thanks for reminding me. Geertivp (talk) 19:07, 27 June 2021 (UTC)
- I had a problem to recognize 2000 as a year; as a workaround I converted it textually into 2000-01-01. I understand that there should be a better solution. Please let me know a way to handle this properly in the future. It should be possible to recognize and store "2000" as a year using OpenRefine... Thanks. Geertivp (talk) 11:34, 27 June 2021 (UTC)
- @Geertivp: It has always worked for me automatically in OpenRefine – did you use normal text fields with 2000, 2000-01 or 2000-01-01 respectively? --Emu (talk) 10:42, 27 June 2021 (UTC)