thiemowmde added a comment.
Here is a query to try the effect of this change: https://query.wikidata.org/#SELECT%20%3Fitem%20%3Ftime%7B%0A%3Fitem%20wdt%3AP31%20wd%3AQ36507.%0A%3Fitem%20wdt%3AP585%20%3Ftime%0A%7D%0AORDER%20BY%20%3Ftime%0ALIMIT%2020 It should now find Items with both Julian and
gerritbot added a comment.
Change 313984 merged by jenkins-bot:
Skip Julian to Gregorian date conversion for extreme, unsupported dates
https://gerrit.wikimedia.org/r/313984TASK DETAILhttps://phabricator.wikimedia.org/T146356EMAIL
gerritbot added a comment.
Change 312215 merged by jenkins-bot:
Fix (Julian)DateTimeValueCleaner for extreme years
https://gerrit.wikimedia.org/r/312215TASK DETAILhttps://phabricator.wikimedia.org/T146356EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
gerritbot added a comment.
Change 313984 had a related patch set uploaded (by Thiemo Mättig (WMDE)):
Add extreme Julian date test to TimeRdfBuilderTest
https://gerrit.wikimedia.org/r/313984TASK DETAILhttps://phabricator.wikimedia.org/T146356EMAIL
gerritbot added a comment.
Change 312214 merged by jenkins-bot:
Cleanup DateTimeValueCleanerTest
https://gerrit.wikimedia.org/r/312214TASK DETAILhttps://phabricator.wikimedia.org/T146356EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: thiemowmde, gerritbotCc:
Smalyshev added a comment.
Perhaps leave it for the data consumer to figure out for him/her/itself that May 4th in 20BC is silly
It is an option, and here we have a tradeoff, of either:
A. Try to represent the wrong data in a way that they would be useful, preserving the useful part and
Jc3s5h added a comment.
In T146356#2663757, @Smalyshev wrote:
I think this idea makes a lot of sense. While I think all far-ago dates that have day precision are most probably data errors (you can't have May 4th in 20BC, really, at least not using Earthly calendars :) handling these errors in
Smalyshev added a comment.
I think this idea makes a lot of sense. While I think all far-ago dates that have day precision are most probably data errors (you can't have May 4th in 20BC, really, at least not using Earthly calendars :) handling these errors in more sane manner is good. However,
gerritbot added a comment.
Change 312215 had a related patch set uploaded (by Thiemo Mättig (WMDE)):
Fix (Julian)DateTimeValueCleaner for extreme years
https://gerrit.wikimedia.org/r/312215TASK DETAILhttps://phabricator.wikimedia.org/T146356EMAIL
gerritbot added a comment.
Change 312214 had a related patch set uploaded (by Thiemo Mättig (WMDE)):
Cleanup DateTimeValueCleanerTest
https://gerrit.wikimedia.org/r/312214TASK DETAILhttps://phabricator.wikimedia.org/T146356EMAIL
10 matches
Mail list logo
