Notes
Slide Show
Outline
1
Making Floating Collections Work
  • John Goodyear
  • ILS Analyst
  • johng@multcolib.org


  • Jennifer Steward
  • Circulation Analyst
  • jennifes@multcolib.org


  • Multnomah County Library


2
Floating Collection
  • Base product


  • Uses first 2 letters of location code
    • Branch code


  • Floats to first within the location served
3
Retaining Branch Information
  • Floating Collection Shelf Assignment


    • Only top level location changes
    • first 2 letters of code


    • Shelving part of location remains
    • 3rd to 5th positions of code
    • Must be consistent
4
Library Planning
  • What and where


  • Workload


  • Space


  • Weeding


  • Acquisitions/Selections
5
What and where
  • We chose
    • Small collections
    • High Demand
    • High Circ
    • All libraries
    • Exclude administrative locations
    • Exclude special collections
    • Add more later
6
Workload
  • Object is to decrease overall workload


  • Don’t merely shift work
    • Less work for materials movement
    • More work for reference
7
Space
  • This is the big one


  • Items that were in crates now on shelf


  • The balls land when the juggling stops


  • Count items and measure shelves


  • What will you do with overflow
8
Weeding
  • Start clean


  • Train staff to keep it clean


  • Guidelines for all staff to follow


  • If you own the item, you own the decision
9
Acquisitions/Selections
  • Don’t over-buy


  • Don’t buy for every location


  • More titles, fewer copies
10
Innovative setup
  • You do the Float Determiner Table


  • Innovative will need to set up Shelf Assignment piece


  • May need patches applied to deal with alphabetical issues of Location Served
11
Location patterns
12
Wrong
13
Float determiner table
  • Keep spreadsheets


  • Table reads from bottom


  • Avoid Roach Motel syndrome
    • Items float in they, never float out


14
 
15
Item location

    • xx* means any rule applies to any item in  locations beginning with  al, be, etc.


    • ? Means rule applies to any item in any location


    • x* will not work, it must be a 2 letter branch code
16
Terminal location

    • Controls whether Items float into locations served by these terminal locations


    • ? Applies any terminal loc


    • ad is specific terminal location
17
Item type

    • Rule applies to specific items types


    • Rule applies to all items types
18
Itypes
19
Will not float
  • First 4
    • Item from any location
    • Any item type
    • Checking in at these 4 specific terminal locs
20
Will not float
  • Item from x location
    • Specific item types
    • Checking in at any location
21
Will float
22
Will float
  • Item locations indicated
  • At any terminal location
  • For these specific item types


23
Will not float
  • Item locations lo, any terminal and any item
  • Any item loc, any terminal loc and any item type not covered by any previous line will not share
24
 
25
 
26
The final surprise
  • Shipping location
    • It is and it isn't a location
    • No way to block circulation in, location will not show up in table to be able to block
    • System sees it as a location and will float material in
27
Ownloc
  • Owning location field in item record tells you where the item started out
  • Static, variable field, no data control
  • We don’t use
28
Recent tweaks