FPDS Query Library
About Us
Contact Us

Generic String03

A free-text generic string attribute stored in the Other Transaction IDV generic tags section. It serves as an extensible data slot whose meaning depends on the awarding agency's implementation and posting conventions.

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__genericString03
Title
Generic String03
FPDS Path
OtherTransactionIDV/genericTags/genericStrings/genericString03
Description
A free-text generic string attribute stored in the Other Transaction IDV generic tags section. It serves as an extensible data slot whose meaning depends on the awarding agency's implementation and posting conventions.
Business Meaning
This field matters because agencies may use generic tags to carry reusable analysis labels, internal classifications, or transaction-specific attributes not captured in standard FPDS fields. It can help analysts identify patterns across Other Transaction IDVs when the same agency or reporting process populates the tag consistently.
Example Value
Example value

FPDS Compare

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

Use Cases

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

Common Usage

  • Filtering records by an agency-specific tag value
  • Grouping similar Other Transaction IDV records for ad hoc analysis
  • Inspecting custom metadata attached to award records

Common Mistakes

  • Assuming the field has a universal FPDS definition across agencies
  • Using the raw text as a stable coded value without validating observed formats

Query Guidance

Use exact match, LIKE, or normalization logic depending on how the agency populates the field. In SQL, trim and standardize case before comparison, and combine with OtherTransactionIDV and adjacent generic tags to understand whether the value is meaningful or just a placeholder.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__genericTags__genericStrings__genericString03 AS generic_string03
FROM fpds.data
WHERE content__OtherTransactionIDV__genericTags__genericStrings__genericString03 IS NOT NULL
LIMIT 25

Top values

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