# Identifying Items With Inconsistent Location Code \<–\> Call Number Combinations

**URL:** https://forum.innovativeusers.org/t/identifying-items-with-inconsistent-location-code-call-number-combinations/2383
**Category:** Sierra Repository
**Tags:** sierra-sql, sql, item-record, audience, discrepancy
**Created:** [March 26, 2025, 8:05pm UTC](https://forum.innovativeusers.org/t/identifying-items-with-inconsistent-location-code-call-number-combinations/2383 "2025-03-26T20:05:18Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![bgaydos](https://forum.innovativeusers.org/user_avatar/forum.innovativeusers.org/bgaydos/32/1045_2.png) [@bgaydos](https://forum.innovativeusers.org/u/bgaydos)
#### Post date: [March 26, 2025, 8:05pm UTC](https://forum.innovativeusers.org/t/identifying-items-with-inconsistent-location-code-call-number-combinations/2383/1 "2025-03-26T20:05:18Z")

</div>

[Inconsistent Item Audience Report.sql](https://forum.innovativeusers.org/uploads/short-url/r3WwzuW6hxgNH28se1gmHL9fgjH.sql) (5.2 KB)

While preparing responses to the annual State [library] report earlier this week, I became aware of a large number of inconsistencies in the intended audience of our items as encoded in the Location Code versus the Call Number.&nbsp; I wrote this query this morning to identify these items and am posting it here in case anyone else can benefit.

You’ll notice a reference to the letters `g` or `t` to indicate `Teen`.&nbsp; The `g` is particular to one of our branches and you may ignore this potentially confusing comparison.

One common false positive appears to be in the area of serials, whose call numbers omit a leading J or YA in many cases despite their intended audience.&nbsp; Maybe this is normal, but hey I’m not a librarian so I wouldn’t know.&nbsp; I’ll check with our serials cataloger tomorrow.&nbsp; Enjoy.