Idiomatic Access Reports
description
Transcript of Idiomatic Access Reports
![Page 1: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/1.jpg)
1
Idiomatic Access Reports
ELSUGOctober 10, 2008
Cathy SalikaCARLI Consortium of Academic and Research Libraries in Illinois
![Page 2: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/2.jpg)
2
Learning Access is like learning a language.
There are idioms.Things you use repeatedly.They become second nature.They build fluency.They save time.
![Page 3: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/3.jpg)
3
This series of tables is very common
What does this query do?
Which tables aren’t needed?
![Page 4: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/4.jpg)
4
We can get rid of MFHD_MASTER.Queries are more efficient if you get rid of extra tables.Here’s a better query.
![Page 5: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/5.jpg)
5
We could do this with even fewer tables…
… but I wouldn’t.I don’t trust the BIB_ITEM table.
![Page 6: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/6.jpg)
6
Bug 16384-15158
Sometimes when you relink a MFHD to a different bib, BIB_ITEM gets deleted, not changed.
In the clients, the item can’t be searched by barcode.
In queries, your numbers get unreliable.
It’s not a big deal, but I avoid it.
![Page 7: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/7.jpg)
7
Bug 16384-15158Here’s a query that will tell you if you have any missing BIB_ITEM records.
If you do, please “me too” bug 16384-15158.You can fix affected bibs by relinking the MFHD to a different bib, then relinking it to the bib you want it on.
![Page 8: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/8.jpg)
8
Another reason to get rid of extra tables from your queries
What could go wrong?
![Page 9: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/9.jpg)
9
ITEM_BARCODE isn’t needed.If any items in reference had to be re-barcoded, they’ll appear twice in this query.
Likely? Yes.A big deal? Depends on how many
barcodes you’ve had to replace.
But tidy up and you won’t have to figure out why your counts don’t jive.
![Page 10: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/10.jpg)
10
Another problem caused by extra tables in a querySomeone asked about the prepackaged report “Circulation Transactions by Dewey Decimal Classification“ on Voyager-L recently.
![Page 11: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/11.jpg)
11
Basic Acquisitions Tables: POs
Bib Tables
Invoices
![Page 12: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/12.jpg)
12
Basic Acquisitions Tables: Invoices
PO Tables
![Page 13: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/13.jpg)
13
Which location should I use?
TEMP_LOCATION in ITEM the location used for circ policies
PERM_LOCATION in ITEMthe location used for circ policies if TEMP_LOCATION isn’t filled it
![Page 14: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/14.jpg)
14
Which location should I use?How to get the current item location:
![Page 15: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/15.jpg)
15
Which location should I use?LOCATION_ID in BIB_LOCATION is the
location that is used for location limiting.It SHOULD be the same as this…
If you move items around a lot, it probably is… 99% of the time.
![Page 16: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/16.jpg)
16
Which location should I use?
Bug 83671 was fixed in Voyager V6.1, but thedata in the table haven’t been cleaned up yet.
I just avoid BIB_LOCATION in queries.
![Page 17: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/17.jpg)
17
Which location should I use?Remember that Voyager doesn’t force you tokeep the item location and MFHD location insynch.
![Page 18: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/18.jpg)
18
Which Call Number should I use?There are lots to choose from !
The choice depends on your library’s data.
![Page 19: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/19.jpg)
19
Which Call Number should I use?
In MFHD_MASTER
DISPLAY_CALL_NO is 852 subfields k, h, i, m
NORMALIZED_CALL_NO is 852 subfields h, i, m
852 $k is the call number prefix.
Does your library use prefixes?
![Page 20: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/20.jpg)
20
Which Call Number should I use?In MFHD_MASTER, DISPLAY_CALL_NO isformatted with a space between subfields.
$h783.9$iB122c 7983.9 B122c
$hM2117$iB122c M2117 B122c
![Page 21: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/21.jpg)
21
Which Call Number should I use?In MFHD_MASTER, the format of NORMALIZED_CALL_NO depends on the classification.
(More on this in a moment.)
![Page 22: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/22.jpg)
22
Which Call Number should I use?In MFHD_MASTER, CALL_NO_TYPE is usually the sameas the 852 first indicator. They tell you the
classification.
0 = LC 5 = Shelved by title1 = Dewey 6 = Shelved separately2 = NLM 7 = Classification specified in $23 = SuDoc 8 = Other4 = Shelving number
EXCEPT, when Voyager is parsing the call number, if its
algorithms fail, CALL_NO_TYPE is changed to 8.
![Page 23: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/23.jpg)
23
Which Call Number should I use?Most libraries use a mix of classifications, including some home-grown ones.
![Page 24: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/24.jpg)
24
Which Call Number should I use?
For display, always use DISPLAY_CALL_NO.
For sorting, always use NORMALIZED_CALL_NO.
For criteria, if you want the call number prefix from 852$k, use DISPLAY_CALL_NO.
For other criteria…
![Page 25: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/25.jpg)
25
Criteria for LC numbersNORMALIZED_CALL_NO begins with the 1-3 letter class code, followed by the class number right-justified in a 5-digit field.ML^^410
M^2117
M^^^^2
KFA^^123
The rest of the call number follows, separated with more spaces.
![Page 26: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/26.jpg)
26
Criteria for LC numbersIn LCCLASS_VW (example: ML410)FIRSTLETTER M
CLASS ML
CLASSNUMBER 410
LONGCLASS ML 410
This works only whenCALL_NO_TYPE = 0 !
example: KNN122FIRSTLETTER KCLASS KNNCLASSNUMBER 12.2LONGCLASS KN 12
It doesn’t work at all for numbers with 3-letter class codes, such as foreign law! (Bug 82369)
![Page 27: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/27.jpg)
27
Criteria for Dewey numbersNORMALIZED_CALL_NO begins with the complete Dewey class. Spaces are inserted after the class, before the Cutter.783.9 W678
In DEWEYCLASS_VW (example: 783.9W678)CLASS 783
LONGCLASS 783.9
DEWEYCLASS_VW works only when CALL_NO_TYPE = 1 !
![Page 28: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/28.jpg)
28
Formatting: Patron Names
![Page 29: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/29.jpg)
29
Formatting: Patron Names
![Page 30: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/30.jpg)
30
Formatting: CurrencyCurrency fields in Voyager are expressed in cents, pence or other small units.
![Page 31: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/31.jpg)
31
Formatting: UNICODE Fields
But you have to know which fields are encoded in UNICODE.
![Page 32: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/32.jpg)
32
Formatting: UNICODE FieldsIn EL Commons, there is (or will be soon)“CARLI’s Version of the Voyager Data
Dictionary for V6.1 to V7.0”
BIB_TEXT p. 11, 14, 27, 33, 36The starred fields in this table are in UTF-8. bib_id number *author character 255 begin_pub_date character 4 bib_format character 2 *coden character 6
![Page 33: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/33.jpg)
33
Date/Time FieldsWhat does this query do?
![Page 34: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/34.jpg)
34
Date/Time Fields
Not very useful…
![Page 35: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/35.jpg)
35
Date/Time Fields: Better!
Circulation Transactions (Charges) includes both currently charged and discharged transactions.
![Page 36: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/36.jpg)
36
Date/Time Fields: Good!
DateValue chops off the time, leaving just the date.
![Page 37: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/37.jpg)
37
Date/Time Fields: Good!
![Page 38: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/38.jpg)
38
Another way to mess up this simple little query…
Moral: Always count a field that you’re sure is filled in. I usually count an _ID field that I’ve used for linking.
![Page 39: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/39.jpg)
39
One more moral…Save your queries, especially the ones you use for routine statistics.
Sometimes it’s more important to be
consistent than to be correct
![Page 40: Idiomatic Access Reports](https://reader033.fdocuments.in/reader033/viewer/2022061420/56815a83550346895dc7f1f8/html5/thumbnails/40.jpg)
40
Thank you!