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.


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.

 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit QURIA-I-291 Possibility to set default values for adding new patrons.

Add patron: required fields Merged

We'd like to have the possibility to have more required fields in the customer mask. For our library it would be "Gender" (because we use this for statistics) and "PIN" (because you can't see after saving if the PIN has been entered). It would be great if every library could decide on their own which field they like to have as a required field (e.g. in the configuration).

  • Sibylle Schlumpf
  • Apr 15 2020
  • Future consideration
  • Morten Nørgaard Berg commented
    May 25, 2020 08:47

    Hi Sibylle,

    It's not in our plans for the moment, that each library can decide this. Since Gender is not mandatory in other libraries for GDPR reasons, we don't require it today. However, we will make a note for future consideration.

    Best regards Morten