FPDS Query Library
About Us
Contact Us

Generic String02

A free-text generic string stored in the IDV Generic Tags section. It carries record-specific content that is not standardized into a named procurement attribute, so the exact meaning depends on the agency’s data population practice and the associated value conventions.

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

Variable Overview

FPDS Query Variable
content__IDV__genericTags__genericStrings__genericString02
Title
Generic String02
FPDS Path
IDV/genericTags/genericStrings/genericString02
Description
A free-text generic string stored in the IDV Generic Tags section. It carries record-specific content that is not standardized into a named procurement attribute, so the exact meaning depends on the agency’s data population practice and the associated value conventions.
Business Meaning
This field can support custom filtering, grouping, and downstream workflow logic when agencies use Generic Tags to store reusable analysis labels or supplemental procurement metadata. In federal procurement analysis, it matters mainly as a configurable extension point rather than a core FPDS descriptor, so it may capture local business rules, internal tracking identifiers, or other analysis aids.
Example Value
RQEZW8BSJCV4
Observed Non-Null Count
5,861,366

FPDS Compare

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

Use Cases

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

Common Usage

  • filtering records by agency-defined tag values
  • grouping awards into custom analysis buckets
  • joining to internal lookup tables or reference mappings

Common Mistakes

  • assuming the value has a universal FPDS meaning
  • using the field for analysis without verifying how the agency populates it

Query Guidance

Query it as a plain string and compare exact values or normalized patterns as needed. For SQL, use equality, IN lists, LIKE, or joins to an external mapping table; if the content appears coded, profile distinct values first and avoid hard-coding interpretations without validation.

SQL Examples

Preview values

SELECT
    content__IDV__genericTags__genericStrings__genericString02 AS generic_string02
FROM fpds.data
WHERE content__IDV__genericTags__genericStrings__genericString02 IS NOT NULL
LIMIT 25

Top values

SELECT
    content__IDV__genericTags__genericStrings__genericString02 AS value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__genericTags__genericStrings__genericString02 IS NOT NULL
GROUP BY value
ORDER BY record_count DESC
LIMIT 25

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