FPDS Query Library
About Us
Contact Us

Generic String01

Free-text generic string stored in the Other Transaction IDV generic tags section as the first generic string slot. It is an attribute-level field used to carry custom, program-specific, or workflow-specific text rather than a standard FPDS coded value.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__genericTags__genericStrings__genericString01
Title
Generic String01
FPDS Path
OtherTransactionIDV/genericTags/genericStrings/genericString01
Description
Free-text generic string stored in the Other Transaction IDV generic tags section as the first generic string slot. It is an attribute-level field used to carry custom, program-specific, or workflow-specific text rather than a standard FPDS coded value.
Business Meaning
This field matters because agencies often use generic tag strings to retain supplemental details that are not captured in core FPDS attributes. In procurement analysis, it can support segmentation, custom identifiers, milestone tracking, or program-specific reporting when the agency has populated it consistently.
Example Value
2020-11-18 00:00:00
Observed Non-Null Count
10,053

FPDS Compare

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

Use Cases

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

Common Usage

  • Custom filtering on agency-populated text
  • Grouping records by a supplemental business tag
  • Searching for embedded dates, IDs, or workflow markers

Common Mistakes

  • Assuming the value has a universal FPDS definition
  • Joining or grouping without first validating the agency-specific pattern

Query Guidance

Use exact-match or pattern-based filters only after profiling observed values. In SQL, consider TRIM/LOWER normalization for text searches, and use CAST or parsing functions only if you confirm the field consistently stores date-like or numeric text; otherwise treat it as an opaque string.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__genericTags__genericStrings__genericString01 AS generic_string01
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericStrings__genericString01 IS NOT NULL
LIMIT 25

Top values

SELECT
    content__OtherTransactionIDV__genericTags__genericStrings__genericString01 AS value,
    count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericStrings__genericString01 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.