The number of passages through designated physical entry points of a library facility recorded during a specified time interval by automatic sensors or manual counting procedures. Each recorded passage through the counted threshold is treated as one unit; the measure indicates flows across an entrance but does not, by itself, identify unique individuals, duration of stay, or on-site activities.

Principle

Gate Count provides a coarse, time‑indexed measure of threshold crossings that can reveal patterns of physical presence at facility access points but cannot substitute for measures of individual attendance, engagement, or service use.

Demonstration

Illustrative Scenario → Situation: A library operates two staffed doors and one automated turnstile. Recognition: Sensors log every passage through each counted entrance. Action: Staff aggregate counts for a seven‑day period. Consequence: Management identifies daily peak entry periods and adjusts staffing on the busiest days. The counts guide scheduling but do not reveal whether entrants remained, attended programs, or used collections.

Misapplication

Mistaken Interpretation: Treating Gate Count as the number of distinct visitors. Why plausible: both are 'people' metrics and counts are often used for reporting. Semantic Error: Equating threshold passages with unique users ignores re‑entries, staff movements, tailgating, and counting errors. Corrected Interpretation: Gate Count measures passages, not unique individuals or engagement levels.

Consequence

Operational decisions (staffing levels, opening hours, cleaning schedules), capacity planning and high‑level trend reports commonly rely on Gate Count. Because it measures flows rather than engagement, using it alone to allocate service resources or evaluate program impact can misdirect resources if not combined with complementary metrics.

Reversal

When entrances are multiplexed, when sensors suffer false positives/negatives, or when entry control is bypassed (tailgating, unlocked doors), Gate Count can substantially overestimate or underestimate physical use. In contexts where services are primarily digital, Gate Count ceases to represent user demand.

Boundary

Clearly Within: Automated turnstile sensor recording every passage through a counted door during a day. Boundary Case: Counts that include staff and volunteers — additional filtering is required to approximate patron passages. Clearly Outside: Web page visits, catalogue queries, or remote reference interactions — these are not captured by Gate Count.

Semantic Tension

Accuracy/Granularity ↔ Privacy: Increasing granularity (e.g., linking counts to identifiers to estimate unique visitors) improves interpretability but raises privacy and data‑protection concerns that libraries must manage.

Synthesis

Gate Count is best understood as a flow metric for entrances: useful for detecting temporal patterns and capacity stress at thresholds, but inherently limited as a proxy for individual attendance or service uptake unless combined with filtration, cross‑referencing, or separate measures.