-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with bulk import status response #1912
Labels
Comments
I have updated the GET API to consider
Also fixed the serialization |
snyaggarwal
added a commit
to OpenConceptLab/oclapi2
that referenced
this issue
Aug 7, 2024
…/report/summary result | correcting serialization
snyaggarwal
added a commit
to OpenConceptLab/oclapi2
that referenced
this issue
Aug 7, 2024
…/report/summary result | correcting serialization
One more round of minor changes: Acceptance criteria:
|
snyaggarwal
added a commit
to OpenConceptLab/oclapi2
that referenced
this issue
Aug 8, 2024
…| only json result
@snyaggarwal looks good! Please update docs |
snyaggarwal
added a commit
to OpenConceptLab/ocl-docs
that referenced
this issue
Aug 8, 2024
snyaggarwal
added a commit
to OpenConceptLab/ocl-docs
that referenced
this issue
Aug 8, 2024
@paynejd Raised a docs PR - OpenConceptLab/ocl-docs#57 |
@paynejd This is deployed on Prod/Demo as well |
@paynejd Can this be closed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When requesting the status of a bulk import, the response has two issues:
summary
,report
,json
In addition, the inconsistent content types in the responses (e.g.
summary
is text and everything else isjson
) puts an unnecessary burden on the client (Sorry: this is a leftover from when I was developing some of the bulk import logic!) This is the right moment to change this, because I am updating the PEPFAR integration script (which is the only dependency on the summary response).Given a request:
There are several possible responses (@snyaggarwal can you please fill in the gaps?):
For some responses, the body depends on the the
result
param:result=summary
(default): change to something like this?result=report
: looks like this:result=json
: response is the same as above, but it also includes aresult
attributeAcceptance criteria:
summary
response should change to a very brief JSON object as described aboveresult
param should work as documented, supporting thesummary
,report
andjson
formats, withsummary
as the defaultresult=json
, should provide a proper JSON object (instead of serialized string)The text was updated successfully, but these errors were encountered: