First very rough draft of general links and tasks useful to Batch & Sierra regularly occurring duties
...
Most batch files are for various e-resources, but some tangible batch record collection are also loaded via batch files (print DDA files, vendor and government document and map files, loaded by Government Information staff)
Copy/Paste the batch file names into their respective Collection Trackers name(s) into each Collection Tracker in Box as soon as they are downloaded/received
Take note of how many records there are in a batch file
if that number changes after a batch processes, then something went wrong, and the file or the process needs to be checked for problems (: some of which can be as simple as duplicate bibs in the file, but at other times, may indicate be indicating one or more bibs with errors added by from a typo or a missing field)
When loading in into Sierra, always click Use Review Files; then Test the batch, and first Test the load, then run the if it looks good, Load.
Avoid at all costs, loading files out of order (generally, this is by the date on the file;, but some will have to be added)
If possible, keep up with weekly loads, so loading dates out of order does not become a possibility
For most collection batch files, when the files have the same date; first load new/additions files, then delete files (but there are exceptions noted in the documentationthese workflows); but, if the delete file is dated earlier than the new additions file, load the always check the date, and load files with earliest date before the latest.
001 fields: each MARC record in a batch file needs a unique control number that is not duplicated anywhere in the catalog (if possiblewe may need to overlay them later) - some collections already have them good 001 as as supplied by the vendor; and all current batch collections have documented methods to apply prefixes or create completely unique numbers.
For any completely new batch collectionscollection, where the 001 fields are missing or contain simple numbers, there will need to be a way of applying method worked out to apply a new, non-duplicating prefix or a creation method for a 001 (and add it to a your new workflow)
Hooks: a series of fields and codes are applied to each batch collection, making them easier to batch edit and or remove. The current master document of hooks is kept in USU’s Box; updates will need to be added and updates distributed to various areas of the library (such cataloging, LIT, etc.), as old batch collections are changed, deaccessioned, or new ones are added. The most current Master List E-Resource Hooks is kept here: https://usu.app.box.com/file/1326778691763.
It will need regular updating, with new batch purchases, and regular batch perpetual purchases, as seen in the screen shot below:
...
Batch/Sierra list of tasks:
Original Systems Librarian’s list of tasks (discovery librarian list will be much more focused on records large-bulk purchases or projects):
| View file | ||
|---|---|---|
|
Working Schedule of Tasks for Discovery Services Librarian (under revision) in Box: https://usu.app.box.com/file/1321320586852
...
Cheryl’s plan of
...
training:
Start with the easier single record loads for Wageningen, then weekly record loads of Cambridge EBA, Taylor & Francis EBA, Safari/O'Reilly subscription, and the YBP discovery records, and then the more complex Academic Complete update records. (One thing to remember is to watch the dates on the ebook discovery and deletes and make sure you load them in order. Also; also, with 1 exception, don't load deletes until you have loaded the discovery records with earlier dates.) Make Make sure you use the tracking sheet versions with “current” at the end.
Preliminary list to start with:
Wageningen: tracked against the yearly purchase invoice & Wageningen site itself.
Cambridge EBA: https://usu.app.box.com/file/1318202855178
Taylor & Francis EBA: https://usu.app.box.com/file/1318195064664
Safari/O’Reilly subscription: https://usu.app.box.com/file/1318206846659
YBP discovery records(and deletes): https://usu.app.box.com/file/1321317102096
pDDA deletes via email from Kevin and Tyler
Streaming videos from Gaby: https://usu.app.box.com/file/1323615493212 (keep of with regular emails of adds/deletes)
Academic Complete update records--part of https://usu.app.box.com/file/1321317102096
University Press of Colorado ebooks: https://usu.app.box.com/file/1321432292725
other more difficult batch processing
Further note: just fyi, I'm trying to include any tracking files you might need eventually. A lot of what I'm adding currently are NOT pressing and could be ignored until you have a day where you want a challenge.
Focusing on the weekly and monthly and quarterly (Univ. Press of Colorado ebooks) for now seems like it makes the most sense.
Also, I've always tried to keep right up with all streaming video additions/deletions/edits for Gaby.
pDDA to be deleted emails from Kevin and TylerWEST archived and non-archived yearly uploads
Sierra weeding and batch cataloging projects
The former librarian’s documentation of Procedures and Tracking of files will remain in Box
FTP downloads software/app:
...
Download for Windows: https://winscp.net/eng/download.php
All users
Accept all the defaults and lawyer repellant
and Open
type in the vendor’s ftp site address and log in with user name & password:
A split window will open with your computer on the left; the vendors files on the right:
...
For historical use & older tracking:
...