System-generated files are created from various Sierra applications that automatically create review files as part of their operation. We can also create these manually in Data Exchange with the Use Review Files checkbox. They have to be copied into Create Lists to use them.
Table of Contents
Files the System Generates Automatically
Items on Search - the system does an automatic search of all the Marmot records to find any that have the status of “Missing” or “Claims Returned”. This system-generated file contains all the Marmot member items with these statuses.
Items with Holds - Items currently checked out with outstanding item level holds. This is neither a list of all titles that have holds nor a list of all holds. Because this file is updated once per night, it can contain items that are no longer on hold (for example, if the hold has been canceled or filled). This file cannot be emptied.
OverDue items - All overdue items, including those that do not require overdue notices at this time are on this list. Because this file is updated once per night, it can contain items that are no longer overdue (for example, items that have been renewed). This file cannot be emptied.
Others: Purchase orders to be processed, Purchase orders last printed or sent electronically, Claims for orders to be reviewed, Claims for orders to print, and Pull slips to be printed.
Here are some of the examples of files that are system generated.
Files Created by Loading Records
These files can also be created by using Data Exchange. When loading a file, in the load window you would choose Use Review Files to create a system-generated file(s).
Here are examples of overlaid and inserted records that the system generated from Data Exchange. The process separates the two groups of records into separate files automatically.
Label Printing Batches
Still, other examples are the monographic labels that can be printed from the edit display or summary display of items records. These labels are sent to the system-generated files. Here are some examples of these files. Each one will end with the Sierra login of the person who generated the labels.