Notes
Slide Show
Outline
1
Virtual Browsing
via
Deeplinked Catalog Searches
  • Scott Warren
  • Librarian for the Physical and Mathematical Sciences
  • Research and Information Services
  • NCSU Libraries
2
Why browsing?
  • Poorly replicated in most online environments


  • Access to collection subsets


  • Lists are easy to use


  • Takes the stacks to the remote patron


  • Great for specialist exploring large collection


3
Advantages
  • Dynamic content
    • Manually created, but not manually maintained


  • Opens up print collection


  • Uses power of LCSH and LC call numbers


  • Easy editing/low maintenance for subject specialist


  • Guarantees something relevant is found
4
 
5
 
6
 
7
 
8
 
9
 
10
 
11
 
12
 
13
 
14
 
15
 
16
 
17
 
18
 
19
 
20
 
21
How does it work?
  • Javascript makes creating menus easy


  • Forms make the dropdown menus


  • Search syntax complex, but easily edited


  • Very little coding is required
22
 
23
 
24
"<FORM NAME="form1..."
25
 
26
 
27
"LC subject heading search"
28
 
29
Advantages
  • Dynamic content
    • No updating necessary as collection changes


  • Easy editing/No large scale systems maintenance


  • Opens up print collection


  • Uses power of LCSH and call numbers
    • Data already in place
30
But…
  • Idiosyncratic
  • One at a time production
  • Not comprehensive across collection
  • Relies on creating web page for each new implementation
  • Doesn’t scale well in this production mode
  • Buried by library’s site architecture
31
Compare to Michigan’s
‘High-level Browse’ project
  • Similarities
  • Based on LC classification schedules
  • Uses data that already exists
  • No changing of individual catalog records
  • Maintenance does not require systems help
  • Focus on collection at hand





32
 
33
 
34
 
35
 
36
Compare to Michigan’s
‘High-level Browse’ project
  • Differences
  • Mine not global in scope
  • Mine placed at point of need/Grassroots solution
  • ‘Tertiary’ level browsing


  • Michigan maps topics to multiple call # ranges
  • I map LCSH/LC#s to topics 1-to-1
  • Based on both LC # and LCSH


  • No MySQL, perl, or php







37
 
38
 
39
 
40
 
41
Automated/Scaling up???
  • Could LCSH terms/call #s be ‘selected’ or ‘harvested’?


  • Search URL generated with correct LCSH appended


  • LCSH and URL added to a table/spreadsheet where subject specialist creates menu term


  • Table is mapped to menu on public page. Form already created.


42
 
43
 
44
 
45
 
46
Frequency distributions of call numbers for LCSHs

  • Even within an LCSH, there is location ‘drift’
  • One primary LC #, but many others too


  • LCSH      ‘differential equations partial’
      • QA377 (main #)
      • QC20.7
      • QA3
      • TA418
      • TA347
      • QA1
      • QC157
      • QA11.2

47
Frequency distributions of call numbers for LCSHs
  • Not sorting the actual titles by call #


  • But producing distributions
    •  top 3-5 call number ‘areas’ for browsing

  • Histogram??
    • SciFinder Scholar, Web of Science

48
 
49
 
50
 
51
 
52
 
53
 
54
 
55
Advantages
  • Dynamic content
    • No updating necessary as collection changes


  • Easy editing/No large scale systems maintenance


  • Opens up print collection


  • Uses power of LCSH and call numbers
    • Data already in place
56
Contact me
  • Scott Warren


  • Scott_warren@ncsu.edu (email)


  • Scottyref (AIM)


  • 919-513-0303


  • http://www.lib.ncsu.edu/risd/staff/warren