System settings

You find the Quria system settings under System settings in the Configuration section of the main menu. These settings apply to all accounts.

Case management: Archive completed cases (number of days)

Specify how many days should pass before completed cases are shown as archived to the patron. Until a case is marked as archived, the patron can continue adding comments and reopening the case. Once a case is archived, the patron can only view it without making changes. Use -1 if cases should never be archived. Use 0 if cases should be archived immediately upon completion.

External depots: Stop trapping reservations (number of days prior to external depot expiry date)

You can define the number of days prior to external depot expiry date when trapping of reservations will be stopped. If no value is set, the trapping will continue until the depot expiry date is reached, but patrons will not be able to borrow the item unless the expiry date is extended.

Item transaction log: Keep patron information for returned items (in days)

You can define a number of days to preserve loan information for returned items. The value -1 will make the system disregard this setting. This also affects patron information in the item transaction log. Loan history for patrons that have chosen to save loan history is not affected by this setting.

Item transaction log: Maximum number of patrons presented

You can define the maximum number of patron names to present in the item transaction log for returned items. The value -1 will make the system disregard this setting.

Login attempts: Maximum number of attempts

Set the maximum number of failed login attempts that are allowed before the patron is temporarily blocked from further login attempts. The block period is defined by the system setting Login attempts: Time Period

The value -1 will make the system disregard this setting.

Login attempts: Time period (in minutes) for maximum number of attempts

Set the time period (in minutes) during what time the patron should be temporarily blocked due to having reached the maximum number of failed login attempts. After this period is reached, the patron can try to login again.

Note:
If the patron sets a new PIN the previous failed attempts are cleared and the patron can log in again. It is recommended that the default error message in the Arena Login portlet is modified to either harmonize with the time period setting in Quria, or to leave out for how long the patron is blocked. The default text picks up a variable for the time period in Arena (default value 1440 minutes).

Maximum overdue period for debt reminders

In order to exclude debts that have been overdue for a long time from debt reminders, you can set a maximum overdue period (days) for debts. The default value is 720. If you set it to 0, no debts will be reminded.

The reason for making this setting is to prevent sending reminders for migrated debts that have already been subject to debt reminders. However, it should be noted that if you at a later point make longer pauses in your debt reminders, this setting may have unwanted consequences.

The setting affects the scheduled jobs Generate debt reminders and Debt reminder bills.

Note:

This setting should be defined at the time of installation before any debt reminders are sent, and only updated after careful consideration. The period defines the full reminder chain. So to have a reminder chain that requires more days than the setting will prevent the latest steps. E.g. if bills are not sent until 75 days have passed, a setting of 70 days will prevent bills from being generated.

Maximum overdue period for overdue reminders

In order to exclude items that have been overdue for a long time from overdue reminders, you can set a maximum overdue period (days) for loans. The default value is 70. If you set it to 0, no loans will be reminded.

If set to -1, the jobs for overdue reminders will not run at all.

The reason for making this setting is to prevent sending reminders for migrated loans that have already been subject to reminders. However, it should be noted that if you at a later point make longer pauses in your reminders, this setting may have unwanted consequences.

The setting affects the scheduled jobs Generate overdue reminders and Overdue bills.

Note:
This setting should be defined at the time of installation before any reminders are sent, and only updated after careful consideration. The period defines the full reminder chain. So to have a reminder chain that requires more days than the setting will prevent the latest steps. E.g. if bills are not sent until 75 days have passed, a setting of 70 days will prevent bills from being generated.

Membership expiry warning (number of days)

Set the number of days prior to membership expiry date that the warnings should be sent. The value -1 will make the system disregard this setting.

Minimum retention period for fully paid debts and the related payments (in days)

Set the number of days after which fully paid debts can be automatically removed. Be very careful not to set a too short period. It must be based on your legal requirements. The scheduled job will not accept a value between 0-365. The value -1 means that the debts should not be automatically removed.

The setting affects the scheduled job Hard delete old debts and bills.

Number of patron names presented in the item transaction log

You can define the maximum number of patron names to present in the item transaction log for returned items. The value -1 will make the system disregard this setting.

Prioritize cover URLs from the record

When presenting covers in Quria, you can decide if they should be based on cover URLs in the manifestation information instead of on the ISBN presented by the cover service.

Save reservation history

You can define if reservation history should be kept or not. Possible values: true or false.

If set to true, no reservations are removed from the system regardless of status and will be searchable under Reservations on the Collections page.

Only active reservations are listed under Reservations on the patron details page regardless of this setting.

Show notification history after event has passed (number of days)

You can define the number of days to show notification history after the event causing the notification (such as overdue reminders and reservations) has passed. The notification history is displayed in the patron details and will be deleted once the period has expired.

Update PIN codes by external patron synchronizations

In connection with the import of patrons from external sources, e.g. student registers, you can use this parameter to choose whether you want potential PIN codes included in the imported data to update the patron PIN code in Quria. Please note that the PIN code belongs to the patron, which means that if the installation has multiple accounts and the patron has multiple patron accounts, the changed PIN code will affect all patron accounts. The PIN is only updated if it conforms to the defined PIN format. If you want the patron PIN code to be updated, set the value to true. By default the setting is set to False.

VAT: Default code

Enter the default VAT code that should be used in e.g. bills in XML-format. All types of debts/payments that has no specific VAT defined, will fall back to this default.

VAT: Default percentage

Enter the default VAT percentage that should be used in e.g. bills in XML-format. All types of debts/payments that has no specific VAT defined will fall back to this default.