Open sseppi opened 2 years ago
@sseppi Maybe instead of this, or in addition, I would suggest increasing the frequency of automatic refresh for events. Right now NOI Events and Locations are refreshed only every 12 hours based on default server configuration. We could make events refresh every 5-10 minutes instead for example. I think every 3 minutes should be minimum to not overload our back-end or NOI API.
@SaimonasFOS I asked to our meeting management, they confirmed me that a delay between the change in their sysem and the display of maximum 5 minutes is fine.
In my opinion we can try to start with 3 minutes and see how it works everything.
I would also suggest to keep the refresh rate as a configuration that we can easily change in the system.
@sseppi The refresh rate is already configurable, although not very "easily".
In the application.properties file of the back-end there is cron config:
cron.opendata.events = ${NOI_CRON_EVENTS:0 0 0/12 ?} cron.opendata.locations = ${NOI_CRON_LOCATIONS:0 0 0/12 ?}
It either takes server config value "NOI_CRON_EVENTS" or uses default value "0 0 0/12 ?" which is every 12 hours. I could change the default to every 3 minutes but I don't know if the default is used in the server.
Probably need to ask @Piiit about this.
@SaimonasFOS and @Piiit in this iteration, I would set the refresh to 3 minutes to start testing.
As a Meeting Management team member I need a Refresh button for the scheduler and the image in order to refresh the schedule and/or the image by taking the last updated data from the Open Data Hub.
Sometimes our meeting management has to do a last minute change in the data of an event (eg. title, start time, end time, etc.). for this reason they need a refresh button that regenerates the schedule and the image by getting the data directly from the Open Data Hub.