Creating Check In Record Notes:
This section contains procedures for check in record notes, with explanations and examples of types of notes and note fields.
Notes in the check-in record are difficult to prioritize. The following are some guidelines for ordering notes:
* TOP NOTES are temporary, timely, and MUST BE SEEN & REVIEWED prior to check-in.
*** PENDING 'ANYTHING' (frequency, vendor, title changes, pending drop, etc.).
+++++Notes from Order Record (entered by the Serials Acquisitions Manager, do not delete)
Check-in notes are NUMBERED.
*****EXTRAPOLATE: [Usually followed by a brief pub schedule]
The following set of notes is not NUMBERED:
Others notes that are not numbered (some of which may be claim notes and others FYI messages) include:
5 dash notes will be entered below the parameters and current claim notes, and above the vendor and binding notes. The five dashes in front of the note indicate that the note is permanent, has important information, and not to be deleted by staff unless you are 100% sure it has become obsolete. If unsure about whether or not to delete a 5-dash note, ask your supervisor.
The CHECKIN MESSAGE BOX field should be used for:
REMINDER: NEVER DELETE 5-DASH NOTES
REMINDER: ALWAYS DATE AND INITIAL NOTES (mm/dd/yy initials)
We do not edit binding fields For serials purposes, they simply alert us to information regarding the title. There is one exception to this, which will be explained below.
Binding fields inform us about the binding procedure(s) for publications. Binding fields often come in three forms: a Bind INFO field, Bind NOTE field, and a BIND TITLE field.
BIND INFO fields are notes created by binding to aid them when they go to bind a title. They may point out errata, changes in volume/years, bind color, and other pertinent binding information.
BIND NOTE fields provide information about if the title is bound or boxed. Also, if the title is a dropped bound title or dropped box title. As the dropped title is ready for Preservation to review for binding or boxing, the Receiving Specialist updates the BIND NOTE field: "DROP ... TITLE / LAST ISSUE RECD".
BIND TITLE fields provide the title under which the material will be bound. For receiving purposes, this field is helpful because it indicates that a title is bound and, therefore, not limited retention.
Some titles are only held for a short period of time before being discarded. These are known as limited retention items. Binding notes for these titles will be in the BIND INFO fields, and state how long we will hold a publication before discard and provide a record of the discard process.
Because they are only held for specific, often short, lengths of time, limited retention items have some special rules:
Also, some titles are not bound and not limited retention, but are placed in a box for preservation reasons. Boxed titles can be identified by looking in the binding info for notes about box height, when they are boxed, saying that they're boxed, etc.
For instance:
Boxed titles also have some special rules. For example, even though they are kept permanently, we don't collect duplicates of boxed titles for binding and we don't process errata for them.
Finally, if errata or corrections have been noted, this may be reflected in the BIND INFO notes as well.
Most Check-in record notes contain check-in procedures. It is important to read ALL the notes and procedures before checking in an item. Here is an example of a check-in procedures note that contains several steps.
Claim notes have an approved set of abbreviations that can be used when writing notes pertaining to specific claims. They can be deleted when obsolete, most commonly when claimed issues are received and the claim can be resolved.
For a full list of commonly-used abbreviations and what types of situations they apply to, check out the Claim Abbreviations and Claim Notes page on the Access & Claiming StaffGuide.
These can also contain general instructions and useful info when claiming that title, for example:
Contact information notes generally have low priority and thus appear further down in the check-in record note sequence. When adding contact notes, write: CONTACT: followed by the appropriate contact information and (date/initials). Notice the formatting for each example.
Examples:
Contact with Name and Email
Contact with Name and Phone
Contact Phone
There may occasionally be other forms of contact mentioned, such as a contact form on a website.
PENDING DROP [if dropping 2nd copy add word "DUPLICATE"]: "reason" w/ ; [add claims resolved note if claims agent resolved claims]; when last issue recd, send drop notification via Trello; [IF NEEDED: ADD "ESER REVIEW / DECISION ON URL"]; COUNT as 1 [cancel or drop] [PERIODICAL or CONTINUATION] [print,cd-rom, or dvd-rom] [paid or gift] [if dropping 2nd copy add word "DUPLICATE"] primary (d/i)
PENDING DROP: Cancel subscription w/ ; when last issue recd, send drop notification via Trello; COUNT as 1 cancel PERIODICAL print paid primary (d/i)
PENDING DROP: Cancel print w/ ; when last issue recd, send drop notification via Trello; ESER REVIEW; COUNT as 1 drop CONTINUATION print gift primary (d/i)
PENDING DROP DUPLICATE: Cancel microfiche subscription w/; when last issue recd, send drop notification via Trello; COUNT as 1 cancel PERIODICAL microfiche paid primary (d/i)
PENDING DROP: Print ceased w/ ; going online only; when last issue recd, send drop notification via Trello; ESER REVIEW; COUNT as 1 drop PERIODICAL print paid primary (d/i)
PENDING DROP: Ceased publication w/ ; when last issue recd, send drop notification via Trello; RETAIN URL; COUNT as 1 drop CONTINUATION print gift primary (d/i)
For the last issue that we are scheduled to receive for a dropped title, you will check in the issue in normally, then report receipt of the issue via the "pSerials: drop notifications" Trello board. In the board, create a card under "drop notifications for cancellations." As the card title, put the bib number and journal title, then click the green add button. Copy and paste the "PENDING DROP..." note from the check-in record summary into the card as a comment and click "send."
If you receive an issue to a title that has already been dropped, follow the procedure for dropped titles (found under "Receiving--Additional Processing" > "No Record, Internet Only, & Dropped/Canceled Titles" > "General Dropped/Canceled Title Procedures").
1st top note in the check in record: "DROP COMPLETED: delete pending barcoding/binding. (d/i)
2nd top note in the check in record:DROP BACK FROM CAT: drop paperwork sent to JC. COPIES sent to BIND / PER. (d/i)
Another example of a 2nd top note in the check in record: DROP BACK FROM CAT: drop paperwork sent to JC. COPY sent to BIND / ARKCO. (d/i)
Extrapolated record notes alert you that the check-in card has been created using extrapolation. They follow a general format.
The following is a list of common extrapolation notes.
Extrapolation note for Winter is New Year:
In Sierra, quarterly publications that begin the year with the winter issue must be extrapolated. Hence this common note:
Extrapolation note for 9 or 10 month per year publications:
Extrapolation note for academic year publication:
Another type of extrapolation note for academic year publication:
**NOTE: Keep in mind, only update expected dates as far as needed!
Because of their importance, notes to flag specific issues (flag notes) should be asterisked and placed at the top of, or near the top of the check-in record note groups.
Flags are most often used to alert other departments that specific titles are on limited retention and that our holdings only retain a certain number of back issues (hence the retains current 6 months only note in the example).
Many times, flags will alert you to flag the first issue of a new year, or a new volume.
When you encounter a check-in record flag note, be sure to examine the issue to see if it should be flagged, and if so, complete the checking in of a flagged item procedure. **It is a good idea to also look back through the card to make sure the issue (or nearby issue) that was supposed to be flagged was flagged.
Note: For some publications, Sierra has been configured to print a flag label regardless of whether or not that specific issue needs a flag. So, beware, just because a flag label prints, does not mean you should flag the item. Look for flag notes in the check-in record and check-in boxes before flagging. (For this reason we have, for several publications, deleted the flag from the routing module and will just hand-write the flag in the future.)
Identity Fields in Check-In Records
Some serials titles have several different identities, and therefore will have multiple check-in records. For these titles, when creating new check-in records, the identity information should be entered for each record, in order to distinguish that check-in record from other check-in records.For some titles, for example, you would want to put the the current number or date range in an identity field. In other cases, information such as the format, frequency or supplement/subtitle should go in an identity field.
The identity field is helpful to Print Serials check-in personnel in determining the correct record to use to check an item in, which is especially important for newspapers. It also displays to the public in OneSearch, so the public can see which issues we have in that particular date range, supplement, format, or what have you.
Some common examples of publications with multiple identities:
The identity info displays in the record summary as follows:
The identity can also be found in the check-in record notes. Here is an example of how it appears in the check-in record:
Identity fields can be entered into check-in records by selecting the Insert button at the top and then choosing "i Identity."
Internal Notes appear relatively infrequently and relay information about a publication (particularly, subscription information). However, they do commonly appear in titles for which we receive multiple copies of each issue to check in for multiple locations (i.e. a copy for PER, a copy for ARKCO, a copy for Binding, or some such combination). A brief internal note will appear saying "need 3 (or however many) copies" as a reminder.These notes appear below the ~~PARAMETERS note.
For some serials, item records are created when the item is checked in.The check-in records for these titles should have notes that provide details on how to create the item record, appearing as high priority notes (in the 1 position).While the item record creation prompts should come up immediately after the item is checked-in, you may have questions on how to answer the prompts. This is where Item Record creation notes prove helpful.**It is a good idea to copy and paste these notes onto a word doc before clicking the check-in button, so you can see the notes while going through the item record creation process.
The notes follow the format: which tally sheet to use/Itype number/Status/barcode or not barcode; other details (date/initials).
Example:
A breakdown of the notes:
Titles that are not kept permanently are known as limited retention titles. Below are the Approved Limited Retention Notes for Print Resources. (These notes will often be found within a Flag note).
Approved Limited Retention Notes for Print Resources
Current issues in PERIODICALS ROOM. (or another location)
Current issues retained until microfilm (or microfiche) received.
Current issues retained until microfilmed.
Current issues retained until microfilmed, see A 630.5 F22.
(or other call number)
Retains current 2 month only
Retains current 3 month only
Retains current 6 month only
Retains latest (or current) year only
Retains latest (or current) 2 years only
Retains latest (or current) 5 years only
Retains latest edition only
Retains latest 2 editions only
Latest edition in REFERENCE (or other location)
Latest 2 editions in REFERENCE (or other location)
NOTE: Use the word "current" for titles published more frequently than annually. Use the word "latest" for titles published annually or less frequently.
**Please refer to the Serials page of the Cataloging and Acquisitions StaffGuide for approved limited retention notes.
Message Notes are timely and important notes that will create a message box as soon as a user opens a specific check-in record. They are most often used to alert the check-in worker to specific instructions with the journal that require close attention, such as passing the issue directly to a specific staff member or department rather than sending it to the collection. Check-in record messages should be used sparingly, and only in cases when it is necessary to alert a user to important check-in information.
Example:
Message box created with check-in record note:
Message notes can be created by right clicking on any check-in record note (ctrl-I), highlighting insert field, and then inserting a message note field (m).
When a message note is inserted into the check-in record notes, it will appear at the bottom of the check-in record note group.
Parameters note:
Oftentimes, you can find claiming restrictions following parameters in the same field. This information is usually obtained from EBSCONET or FOKUS in their title information pages, restrictions specified on a publisher's website, or some other form of communication from the publisher. These notes give you helpful information for claiming purposes, such deadlines (i.e. must claim within 3 months after publication), limitations on the number of issues that can be claimed per year, or what information is needed when submitting a claim. More information on claiming restrictions can be found in the Vendor Claims page of the Access and Claiming StaffGuide.
Publication schedule notes alert you to the frequency of publication. Some publication schedules are complex and change often, so we attempt to keep record notes regarding those changes. These notes alert us to possible frequency changes and guide us in how to create a check in card or add boxes for the following year(s). Early in the year, pay close attention to the publication schedules often found in fine print near the back or front of an issue. For journals that always follow a simple/predictable schedule, i.e. monthly, weekly, bimonthly, etc., there is no need to create pub schedule notes. For journals that have more complex schedules, i.e. mostly monthly with one or more combined months, it is best to note that in the check-in record. For most of these journals, only the current year is needed, but with some, it is best to keep the pub schedule history for two or more years if it contains info that might be useful in the future; for instance, if the publisher has stated that the publication schedule might change at some point in the future.
Publication schedule notes follow a specific format. They appear as high priority note (usually 1 or 2). They begin with the prompt: PUB SCH (year): the schedule per (the date and issue number you are pulling the information from) and (D/I).
NOTE: This publication changes frequently. The third PUB SCH note was not obtained from an issue, but from the vendor, Harrassowitz.
NOTE: Give journals and forward any e-mails, publisher correspondence, etc., that indicate new frequencies or pending frequency changes to the Serials Processing Specialist for review.For more information on how to process frequency changes, go here.
NOTE: Frequency changes will be under notes called "FREQ CHG" and not "PUB SCH" notes.
Top notes are temporary, timely, and must be seen and reviewed prior to check-in. Because of their important but temporary nature, they do not receive numbering, but appear at the top (highest priority) of check-in record notes and may be offset with asterisks to denote importance.
Top notes are often PENDING ANYTHING (FRQ, vendor or title changes, as well as drop pendings, new set-ups, etc). Some examples include:
Drop Notes:
New Setup:
Sometimes supplements are known are to accompany certain titles. These titles will include instructions on how to process supplements. These notes come in many forms and you will find several examples and descriptions on the page for supplement check-in procedures.
See the URLs page for information on what types of URLs Serials lists in check-in record notes and how to format their notes, as well as information on URL testing and maintenance.
Vendor notes provide information about vendors in the check-in record.
Types of Vendor Notes:
VEN.ADDR.(q): Vendor address or other contact information.
VEN. TITLE#(f): The title's number connected to our subscription in the vendor's system (i.e. FOKUS). Sometimes useful for claiming purposes.
VEN. NOTE (v): Any other pertinent information.
Examples of vendor notes:
Note that vendor addresses only need to be checked or updated when we need to send a letter to a vendor via physical mail. This most commonly occurs when we are asked to mail back a receipt acknowledgement card for a journal received or when we must send a special letter to a publisher in regards to a claim. The address can be verified on the mailing envelope, inside the issue near the masthead, or on the publisher's website. If you need to update the address, follow the instructions for Processing Address Changes.
Note: If you see UARK Serials Department contact information in a vendor note, delete it. This was for an old procedure that we do not follow anymore, so the contact information is not needed. Sometimes there will also be a corresponding internal note that also needs to be deleted.
Example: VEN. NOTE: Serials Department 479-575-5415
5-DASH NOTES
5 dash notes will be entered below the parameters and current claim notes, and above the vendor and binding notes. The five dashes in front of the note indicate that the note is permanent, has important information, and not to be deleted by staff unless you are 100% sure it has become obsolete. If unsure about whether or not to delete a 5-dash note, ask your supervisor.
Examples of situations when we enter 5-dash notes include frequency changes, vendor changes, checking in a damaged copy when a replacement copy is not available, not published issues, out of print issues, and unavailable issues. Below are some examples of what types of info the notes include in these situations:
Frequency changes, vendor changes, etc.:
Damaged issue circulating due to unsuccessful claiming attempts for replacement:
Not published, unavailable, out of print, etc.:
Other relevant info (including, but not limited to these types of situations):