Axiell Quria Ideas
Welcome to the Ideas Portal for Quria users!
Axiell invites customers to contribute ideas for new features or functions. While we can't develop every suggestion, your input helps shape Quria’s roadmap. You are welcome to add ideas, vote on others’ suggestions, and discuss them. To make this portal more effective, please submit your ideas in English.
Ideas are regularly reviewed by the product manager or local representative. Once reviewed, the ideas are visible for voting and discussion. Popular ideas will be prioritized within our backlog.
Status meanings:
Under investigation: Developers and specialists are discussing if the idea is possible to implement.
Planned: The suggestion will be fulfilled in some way in a foreseeable future
Future consideration: A good idea, without technical obstacles, but it can't be prioritized into the roadmap at the moment.
No action: Technical or other issues prevent development, or an alternative solution exists.
We reserve the right to reject ideas and to close issues after 3 months if we don't receive answers to follow-up questions.
For technical issues, please contact your local support.
Welcome to the Ideas Portal for Quria users!
Axiell invites customers to contribute ideas for new features or functions. While we can't develop every suggestion, your input helps shape Quria’s roadmap. You are welcome to add ideas, vote on others’ suggestions, and discuss them. To make this portal more effective, please submit your ideas in English.
Ideas are regularly reviewed by the product manager or local representative. Once reviewed, the ideas are visible for voting and discussion. Popular ideas will be prioritized within our backlog.
Status meanings:
Under investigation: Developers and specialists are discussing if the idea is possible to implement.
Planned: The suggestion will be fulfilled in some way in a foreseeable future
Future consideration: A good idea, without technical obstacles, but it can't be prioritized into the roadmap at the moment.
No action: Technical or other issues prevent development, or an alternative solution exists.
We reserve the right to reject ideas and to close issues after 3 months if we don't receive answers to follow-up questions.
For technical issues, please contact your local support.
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