You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mula raw data events from bytes, in the message the raw data object is sent over information about the Boefje is also sent. However this doesn't contain the name of the boefje.
From rocky it is preferred to display the name of the boefje for a normalizer task, in the task overview. However they only have the boefje id. To retrieve the name of a boefje an API call should be made to the katalogus to uncover the name. This can, based on the number of results showed on a task overview, lead to many API calls to the katalogus uncover the name.
When available it would be nice to have bytes relay the boefje name to the raw data event that is sent on the message queue. Such that the scheduler can relay this information in the normalizer task.
The text was updated successfully, but these errors were encountered:
This data is not available unfortunately, but we could just use the ids query parameter on the list plugins API to limit this to 1 call to the KATalogus. 🙂
Mula raw data events from bytes, in the message the raw data object is sent over information about the Boefje is also sent. However this doesn't contain the name of the boefje.
From rocky it is preferred to display the name of the boefje for a normalizer task, in the task overview. However they only have the boefje id. To retrieve the name of a boefje an API call should be made to the katalogus to uncover the name. This can, based on the number of results showed on a task overview, lead to many API calls to the katalogus uncover the name.
When available it would be nice to have bytes relay the boefje name to the raw data event that is sent on the message queue. Such that the scheduler can relay this information in the normalizer task.
The text was updated successfully, but these errors were encountered: