FPDS Query Library
About Us
Contact Us

Generic Boolean03

Numeric indicator stored in the Other Transaction IDV generic boolean slot 03 within the Generic Tags section. It functions as a reusable flag value for this FPDS record rather than a core contracting attribute, and the observed value is typically coded such as 0/1.

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__genericBoolean03
Title
Generic Boolean03
FPDS Path
OtherTransactionIDV/genericTags/genericBooleans/genericBoolean03
Description
Numeric indicator stored in the Other Transaction IDV generic boolean slot 03 within the Generic Tags section. It functions as a reusable flag value for this FPDS record rather than a core contracting attribute, and the observed value is typically coded such as 0/1.
Business Meaning
This field matters when analysts need to segment, filter, or group Other Transaction IDV records using FPDS generic tagging logic. It can support workflow-specific analysis, custom business rules, and consistency checks across records that use the same generic boolean framework.
Example Value
0
Observed Non-Null Count
6,280

FPDS Compare

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

Use Cases

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

Common Usage

  • Filtering Other Transaction IDV records by a reusable analysis flag
  • Grouping records for custom reporting workflows
  • Checking presence or absence of a generic tag condition

Common Mistakes

  • Assuming the field has a universal business meaning outside the specific FPDS tagging context
  • Interpreting 0/1 without validating the dataset's coded-value convention

Query Guidance

Use exact numeric comparisons in WHERE clauses, for example `WHERE content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean03 = 1`. If the field is sparse or inconsistently populated, add null handling and verify meaning against companion generic tag fields or observed value distributions.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean03 AS generic_boolean03
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean03 IS NOT NULL
LIMIT 25

Aggregate total

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

Distribution overview

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