Add, Delete, Update Databases Report
The Add Delete Update Databases (Adutext) report re-indexes the full text records to keep up with added, deleted and updated information for both bibliographic and authority data. It is important to schedule the Add, Delete, and Update Databases report to run at frequent intervals. It is recommended the report be run each night when there are fewer users updating the system.
When new records are added to SirsiDynix Symphony, or modifications are made to existing records, the report indexes the headings and words in the records so they can be searched and browsed in the catalog. When items are removed, the report updates the library holdings information, text indexes, and authority thesauri so that all references to words or headings in that text record are erased.
This report contains the Basic Tab: Reports. It also contains the Shutdown Options (Windows only) tab on Windows systems.
Various record statuses are reported in the log. The following key may be used to interpret the results.
1 |
Has been processed |
4 |
Needs to be processed |
6 |
Locked/currently processing |
0 |
Does not need processing |
Important Considerations When Running This Report
• | The Add, Delete, Update Databases report should be run each night between 6:00 p.m. and 8:00 a.m.; the dynamic index is automatically rebuilt or reorganized when the report is run between those times. For more information, refer to the Maintaining the Integrity of Your Data with Reports topic. |
• | When this report is run on the Windows platform, SirsiDynix Symphony services may stop at the beginning of the report and restart automatically when the report finishes, depending on the settings you choose under the Shutdown Options tab (for more information, see Shutdown Options (Windows only)). Users cannot access SirsiDynix Symphony through WorkFlows or e-Library while SirsiDynix Symphony services are stopped. If stopped, do not restart the SirsiDynix Symphony services manually while this report is running. |
• | If you choose to keep the SirsiDynix Symphony services running as the report runs, you may encounter the following message while using SirsiDynix Symphony WorkFlows: "The records are currently in use." This message is a result of those records being locked for indexing or updating; the records will become available again after the report is finished. |
• | The number of keys the SirsiDynix Symphony system can handle really depends on the size and speed of your server. The standard recommendation is not to run more than 5000 keys through adutext. If you are loading a larger number of bibliographic records, the safest procedure is to use the Bibliographic Database Overlay report. Please note that you then have to run the Rebuild Heading Databases and Rebuild Text Databases reports in order to see the new records. |
• | Your system can be configured to create provisional authority records (both MARC21 and UNIMARC) when running this report. Contact SirsiDynix Customer Support to configure your system for creating provisional authority records. |
Updating Headings in Bibliographic Records
The Add, Delete, Update Databases report will not update headings in bibliographic records based on the 4XX (See From) entries in the authority record. Only the Change Invalid Headings by Authority report will do this. The Add, Delete, Update Databases report will update headings in the bibliographic records in cases where an authority record load overlays an existing authority record and changes the heading.
For example, when an authority record is overlaid by a load, the old leading term is moved to the Old Leading Term entry (typically the 961) in the authority record. For example, you have the following authority record.
.001. |aSUBJECT015
.150. |aRabbits
You plan to overlay the record by loading the following authority record.
.001. |aSUBJECT015
.150. |aBunnies
After the overlay, the SirsiDynix Symphony authority MARC record will look like the following.
.001. |aSUBJECT015
.150. |aBunnies
.961. |aRabbits
The Add, Delete, Update Databases report will then use the information in the 961 entry to find headings in the bibliographic records authorized by that authority key and replace the 961 text with the 1XX text.
Related topics