Axiell Quria Ideas
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.
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.
Hallo, I have set the wrong status - it will be released in the next release, Feb 6th!
Sorry!
More information will be present in the release notes
Regards
Magdalena
Hi,
where can i find this Rule to configure it?
Best regards
Marcel Peters
Okay sorry.
I thought this will happen automatically.
Best regards
Marcel Peters
Sorry, this tool demands a lot of manual handling and I am reviewing the ideas now and then, not every day. Thanks for the reminder //Magdalena
Hi,
why is this Idea on "Awaiting answer from Idea Creator"?
I gave an answer.
Best regards
Marcel Peters
Hi,
mir ist durch Rücksprache Ihrer Kollegen bewusst, dass dies absichtlich so eingerichtet wurde.
Daher bitte ich hier um eine Regel, die dass Sperren automatisch ermöglicht.
Leider ist es bei dem Arbeitsaufkommen nicht praktikabel, wenn ich auch dieses manuell alle vier Wochen nachschauen muss.
Daher bitte ich um diese Regel.
Viele Grüße
Marcel Peters
Englisch:
Hi,
I am aware, through consultation with your colleagues, that this was set up that way on purpose.
So I'm asking for a rule here that will automatically allow blocking.
Unfortunately, given the volume of work, it is not practical if I have to check this manually every four weeks.
So I'm asking for this rule.
Best regards
Marcel Peters
Hi,
When we created the membership funcion we were thinking that it's unessesary to create free memberships, instead all people that can use library services for free don't need a membership and only those who have to pay need a membership. We felt that this would make life easier for you.
In the last release we have created a possibility to find all patrons without membership and block them in bulk, an operation that can be performed manually now and then to avoid people without membership to use the library service. For example, you can search for specific patron categories and/or agegroups and block them, and avoid to block for example staff or children but still don't mess with adding membership to them.
What do you think about this approach?
Regards
Magdalena