Currently, the values for representing urgency in the /data-requests endpoint (and associated database) are lengthy -- including the word, as well as a parenthetical description of each. This can be made more concise.
Requirements
Convert the accepted values for urgency to be just the word (or, if multiple words, the words in snake_case), omitting the parentheticals.
Add comments to necessary areas to describe what each represents: This could include the database enums, the code representation of the enums, and the schema description
Tests
All tests should continue to run as expected.
Docs
API docs should be updated to reflect the new acceptable values.
Context
urgencyin the/data-requestsendpoint (and associated database) are lengthy -- including the word, as well as a parenthetical description of each. This can be made more concise.Requirements
urgencyto be just the word (or, if multiple words, the words in snake_case), omitting the parentheticals.Tests
Docs
Open questions