content negotiation functionality for grants in REST API
As a funder, I would like the metadata for my grants to be available via the REST API so that metadata consumers can retrieve data about my grants.
What
Specification for grants content negotiation behavior. Note that content negotiation will not be supported at this time, but we'd like to be sure to specify the expected behavior.
Definition of ready
-
Product owner: @ppolischuk1 -
Tech lead: @dtkaczyk -
Service:: label applied -
Definition of done updated -
Acceptance testing plan: staging -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
SONAR on merge request branch checked by tech lead -
SONAR on merge request branch checked by reviewer -
Code reviewed -
Available for acceptance testing via a staging URL, or otherwise -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Knowledge base reviewed and updated -
Swagger documentation reviewed and updated -
Education curriculum reviewed and updated -
Acceptance criteria met -
Content negotiation will not be supported for grants -
When content negotiation is attempted for grants, return HTTP code 406 not acceptable
-
-
Test that CN proxy integrates correctly with this -
Acceptance testing passed -
Deployed to production
Edited by Patrick Polischuk