Welcome to the Ideas Portal for Quria users!
Axiell invites customers to contribute ideas for new features or functions. While we can't develop every suggestion, your input helps shape Quria’s roadmap. You are welcome to add ideas, vote on others’ suggestions, and discuss them. To make this portal more effective, please submit your ideas in English.
Ideas are regularly reviewed by the product manager or local representative. Once reviewed, the ideas are visible for voting and discussion. Popular ideas will be prioritized within our backlog.
Status meanings:
Under investigation: Developers and specialists are discussing if the idea is possible to implement.
Planned: The suggestion will be fulfilled in some way in a foreseeable future
Future consideration: A good idea, without technical obstacles, but it can't be prioritized into the roadmap at the moment.
No action: Technical or other issues prevent development, or an alternative solution exists.
We reserve the right to reject ideas and to close issues after 3 months if we don't receive answers to follow-up questions.
For technical issues, please contact your local support.
It is possible to address the Guarantor of a young child using the variables:
Dear {{PatronFirstName}} {{PatronLastName}} {{GuarantorStart}} (guarantor for {{Child}}){{GuarantorEnd}}
This would then return:
Dear Tom Brown (guarantor for Lisa Green)
This works as long as you use the “Patron connection” function in Quria and if both Child and Guarantor are registered users of Quria.
German libraries often use then field “Guarantor name (if no connection)” instead of the Patron connection. Since library use is charged for, many Guarantors might not be registered in Quria as users.
(For internal reference: HB IN00134963)
I have been told by my German Axiell colleagues that it is forbidden to send invoices to children. if this also goes for the "hälsningsfras", I do not know. I will check if I can find out.
I will forward your suggestions to the client, and we will see what kind of answer I get.
I understand what the customer is expecting. But I want to know what is the practical problem with the current solution? Is it a real problem that causes trouble or is it just "not what the customer expects"? If the customers suffers badly from not getting the guarantor information in the messages I would recommend them to remove the variable for name and replace it with "Dear Library visitor" or "This is a message from {{LibraryName}}"
//Magdalena
Client is expecting to be able tu use somthing similar to
Dear {{PatronFirstName}} {{PatronLastName}} {{GuarantorStart}} (guarantor for {{Child}}){{GuarantorEnd}}
in notifications.
But since there is no Patron for the Guarantor, the message ends up with Dear (child's name). This was not what the client exepected, the help was not specific enough to explain this.
Help will be changed, but an equivalent for the "Guarantor name (if no connection)" is desirable.
What is the practical problem with the current solution?
Depending on how the guarantor has been entered for the young patron, there are three different options for how notifications will be sent to guarantors:
The young patron is connected to an adult patron that is registered in Quria: notifications will be sent to the name and contact details registered for the guarantor.
A guarantor name has been added: notifications will be sent to the name of the guarantor but to the contact details registered for the young patron.
No guarantor is associated: notifications will be sent to the contact details registered for the young patron, but with the addition “To the guarantor of”.
//Magdalena