FPDS Query Library
About Us
Contact Us

Negotiator Code

NASA-specific award identifier used to store the negotiator code associated with the award record. It is a coded value, not a free-text description, and may represent an internal reference used by NASA for routing or tracking.

Family: Award
Category: General
Data Type: identifier_or_code
Semantic Type: identifier
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__award__agencySpecificAwardElements__NASASpecificAwardElements__negotiatorCode
Title
Negotiator Code
FPDS Path
award/agencySpecificAwardElements/NASASpecificAwardElements/negotiatorCode
Description
NASA-specific award identifier used to store the negotiator code associated with the award record. It is a coded value, not a free-text description, and may represent an internal reference used by NASA for routing or tracking.
Business Meaning
This field helps analysts isolate or group awards handled by a particular NASA negotiator, office, or internal workflow code. It can support oversight, workload analysis, and agency-specific segmentation when reviewing award processing patterns.
Example Value
AAA
Observed Non-Null Count
825,111

FPDS Compare

FPDS Query Variable
content__award__agencySpecificAwardElements__NASASpecificAwardElements__negotiatorCode
FPDS XML Path
award/agencySpecificAwardElements/NASASpecificAwardElements/negotiatorCode
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'award/agencySpecificAwardElements/NASASpecificAwardElements/negotiatorCode' into the SQL-ready variable 'content__award__agencySpecificAwardElements__NASASpecificAwardElements__negotiatorCode'.

Use Cases

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

Common Usage

  • filtering NASA awards by negotiator assignment
  • grouping records for workload or process analysis
  • joining to agency-specific code tables or reference data

Common Mistakes

  • assuming the value is a human-readable title
  • treating the code as comparable across agencies without validation

Query Guidance

Use exact-match predicates for filtering or grouping, and normalize case if source values are inconsistently cased. In SQL, prefer SELECT DISTINCT or GROUP BY on the code to profile observed values before joining to any lookup table; avoid substring logic unless you have confirmed the code structure.

SQL Examples

Preview values

SELECT
    content__award__agencySpecificAwardElements__NASASpecificAwardElements__negotiatorCode AS negotiator_code
FROM fpds.data
WHERE content__award__agencySpecificAwardElements__NASASpecificAwardElements__negotiatorCode IS NOT NULL
LIMIT 25

Top values

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