search

oskariorg / oskari-docs

Oskari documentation and Node.js app running oskari.org
http://www.oskari.org
Other
9 stars 20 forks source link

Create time for objects identifies wrongly in Oskari map service #279

Closed Sanni975 closed 2 years ago

Sanni975 commented 2 years ago

Hi, there is an issue in Oskari map service regarding the creation time for marked objects. For example, the user has several marked objects (like points) saved to a personal layer. The user wants to order the points based on the creation time of the objects. The Oskari map service identifies the creation time to number instead of date, because the order is wrong (picture in attachments). Would it be possible to rectify the column Creation time to be identified as a date?

Sanni975 commented 2 years ago

MicrosoftTeams-image (1)

Sanni975 commented 2 years ago

For example, in the list above the next object date should be 2.4.2020 not 1.6.2020

ZakarFin commented 2 years ago

I guess the erronous date order is not included in the picture, but should be an easy fix with a hopeful 2.9.0 inclusion.

Sanni975 commented 2 years ago

That's great news! Do you have an estimate about when this 2.9.0 inclusion will be released?

ZakarFin commented 2 years ago

2.9.0 is due later this month. We are still working on some fixes that we want to include, but we are releasing it soon.

ZakarFin commented 2 years ago

Trying to solve this we realized that the screenshot is from the older "personaldata" bundle. The currently supported "drop-in replacement" for it is called "mydata". Can you try if using the current implementation solves the issue? It looks like the new one is working correctly.

Sanni975 commented 2 years ago

Good to know. I will be in touch with the user and open this issue again if these don't help. Thank you!

Sanni975 commented 2 years ago

Sieppaa2

Sanni975 commented 2 years ago

Hi, I realised that this problem has not been solved since the dates still are organized wrongly. Do you have a solution for this? Earlier it was mentioned that there would be an update to this in September that would correct this problem?

ZakarFin commented 2 years ago

Hi, it all (or at least the update cycle) depends on the Oskari instance you are using. The updated code has been available for a while in GitHub and you can see the latest version running on for example https://demo.oskari.org and https://kartta.paikkatietoikkuna.fi. If you can reproduce the issue on these instances I'm happy to take another look at it. But if it's on some other instance you should make sure they are using the "mydata" implementation for that Omat Tiedot listing and that the instance have been updated. The most recent version of Oskari is 2.9.1. You can check the Oskari-version by running Oskari.VERSION on the developer tools console of your browser.

Sanni975 commented 2 years ago

Hi, our version is currently 2.7.2. I tried the demo oskari and wasn`t able to reproduce the issue. That would indicate that the 2.9.1 version should correct this bug. Thank you again for the quick reply.

ZakarFin commented 2 years ago

Thanks for testing this out :)