FPDS Query Library
About Us
Contact Us

Generic Boolean01

Numeric indicator stored in the Other Transaction Award generic booleans group. It represents the value of the first reusable boolean flag in the Generic Tags section for an OT award record, typically encoded as 0/1 rather than free text.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean01
Title
Generic Boolean01
FPDS Path
OtherTransactionAward/genericTags/genericBooleans/genericBoolean01
Description
Numeric indicator stored in the Other Transaction Award generic booleans group. It represents the value of the first reusable boolean flag in the Generic Tags section for an OT award record, typically encoded as 0/1 rather than free text.
Business Meaning
This field matters because it supports flexible tagging, segmentation, and downstream reporting on Other Transaction Awards without relying on a fixed business meaning in the award core fields. Analysts may use it to isolate records that have been marked for a specific workflow, interpretation, or internal review pattern in FPDS extracts.
Example Value
0
Observed Non-Null Count
12,012

FPDS Compare

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

Use Cases

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

Common Usage

  • filtering OT award records by a specific generic tag value
  • grouping awards into custom analytical buckets
  • joining to record-level QA or workflow flags in stored extracts

Common Mistakes

  • assuming the field has a universal business meaning across all FPDS releases or agencies
  • treating numeric codes as text labels without checking the dataset-specific definition

Query Guidance

Use equality filters or CASE logic on the stored numeric value, for example WHERE content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean01 = 1. If the field is sparsely populated or implementation-specific, inspect distinct values and null rates before using it in production SQL.

SQL Examples

Preview values

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

Aggregate total

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

Distribution overview

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