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.
Dear Sibylle,
Unfortunately, we do not see a safe solution.
If it is an identical title and author, it will be like this.
We cannot look at publishers, because the same book can be published by different publishers over time and then there will be another manifestation of the same work. On the other hand, one might assume that fiction should be matched as it is today, while for non-fiction it can be checked at publishers, but it feels a bit insecure and also makes it even harder to grasp and troubleshoot.
We can also not build a function for approval of match and merge, because in a bulk import, there would be “stop and go”. But we will try to think about it when we deliver bulk metadata. Can we deliver a tool so users can catch them a little now and then?
For example, search for all manifestations that have been created during a certain time, back in time, and then see where they have ended up? But what to do next? Then you have two works with the same creator / title and then comes a third, which one should it be merged with then? Not an easy task, but we understand what you mean and will keep it in mind for bulk metadata.
For the moment, the best thing to do, is to create a new Work and move the manifestation there.
Thanks, Morten
Dear Morten,
Here three examples of manifestations merged on a wrong work (see ticket SR00060726):
978-3-8342-3093-5 (Berlin)
978-3-8317-3248-7 (Paris)
978-3-616-01044-1 (Gardasee)
It often happens with comics, but I don't have an example right now.
Best regards,
Sibylle
Dear Sibylle,
Would it be possible for you to send a few examples?
Thanks, Morten