Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
serials_prediction_patterns [2009/03/12 18:15]
ldegozzaldi
serials_prediction_patterns [2020/09/24 20:28]
annk removed
Line 1: Line 1:
-(Aleph Workflow--Collection Services Division)\\  +====== **Under Review for FOLIO Migration** ====== 
-(Working Draft, 3/12/09)  IN PROCESS!!!+ --- //​[[annk@umass.edu|Questions:​ Ann Kardos]]//
  
 ====== Serials Prediction Patterns ====== ====== Serials Prediction Patterns ======
  
-Patterns ​will be created for **periodicals only** (either newly-cataloged or previously-owned which are currently received but have been reported by Acquisitions as having no pattern or an incorrect pattern). ​ We will not be creating patterns for serials.+Prediction patterns ​will be created for **periodicals only** (either newly-cataloged or previously-owned which are currently received but have been reported by Acquisitions as having no pattern or an incorrect pattern). ​ We will not be creating patterns for serials.
  
 ===== Useful references ===== ===== Useful references =====
Line 31: Line 31:
 NOTE: DO NOT use 99 with whole (continuous) numbering systems! NOTE: DO NOT use 99 with whole (continuous) numbering systems!
 </​file>​ </​file>​
-  - Set claiming pattern. Check arrival dates of previously checked-in items, and of item in hand. Refer to Innopac CHECKIN documents if needed. Estimate the difference between the dates on the issues and their arrival, and enter the number of days in the First Claim field. Leave following claims at 90 unless instructed otherwise.+  - Set claiming pattern. Check arrival dates of previously checked-in items, and of item in hand. Refer to Innopac CHECKIN documents if needed. Estimate the difference between the cover dates on the issues and their arrival, and enter the number of days in the First Claim field. Leave following claims at 90 unless instructed otherwise.
   - Make sure Print Label box is checked, and Send Claims is set at "​Yes"​ unless instructed otherwise.   - Make sure Print Label box is checked, and Send Claims is set at "​Yes"​ unless instructed otherwise.
  
Line 40: Line 40:
 ==== HOL Record ==== ==== HOL Record ====
  
-Most periodicals for UMDUB (Main Sublibrary) will have unbound and bound issues shelved in the same location, requiring **one** HOL record with collection UPER (bound periodicals). UMSCI (Science Sublibrary) will require **two** HOL records for shelving unbound and bound issues in separations, with collection UPERC (unbound periodicals) and collection UPER (bound periodicals). ​ The pattern will be entered into the UPER HOL for Main, and into the UPERC HOL for Science.+Most periodicals for UMDUB (Main Sublibrary) will have unbound and bound issues shelved in the same location, requiring **one** HOL record with collection UPER (bound periodicals). UMSCI (Science Sublibrary) will require **two** HOL records for shelving unbound and bound issues in separate locations, with collection UPERC (unbound periodicals) and collection UPER (bound periodicals). ​ The pattern will be entered into the UPER HOL for Main, and into the UPERC HOL for Science.  __UMDUB Exception__:​ The unbound issues of approximately 90 popular magazines and newspapers will be shelved on the reading area on the 5th floor, in a separate location from the stacks. ​ These will also require **two** HOL records, with collection UPERC (unbound) and collection UPER (bound).
 <​file>​ <​file>​
-NOTE: Approx. News& Mag. titles ​in UMDUB will need UPERC HOL's. See link below+NOTE: Approx. ​90 UMDUB News & Mag. titles will need UPERC HOL's. See link. 
 </​file>​ </​file>​
 +
 +
 +[[serials_popular_magazines_and_newspapers_list]]
 +
  
 Before opening pattern: Before opening pattern:
Line 55: Line 59:
   - Harvard patterns will have a 853 with a beginning Subfield 8. Often it is easier to delete them, as the starting issue and year will be incorrect. ​ However, they may also be edited instead of adding a new pattern with "​Expand from Template"​ if preferred.   - Harvard patterns will have a 853 with a beginning Subfield 8. Often it is easier to delete them, as the starting issue and year will be incorrect. ​ However, they may also be edited instead of adding a new pattern with "​Expand from Template"​ if preferred.
   - Open the pattern by clicking Edit on bar at the top of screen, and choosing "​Expand from Template."​   - Open the pattern by clicking Edit on bar at the top of screen, and choosing "​Expand from Template."​
-  - Choose appropriate frequency from left-hand column, and press Open.  An 853 fieldand an 853X field will appear automatically in the HOL record. ​ The 853 field defines the values to be entered in the pattern, and the 853X field fills them in.  For titles that don’t have straightforward frequencies,​ the information in the 853 field will have to be manipulated. ​ Enter the information appropriate for the title. ​ Information for basic patterns follows; more subfields exist for smaller levels of enumeration and chronology and more complicated situations, see the SERIALS MANUAL ​(mentioned above). +  - Choose appropriate frequency from left-hand column, and press Open.  An 853 field and an 853X field will appear automatically in the HOL record. ​ The 853 field defines the values to be entered in the pattern, and the 853X field fills them in.  ​(For titles that don’t have straightforward frequencies,​ the information in the 853 field will have to be manipulated.
- +  Enter the information appropriate for the title. ​ Information for basic patterns follows. (More subfields exist for smaller levels of enumeration and chronology and more complicated situations, see the SERIALS MANUAL mentioned above). 
-Subfield a=first-level enumeration,​ most often vol. of first issue of start year. +    ​* ​Subfield a=first-level enumeration,​ most often vol. of first issue of start year. 
-Subfield b=second-level enumeration,​ most often no. of first issue of start year. +    ​* ​Subfield b=second-level enumeration,​ most often no. of first issue of start year. 
-Subfield i=year of starting issue. +    * Subfield u=issues published per year (equal to or less than frequency). 
-Subfield j=month of starting issue. +    * Subfield v=whether 2nd level of enumeration is repeating or continuous. 
-Subfield ​3=date first issue of start year is published. ​ ​(Usually we’ve been making this the cover date of the first issue with 01 entered for the day unless otherwise specifiedbut it can also be the “expected ​date”—useful for cases when expected ​dates are earlier ​than the issue dates) +    * Subfield i=year of starting issue. 
-Subfield 9=link to Subscription. ​ This is required for the pattern to work.  If only one HOL record is present, when the pattern is saved to Server, this subfield will automatically be entered.  ​But if two HOL records are present ​(for two different locations), we have to manually enter this number. ​ It can be found next to [S] Subscription in the Serials mode.  ​Usually ​it is copy=10which has to be entered as 00010. ​ Occasionally we’ll get a copy=20, entered as 00020. +    ​* ​Subfield j=month of starting issue. 
- +    ​* ​Subfield ​w=frequency. 
-590 Note.  Except in weird cases where the 590 note which appears with the pattern might be helpful (as edited to fit our specific requirements),​ delete the 590.  Save the HOL record to the Server. +    * Subfield x=start ​date for next sequence (if middle ​of calendar ​year). 
- +    * Subfield y=seasons, months etc. published, omitted or combined. 
-Push to Acquisitions Module. ​ Hit the stack of books (Serials).  ​Go to [L] Subscription List, 4. HOL Links. ​ Make sure that the current subscription is highlighted,​ as well as the current HOL record (in which the pattern has been inserted. ​ Hit Open All on right side of top screen. ​ A small hourglass will appear and blink off, signaling that the pattern has been constructed. ​ If you get an error message, check to make sure the HOL record is linked to the Subscription,​ and that the subfield 9 is in place. +    * Subfield 3=cover date of first issue to be generated by the pattern, ​with 01 entered for the day. (ALEPH adds this subfield information to the figure entered into the "First Claim" field under [L] Subscription List3. Subscription Info. (2) (see above), to produce ​the "date expected" which displays in the OPAC.  Subfield 3 can be manipulated if necessary, for example, if issues ​are arriving sooner ​than their cover dates.
- +    ​* ​Subfield 9=link to Subscription. ​ This is required for the pattern to work.  If only one HOL record is present, this subfield will automatically be entered ​upon saving changes to the HOL.  ​However, ​if two HOL records are present for two different locations, we have to manually enter this number. ​ It can be found next to [S] Subscription in the Serials mode.  ​For new periodicals ​it will be copy=1entered as 00001; for previously-owned pers it will be copy=10, ​entered as 00010. ​ Occasionally we’ll get a copy=20, entered as 00020. 
-V. Go to [K] Check In at left side of screen, and press the tab for 2. Expected/​Not Arrived. ​ “Expected items” generated by the pattern should appear.  ​Compare to the Innopac boxes and check to be sure they make sense.+  ​- ​590 Note.  Except in weird cases where the 590 note which appears with the pattern might be helpful (as edited to fit our specific requirements),​ delete the 590.  Save the HOL record to the Server. 
 +  ​- ​Push to Acquisitions Module. ​ Hit the stack of books (Serials).  ​Click on [L] Subscription List, and hit Open All on right side of top screen. ​ A small hourglass will appear and blink off, signaling that the pattern has been constructed. ​ If you get an error message, check to make sure the HOL record is linked to the Subscription,​ and that the subfield 9 is in place. 
 +  ​- ​Go to [K] Check In at left side of screen, and press the tab for 2. Expected/​Not Arrived. ​ “Expected items” generated by the pattern should appear.  ​Make sure that pattern has been properly generated. 
 +  - De-dupe any “expected items” which have already been checked in.
  
-A. Delete all “expected items” which have already been bound. ​ (Bound items should appear under 1. All, in the Check In mode, as well as under [M] Item List accessed lower down in the left-hand column.) ​+===== Examples =====
  
-B. Arrive all “expected items” which have already ​been checked in but not yet bound.+Following is a link to screenshots of how various patterns ​have been generated, including some more complex situations.
  
 +[[serials_prediction_patterns_examples]]
  
  
  
  
 +//​[[lucyd@library.umass.edu|Primary contact: Lucy deGozzaldi]]//​.
[unknown link type]Back to top
www.chimeric.de Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0