About Ops Learning – past, present, future #2168
szabozoltan69
started this conversation in
General
Replies: 1 comment
-
An example API call output:
And the same in CSV:
Some filtering options, and the given records count:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The recent "Ops Learning" in Django data means one model in the PER section, with some many-to-many fields, beginning here:
There is an API endpoint, for standard json and CSV data also:
In CSV serialization we used a specific NarrowCSVRenderer, which means that the multiplied values of the many-to-many fields we show in a "narrow" way, i.e. repeating the rows with showing in the same column the different values of the many-to-many field. It's quite unique (and useful) in our GO api.
And we have a nice filter also:
There is a planned cron job to read in the new OpsLearning entities. This task was done manually by Paola until now; if we decide to introduce that cron job, it could be fine.
The Django Admin page makes it possible to work with these OpsLearning records manually, validate or modify them. Recently there are 12663 records in the prod live database, which means a lots of data.
Here are some local testing options of using the ops-learning API endpoint. Normally the logged in users see more (e.g. about the appeal details) than the anonymous calls. That "-H ..." part below means a logged in usage:
Beta Was this translation helpful? Give feedback.
All reactions