-
Notifications
You must be signed in to change notification settings - Fork 5
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
Learnings Table and API Endpoints #1927
Comments
Permissions
|
The fully functional opslearning API endpoint is deployed to Staging. |
Context: Requests for the API endpoint:
We also would need this type of filtering for the CSV export. Thanks! |
All the above filterings are working for CSV output also (due to this filtering happens before the format conversion).
Also you can check the already existing /api/v2/primarysector and /api/v2/per-formcomponent/ endpoints to have sectors and per_components. |
@ypyelab the change is ready and can be tested on Staging.
|
Is your feature request related to a problem? Please describe.
No. We want to have GO API endpoints for displaying operational learnings coming from DREF and Emergency Appeals documents.
Describe the solution you'd like
We would like to have:
Additional context
This is part of the ops learnings project, which tries to display operational learning data in different platforms/sections. The first step is to have the data easily retrievable (i.e., via GO API).
Where does the data come from and how is it maintained?
Externally generated from appeal documents and posted to GO via a POST endpoint.
Should there be any restrictions around viewing or updating information related to this feature
Links to documentation
Table structure:
go_ops_learning_endpoint.xlsx
Context of project:
https://docs.google.com/presentation/d/1HiulBBMZLoaazieX9lDuu13XRE6ZGG-RBkRoWBlafcY/edit?usp=drive_link
@tovari @AlexxxH
The text was updated successfully, but these errors were encountered: