Headings – merge (and remove duplicates)

This function, as it declares, allows for the merger of duplicate controlled term headings

Build headings from bibliographic records

Build bibliographic control numbers

Build item call numbers

Build authority headings **

Build authority relationships **

• • Note that the last two are reserved for AIT usage and will not appear on library workstations

These tasks provide functions for database housekeeping, and do not need to be sheduled, but only run after instruction from AIT

Allocations – standard

This function allows for the operation of automatic allocations for Homebound operations

OPAC search term extraction

Following update to Schema version 174, new fields are added to the SQLTrans table, allowing search terms from OPAC to be recorded. This task then allows extraction of these terms for use in tag presentation. This task only needs normally to be performed on one occasion, to build the new fields and then AWS will add these fields automatically

Old charges and purge associated users if inactive since the purge date

This purge option has value in maintaining the user database – normally a purge of inactive or expired users will not remove users if they still have charges owing. This option allows these users to be specifically targetted, so that the charge details are removed, allowing those users to be purged, where they remain inactive

Build bibliographic search table

Build heading search table

Build user search table

These tasks perform the same function as in ‘Search Build’ but may be invoked as tasks here, and so scheduled. Override options llow the number of records processed to be limited: if an override is applied and the records are limited, then the process bypasses the synchronisation of tables to ensure all BDDS DDS_Status values reflect the content of BDDR DDR_Status and also that the item tables are in synch.

Reservations – enliven dormant reserves

This task allows a dormant reserve to be enlivened when the dormancy period is complete, and restores the reserve to active status (unless its expiry date is also passed).

There is no override option. The Task name is RESERVE_DORMANCY, and should be run daily. To assist in ensuring dailly operation, if you invoke any Task other than the reserve dormancy task, File Watcher will look for an entry of this task in the task history. If there is a zero count it will run the reserve dormancy task. The history table is updated, and so the table will then have one entry every day in active sites and this will make sure that there is a regular refresh of the dormant reserves – the site just has to have one task running per day to get this.