Axiell Quria Ideas

Welcome to the Ideas Portal for Quria users!

Axiell wants to get our customers to be involved in the roadmaps suggesting ideas for features or functions. Unfortunately we cannot develope each and every function suggested but we want to make sure that you have your say. Add your ideas, and opinions to Axiell's roadmap for Quria, creating new features that yours and other libraries would benefit from. You can also vote for other peoples suggestions as well.

In order to make this portal more useful for all the contributors and for us that work with your ideas, we kindly ask you to write in English.

Please note: If you have an error or a misbehaving function, please contact your local Support for the best possible service. If you are not sure what forum that is the most appropriate for your issue, please choose local support as a first step.

How it works:
The ideas are read and reviewed on a regular basis, by product manager and/or local representative. Your ideas will then be available for others to see, vote on and discuss. We encourage discussions between the idea contributors.

Successful ideas will the be prioritzed within our backlog.

What does the status mean?

Under investigation - often there needs to be a discussion between developers and system specialists before we can say if something can be developed, how and when.

Planned - this suggestion or need will be fufilled in some way in a forseable future.

Future consideration - this status means that we think that it's good idea with no technical obstacles but it's not decided if it can be prioritized and put on the roadmap.

No action - in some cases it is impossible to meet some requirements for technical or other reasons, and sometimes there is another alternative way to solve the need.

Right to reject and close
We reserve the right to reject ideas, and also close issues after 3 months if we don't receive an answer to our follow up questions.

Mulighet for å hindre utsending av to purringer samtidig / Possibility to prevent two overdue reminders to be sent simultaneously

Ved helligdager deaktiverer vi utsending av purringer, så ikke låner får purring på julaften f.eks. Når purringer aktiveres igjen, blir det kortere mellomrom mellom purring 1 og 2, noen ganger kan purring 2 komme f.eks. allerede dagen etter purring 1. Dette fordi slik det er nå hos oss, genereres purring 1 7 dager etter forfall, purring 2 14 dager etter forfall. Vi ønsker at det i tillegg er mulig å gjøre en innstilling som gjør at purring 2 ikke sendes ut før det har gått en uke siden purring 1. Tiden i mellom purringene, bør selvsagt det enkelte bibliotek selv kunne velge. Det er uheldig for låner å få to purringer (inkludert gebyr) nesten samtidig. Jeg er klar over at purringer kan kjøres manuelt i stedet, men i et stort bibliotek er det ønskelig med automatisert utsending.

During holidays, we deactivate sending of overdue reminders so that borrowers do not receive these on Christmas Eve, for example. When overdue reminders are reactivated, the interval between Reminder 1 and Reminder 2 becomes shorter. Sometimes, Reminder 2 can be sent as soon as the day after Reminder 1. Currently, at our library, Reminder 1 is generated 7 days after the due date, and Reminder 2 is generated 14 days after the due date. We would like to add a setting that prevents Reminder 2 from being sent until a week has passed since Reminder 1. The time between reminders should be customizable by each individual library. It is unreasonable towards borrowers to send two overdue reminders (fees are also generated) almost simultaneously. We are aware that reminders can be manually triggered, but in a large library automated sending is desirable.

  • Therese Engan
  • Apr 26 2024
  • Future consideration
  • Attach files