...
- "Enter OPID" is a sub-function of these other macros. You will never need to select this; it's built into any staff member report you run.
- "Enter Start and End Dates" is also a sub-function of these other macros. You will never need to select this; it's built into every report you run.
- Run “Dept Summary Report” if you want a summary of all work done in LTS for the desired date range.
- Run “Individual Report” if you want to extract a summary of all work done by a specific staff member during the desired date range.
- Run “Staff/Bib ID Report” if you want to extract a list of all bib IDs worked on by a specific staff member during the desired date range.
- Run “Law TS Summary Report” if you want a summary of all work done in LAW TS for the desired date range.
- Run “BATCH Summary Report” if you want a summary of all work done via batch processing for the desired date range.
- Run “NON-BATCH Summary Report” if you want a summary of all work done by non-batch processes for the desired date range.
- Run "Maintenance Summary Report" if you want a summary of all maintenance processes for the desired date range.
- Run "Transfers Summary Report" if ????????
- Run "Unit Reports" if you want a summary of all work done by members of a specific unit within LTS for the desired date range.
...
e. “Records Enhanced” – This information is found by running the Record Enhancements query in the database 1New_culv2-2012-2013.accdb. Includes info for WorldShare, Batchmatch, ebooksenhanced, and all “Update Backlog Records” (storage items) jobs. This query is run against the Batch_Stats table in the built by PH’s job in LS Tools, mentioned in h, below.To get the total number of records enhanced, run “Record enhancements” Enhancements” query and then run “Get Records Enhancements Grand Total” query. The resulting table will consist of one number: The total number of records enhanced in the FY. (Note: You will need to go into first query, "Record Enhancements" and edit to limit for specific FY.)
...
h. “Batch Jobs” – LTS managers would like to determine how many batch processes are run each month. Additionally, Batch Processing unit managers would like to know how many records for each vendor/collection are processed. Not all of this information can be gathered via the existing LTS statistics database, so Pete Hoyt built a job a script was built in LS Tools to gather the data. (See query spec, “BatchStats_countXandH.docx”). The job is found under “Administrative Proc” in LS Tools, and is called “TS Stats Summary." The data from this job should be entered into the spreadsheet “3_Batch_Stats_FY15_16.xlsx” found in L:\tsstats\. (Get count from adding together “#of jobs run” from each page of 3_Batch_Stats_FY15_16.xlsx. This grand total will be entered into the “Batch jobs” line item in the LTS_Stats_2005-2016.xlsx spreadsheet.) (NOTE: Do we want to create a report for this data that presents it in some way other than monthly breakouts?)
...