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
In InvenioRDM, we would like to distinguish between record-view events that go through the API or UI via a boolean field via_api in the event.
Currently, during aggregation we can either discard events with either of the values (via_api=true/false), or discard the information from this field altogether – or we can cobble together a unique_id that separates the two kinds of events (e.g. {prefix}-{recid} where prefix would be either "ui" or "api").
In the statistics PR in app-rdm (inveniosoftware/invenio-app-rdm#2080), we went the third route for now.
Neither of these possibilities is too enticing, we would rather be able to aggregate the document counts per value inside the aggregation, similar to:
In InvenioRDM, we would like to distinguish between record-view events that go through the API or UI via a boolean field
via_api
in the event.Currently, during aggregation we can either discard events with either of the values (
via_api=true/false
), or discard the information from this field altogether – or we can cobble together aunique_id
that separates the two kinds of events (e.g.{prefix}-{recid}
whereprefix
would be either"ui"
or"api"
).In the statistics PR in app-rdm (inveniosoftware/invenio-app-rdm#2080), we went the third route for now.
Neither of these possibilities is too enticing, we would rather be able to aggregate the document counts per value inside the aggregation, similar to:
This would probably require a
bucket_fields
feature in the aggregations, similar to themetric_fields
.The text was updated successfully, but these errors were encountered: