Generic Boolean04

Numeric indicator in the IDV Generic Tags section that stores the fourth custom boolean flag for an IDV record. It represents an internal or extended tagging value, typically using 0/1-style logic rather than a descriptive business measure.

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

Variable Overview

FPDS Query Variable
content__IDV__genericTags__genericBooleans__genericBoolean04
Title
Generic Boolean04
FPDS Path
IDV/genericTags/genericBooleans/genericBoolean04
Description
Numeric indicator in the IDV Generic Tags section that stores the fourth custom boolean flag for an IDV record. It represents an internal or extended tagging value, typically using 0/1-style logic rather than a descriptive business measure.
Business Meaning
This field supports reusable filtering and segmentation in procurement analysis when an organization has mapped internal meaning to the tag. It can help analysts isolate subsets of IDVs for workflow-specific reporting, governance checks, or supplemental classification that is not captured by core FPDS fields.
Example Value
0
Observed Non-Null Count
695,745

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter IDV records into internally defined analysis groups
  • Join with other generic tags to build reusable reporting logic
  • Identify records marked for special handling or supplemental review

Common Mistakes

  • Assuming 0 and 1 have universal FPDS business meaning without local documentation
  • Using the field as a procurement outcome measure instead of a tagging flag

Query Guidance

Use equality filters and explicit null handling, for example WHERE content__IDV__genericTags__genericBooleans__genericBoolean04 = 1 or IS NULL checks as needed. If the data are stored as text or mixed numeric codes in your extract, cast or normalize before aggregating, and avoid interpreting counts unless the associated tag definition is known.

SQL Examples

Preview values

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

Aggregate total

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

Distribution overview

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