Implement CRUD endpoints to manage GCMS - Alkanes data
Implement POST/api/rafs-ddms/samplesanalysis/data/gcms_alkanes is implemented and available on Swagger
- record_id is the SamplesAnalysis WPC which was created previously
- User should be able to fill the SamplesAnalysis report with measurements taken in this analysis
- Successful response (200 status code) should update SamplesAnalysis record and include DDMSDatasets array with GET endpoint to the linked bulk data of gcms_alkanes
- Validation cases should be covered with appropriate status codes
- Request & response structure should correspond to populated JSON
Implement GET/api/rafs-ddms/samplesanalysis/data/gcms_alkanes is implemented and available on Swagger
- record_id is the SamplesAnalysis WPC
- User should be able to retrieve bulk data of gcms_alkanes new endpoint
- Successful response (200 status code) should retrieve all existing gcms_alkanes Measurements (bulk data) linked to specified record id (SamplesAnalysis WPC)
- Validation cases should be covered with appropriate status codes
- Structure of request and response should correspond to populated JSON content schema
Link to Schema which should be used: https://gitlab.opengroup.org/osdu/subcommittees/data-def/projects/RAFSDDMSDEV/docs/-/blob/main/Design%20Documents/gcms_aromatics_data_schema.json
Edited by Mykhailo Buriak