Administration tools

Under the Admin tab in the Configuration section, you find tools that facilitate administration of your Quria installation.

Scheduled jobs

Different scheduled jobs are set up for the Quria system at installation, and you can run the jobs manually at any time. You can also edit a scheduled job by clicking it in the list. You may for example want to temporarily disable a job or change the time for the next occurrence of it.

You can filter the list of logs on Aborted or Failed jobs. Aborted jobs are due to e.g. a new release is deployed and running jobs have been aborted. They need to be started again to be finished, but there is no underlying problem. If specific jobs are continuously failing, please report to Axiell for investigation. Keep in mind that the Date/time column contains start date/time if the list is not filtered. If filtered on Aborted and/or Failed, the stop date/time will be presented.

You also find a status overview of executed jobs. If you expand the rows you get more information such as run time and relevant statistics for the job. The log for the job Resend failed messages is found here, and it contains information about how many messages that have been handled if they failed for some reason. The job is run every hour, and for each failed notification it will continue trying for three days. For the time being it does not include information about specific phone numbers or e-mail addresses. It might be added in the future if Quria can get useful information back about the reason for the failure.

Note:
It is recommended to start different scheduled jobs with some time apart (at least 10 minutes) rather than starting several jobs at the exact same time. If sending notifications failes, the reason might be in the very end of the message chain, i.e., when the SMS or e-mail provider is handling the message, and then Quria might not get the information back.

Note:

It is recommended to start different scheduled jobs with some time apart (at least 10 minutes) rather than starting several jobs at the exact same time.

If sending notifications failes, the reason might be in the very end of the message chain, i.e., when the SMS or e-mail provider is handling the message, and then Quria might not get the information back.

Overdue warnings, reminders and bills

You can set up the frequency of generation of overdue items, with separate jobs for warnings, reminders and bills, and debt reminders. Make sure to trigger these jobs during daytime, to avoid disturbing patrons with email or SMS notifications. You can also fetch invoice updates from an external financial system.

If you want to remove old debts and bills you can use the Hard delete old debts and bills job. The job needs to be activated and the system settings Minimun retention period for fully paid debts and related payments (in days) and Minimun retention period for settled and closed bills needs to be configured. Both settings must be set to more that 365 days to take affect.

For integration with Visma, you must run one job to check for bills that have been successfully sent to Visma and get the latest invoice information, and another job to look for outstanding bills that have a Visma invoice number, and check their payment status. If an invoice has been paid, it will be noted as External payment in the patron details. The routines for this need to be set up by the library.

Memberships

You can set up the frequency of update of memberships, with separate jobs for memberships based on bank payments and based on manual payments. The Update memberships based on manual payments job should not be used in combination with the scheduled job for debt reminders, as this would result in debts for membership renewals that might be of no interest to the patrons, and patrons would be reminded of debts that they have not caused.

URL checker

This tool is used to verify the availability of internet resources by checking that URLs in manifestations are valid. It is recommended to run this job during night time.

Order reminders

You can set up reminders for order lines where the expected delivery date has passed. Only one reminder can be sent per order line. See also: Order reminders

Periodicals reminders

You can set up reminders for the case when periodical issues have not been received according to the publication plan.

Patron age group transition

You can set up handling of patron age group transition.

Maintenance of catalogue records

You can clear any unused references to creators, subjects and classifications by running the Discard unused metadata job. This will improve the lists of creators, subjects and classifications when adding or editing metadata.

By running Fetch authority record updates, you will get updates regarding authority persons from DNB.

For titles that come from Onleihe, you can run the job Fetch list of discarded titles from Onleihe to fetch eMedia titles that have been discarded and should be cleared from the catalogue.

For Libris, you can fetch new and discarded titles as MARC records by running the job Fetch metadata updates.

For Onleihe you then run the Handle metadata discard requests job to execute removal of discarded titles. If there are existing items, reservations or eLoans connected to the discarded titles, these will not be discarded. The next time the job is run, it will try to handle the left-over titles again. You can see in the log file which titles could not be handled and take care of these manually. The job Handle metadata discard requests is also used for e-media records from Libris.

The job Handle item discard requests removes holdings in Libris when the last item on a "sigel" is removed from Quria.

The Authorise metadata entities job authorises all metadata entities that is currently not authorised and have authority record control number matching the configured source.

Import of incoming ILL requests

You can also run the job Import incoming ILL to import ILL requests from Libris.

Import

You can import Antolin subjects and MARC records using the import tools. You can also import authority MARC records via the Authority MARC records import. As of now the Finnish data source Yso-Paikat is available and can be used to import Places. When the records are imported, a match against existing Places is performed. Matching Places are updated and marked as authorized. Non-matching Places are imported as new entities and marked as authorized. There is also a function that allows you to delete records based on an input file containing MARC records.

Note:
In order to find the correct manifestation to be deleted, both identifier in 001 and assigner in 003 in the MARC records must match the corresponding identifierIassigner for the manifestation. MARC records without field 003 will not result in a deleted manifestation.

Year end tasks

Some functions that are meant to be used on a yearly basis are found under Configurations/Admin.

Year end processes

Acquisitions. Transfers any open requisitions and orders to the next year, based on the budget year information in the requisitions and orders. If budget periods for the new year do not exist, they will be created automatically with the same amounts as the current year. Modification of amounts must be handled manually.

Periodicals: Publication plans are created for titles that don't already have one for the new year, based on existing publication patterns. Only periodicals with active subscriptions will be handled in the process. When you run the year end process for periodicals, publication plans will be generated with the same patterns as the current year. You may need to adapt the plans manually if there are changes to the release patterns for specific periodicals. Any manual changes done during the past year will not be included in the new publication plan.

Author fund reports

You can generate and download various author fund reports based on your local needs, all using data from the current account. The file format and data included depend on the requirements of those requesting the information. For reports based on loan numbers, you have the option to include renewals in the counts.

After running the reports, the reports can be downloaded and sent to the recipient.

The different reports are:

Number for loans per title. Counts all loans per manifestation.
Number of reference items per title. Counts all items with an item type marked as Reference. Note: the report counts the items at the time when the report is run, so it is important to run the report as close to the new year as possible.
Number of loans per title and component part. Counts the loans for titles with manifestation types that are marked specifically to be included. This is done in Configurations/Settings/Metadata and Items/Manifestation types.
Number of loans per title for VG Wort. Counts all loans per manifestation. A specific report format for the German market.

Note:
To be able to configure and run author fund reports, the module needs to be activated. Please contact Axiell Support if you need assistance.