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.
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.
Hi,
We have decided to implement those two search filters, but I can't say when exactly it will be in place.
Best regards and have a nice weekend!
Regards
Magdalena
Hello Magdalena,
thank you for your detailed reply:
1. The thing is that this function is not a "cash report" with the purpose of giving information about how much money there is in the till, and the reason for us having this solution of fee owning branch is for that libraries in consortias, that are using a common Arena with online payment option, they need to be able to figure out how to split the money. When they payment of for example overdue fees is done in Arena, they need to know which municipality that owns the fee and that is the municipality in which the book originally was borrowed.
Thank your for this explanation ��� we did not consider this, because we are in a different situation.
The need to use this function as a ���cash report��� came up, because the actual cash reports (analytics���) failed right after the first release we experienced in December and Sebastian recommende exactly this as workaround: Use patrons / fees to fetch all the payments, then export it as csv to be able to check.
As long as Quria���s cash reports under ���Analytics��� are correct, we are fine ��� but when we have to do research, where mistakes come from, the only way ist to look at the details under ���Patrons.
2. We are investigating what we need to develop to fullfill the requests from the German libraries when it comes to fees and payments, but it's not clear to us. If you disregard what Quria has today, what do you need to be able to handle your payments correctly? You write that you want to get the paid fees per branch where they have been paid. Maybe that is not enough, one branch could have many desks and payment points so you need to get the list per workplace, I guess?
Yes, this would be an improvement. It would even help, if the workplace was shown in the overview, not only under details ��� because the we could just rearrange the list by workplace.
Unfortunately neither ���workplace��� nor ���creating branch��� is included in an CSV-export oft he list (see attached file) ��� we cannot work around that way either.
3. (As a background to my lack of knowledge: The Scandinavian libraries are always using a separate cash register system in parallell with the library management system, which produces the daily reports of the transactions).
In Freiburg Quria is the place where all the details for payments are saved. We deposit weekly or monthly the whole sum of payed fees in SAP, so there is the documentation about the amount of money for a period ��� but no information about what sort of fees are included.
I guess most german libraries handle things like this.
4. I'm not sure what you mean with no 2. Jahresgeb��hr is a type of membership fee in your system.
a) in the list of possible fees names turns up ���Mitgliedsgeb��hr��� (german word for ���membership fee���) but we never had a payment with this description. When we renew the membership and patrons pay, it is named ���Jahresgeb��hr��� in the list and patron account. No idea why ���Mitgliedsgeb��hr��� even exists but this is not important.���
5. and I can see them in the list when searching for an interval in Payment date
hmm���so where is my mistake?
When I filter like this I get no results:
[cid:image003.jpg@01DA6575.18678F30]
When I reduce the search filters to an ���end date��� I get the ���Jahresgeb��hr���-Payment of that day in that branch:
[cid:image004.jpg@01DA6575.18678F30]
Kind regards
Silke
Von: Axiell
Gesendet: Mittwoch, 21. Februar 2024 12:25
An: Kelpe, Silke
Betreff: Magdalena Olofsson (Axiell) responded to idea QURIA-I-858 two more search filters in Patrons / Debts
Hi!
Thanks a lot for this. The thing is that this function is not a "cash report" with the purpose of giving information about how much money there is in the till, and the reason for us having this solution of fee owning branch is for that libraries in consortias, that are using a common Arena with online payment option, they need to be able to figure out how to split the money. When they payment of for example overdue fees is done in Arena, they need to know which municipality that owns the fee and that is the municipality in which the book originally was borrowed.
We are investigating what we need to develop to fullfill the requests from the German libraries when it comes to fees and payments, but it's not clear to us. If you disregard what Quria has today, what do you need to be able to handle your payments correctly? You write that you want to get the paid fees per branch where they have been paid. Maybe that is not enough, one branch could have many desks and payment points so you need to get the list per workplace, I guess?
(As a background to my lack of knowledge: The Scandinavian libraries are always using a separate cash register system in parallell with the library management system, which produces the daily reports of the transactions).
I'm not sure what you mean with no 2. Jahresgebühr is a type of membership fee in your system and I can see them in the list when searching for an interval in Payment date.
Thank you for helping us with this
Best regards
Magdalena
Hello Magdalena,
thank you for your response and considering our idea.
Yes ��� related are:
1. Support Ticket - IN00204610 that describes the irritating fact, that the filter ���view data for��� where you can choose a certain branch library does search for fees, that have been caused by loans in that special branch ��� instead of where the fee has been paid ��� what everyone would expect.
The effect of this misleading filter is, that the request does not deliver the payments oft he chosen date and the chosen branch ��� the result includes payments that have been done in other branches.
Es far as I can see, the filter ���view data for��� asks fort he chosen branch via the field ���Owning branch��� instead of ���creating branch��� ��� see e.g. payment of Janz, Nuria on 16/01/2224, Dept ID 6a50a887-a541-4bc3-830c-ecd40455fcd9
2. We do not understand why our membership fees (in our system they turn up as ���Jahresgeb��hr��� not as ���membership fees���) are not included in the list when you use the filter ���Payment date (period)��� for a real period ��� start date and end date fields filled with a date.
They are only included in the result list, when you only chose an end date.
Kind regards
Silke
Von: Axiell <64b773ff2f551a81a839d26d-axiell@iad-prod1.mailer.aha.io>
Gesendet: Dienstag, 20. Februar 2024 11:58
An: Kelpe, Silke
Betreff: Magdalena Olofsson (Axiell) responded to idea QURIA-I-858 two more search filters in Patrons / Debts
Hi,
Thank you for submitting this. Is there anyhing else that you miss regarding fees and payments in Quria?
Regards
Magdalena