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.
Hallo zusammen,
es wäre extrem gut, wenn es eine Regel erstellt wird, die es erlaubt Kunden und Kundinnen ohne Mitgliedschaft zu sperren.
Viele Grüße
Marcel Peters
English:
Hello everyone,
it would be extremely good if there was a rule that would allow banning customers without a membership.
Best regards
Marcel Peters
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