FPDS Query Library
About Us
Contact Us

Generic Boolean04

Numeric generic boolean flag within the Other Transaction IDV record, stored under Generic Tags. It captures one reusable yes/no-style attribute for the award, typically represented as 0/1 rather than a text label.

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__genericBoolean04
Title
Generic Boolean04
FPDS Path
OtherTransactionIDV/genericTags/genericBooleans/genericBoolean04
Description
Numeric generic boolean flag within the Other Transaction IDV record, stored under Generic Tags. It captures one reusable yes/no-style attribute for the award, typically represented as 0/1 rather than a text label.
Business Meaning
This field matters because Generic Tags are used to carry analysis-specific indicators that support filtering, grouping, and workflow logic across Other Transaction IDVs. It can help analysts segment awards by a custom status or characteristic when standard FPDS fields do not capture the needed distinction.
Example Value
0
Observed Non-Null Count
6,280

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter Other Transaction IDVs by a custom yes/no attribute
  • Group awards for reusable reporting logic
  • Create inclusion or exclusion flags in analytic workflows

Common Mistakes

  • Assuming the field has a universal business meaning without checking the extract or data dictionary
  • Treating numeric codes as continuous measures instead of categorical flags

Query Guidance

Use equality filters such as = 1 or = 0, and aggregate with COUNT or SUM only after confirming the coding convention. In SQL, cast or compare explicitly rather than relying on truthy behavior, and pair this field with related generic tags if you need the full business interpretation.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean04 AS generic_boolean04
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean04 IS NOT NULL
LIMIT 25

Aggregate total

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

Distribution overview

SELECT
    min(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean04) AS min_value,
    avg(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean04) AS avg_value,
    max(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean04) AS max_value,
    count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean04 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.