Skip to content

Checklist: challenges.csv data file format #4

@MattTriano

Description

@MattTriano

Requirements for the challenges.csv data file format

Per page 27 of the policy notice and Notices of Changes to the process.

Column Names, Order, and Data Types (dtypes):

  1. challenge (dtype: string)
  2. challenge_type (dtype: single-character string)
  3. challenger (dtype: string)
  4. challenge_date (dtype: string)
  5. rebuttal_date (dtype: string)
  6. resolution_date (dtype: string)
  7. disposition (dtype: single-character string)
  8. provider_id (dtype: integer here, string in challenger)
  9. technology (dtype: integer)
  10. location_id (dtype: integer)
  11. unit (dtype: string)
  12. reason_code (dtype: single-character string)
  13. evidence_file_id (dtype: string)
  14. response_file_id (dtype: string)
  15. resolution (dtype: string)
  16. advertised_download_speed (dtype: integer)
  17. download_speed (dtype: integer)
  18. advertised_upload_speed (dtype: integer)
  19. upload_speed (dtype: integer)
  20. latency (dtype: float)

Column Content Requirements

Columns Required to be Not Null

Columns that can be Conditionally Null

Multi-File Column Rules

  • challenger: Uniquely identifies a challenger in the table challenger.csv (not case sensitive)
    • test: ToDo: implement test

Intentionally noted but not checked by this project

  • provider_id: Must be a valid provider in the state.
  • location_id: Must be in the Fabric for that state.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions