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.
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.
Hi
Thank your for this suggestion, but there is a quite advanced logic behind the manifestation types so it not possible to create a customization of them in a near future. The manifestation types are created based on the RDA values together with the work type and expression type, and those are created from the marc records, which is the most common way of getting bibliographical data among the Quria libraries today.
Then every manifestation type is mapped to Arenas mediaclasses, since they are not equal. Arena is a solution that runs on top on many other backend systems with differetens metadata format so every system must have a specific mapping to Arena.
Qurias build-in-logic and connection between RDA values can be used as a help when doing manual cataloguing. When you have chosen the Work type on Work, and RDA Inhaltstype on Expression you can click the button Expressionsart festlegen to let Quria calculate the Expressionart. When you work on the manifestation, you choose RDA Medienart and RDA Datenträgentyp and then click on the Manifestationsart festlegen button to let Quria calculate a suggested Manifestation type. Then it's of course possible to chose a different one in the end.
I totally understand that you would need a shorter customized list of manifestation types but it's not possible for us to meet this wish for quite some time, if ever.
Best regards
Magdalena Olofsson, Quria product manager
Attachments Open full size