-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wrong dates! #75
Comments
his could be related to the native JS date object which is used for display. I will check that, too. |
maybe it is because months indexes are 0 based. And there is no month here: -1 => November of the previous year. |
yeah it seems like it is rounding with -1 to previous year! But what puzzles me is that it does not do the same thing for all dates which have just year precision!!!!! |
does it depend on the browser? we had some problems with Safari. |
I am using chrome |
@tobiasschweizer It is browser based!!! in Safari date is right!!!!! |
Could you please make an issue in Knora-UI and assign it to @flavens, referring to this issue? I bet it is a problem with the constructor of the date object. |
the component in questions is: kui-date-value (viewer module) |
@andreas-aeschlimann suspsects that it could also be a time zone related problem. |
Commented in the other thread @tobiasschweizer. |
Date presentations in BEOL are incorrect for some of the resources. For resource which has
"knora-api:dateValueHasCalendar": "GREGORIAN",
"knora-api:dateValueHasEndEra": "CE",
"knora-api:dateValueHasEndYear": 1786,
"knora-api:dateValueHasStartEra": "CE",
"knora-api:dateValueHasStartYear": 1786,
"knora-api:hasPermissions": "CR knora-base:Creator|M knora-base:ProjectMember|V knora-base:KnownUser|RV knora-base:UnknownUser",
"knora-api:valueAsString": "GREGORIAN:1786 CE"
Date is correct in triplestore and knora returns correct date value.
But in GUI the shown date is 1785 CE!!
In the new data please check the resource
http:%2F%2Frdfh.ch%2F0801%2F0TRvVX9kSyabvaD5J1_7tQ
Since the problem is not true for all resources this sounds really fishy!
The text was updated successfully, but these errors were encountered: