FPDS Query Library
About Us
Contact Us

Generic Boolean01

Numeric flag in the Other Transaction IDV generic boolean group that records the value of the first reusable boolean indicator attached to the award. It functions as a binary attribute, typically stored as 0 or 1, for FPDS filtering and analysis.

Family: Other Transaction IDV
Category: Generic Tags
Data Type: numeric
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01
Title
Generic Boolean01
FPDS Path
OtherTransactionIDV/genericTags/genericBooleans/genericBoolean01
Description
Numeric flag in the Other Transaction IDV generic boolean group that records the value of the first reusable boolean indicator attached to the award. It functions as a binary attribute, typically stored as 0 or 1, for FPDS filtering and analysis.
Business Meaning
This field matters because generic booleans in FPDS often carry program- or reporting-specific attributes that help analysts segment awards, identify special handling, and support repeatable procurement workflows. Even when the business meaning is not self-describing, the presence or absence of the flag can be useful for isolating subsets of Other Transaction IDVs in trend, compliance, or portfolio analysis.
Example Value
0
Observed Non-Null Count
6,280

FPDS Compare

FPDS Query Variable
content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01
FPDS XML Path
OtherTransactionIDV/genericTags/genericBooleans/genericBoolean01
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionIDV/genericTags/genericBooleans/genericBoolean01' into the SQL-ready variable 'content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building

Common Usage

  • binary filtering of Other Transaction IDV records
  • grouping awards by a generic attribute flag
  • building reusable award-segmentation logic

Common Mistakes

  • assuming 0 and null mean the same thing
  • inferring business meaning from the field name alone

Query Guidance

Use exact numeric predicates such as = 1 or = 0, and include IS NULL checks when missing values matter. When joining or aggregating, treat the field as a binary indicator and validate the distribution before using it as a business rule.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01 AS generic_boolean01
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01 IS NOT NULL
LIMIT 25

Aggregate total

SELECT
    sum(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01) AS total_value
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01 IS NOT NULL

Distribution overview

SELECT
    min(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01) AS min_value,
    avg(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01) AS avg_value,
    max(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01) AS max_value,
    count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean01 IS NOT NULL

Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.