We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Are there any plans for ezpaarse to support the new R5 spec ?
The text was updated successfully, but these errors were encountered:
Hello Béranger, can you be more specific? Is there a link to the R5 spec you mentionned? Thanks
Sorry, something went wrong.
Sorry, I mean Counter Code of Practice Release 5, https://www.projectcounter.org/code-of-practice-five-sections/abstract/
Thank you
Yes, we will most likely update our double-click procedure to follow the updated R5 algorithm https://www.projectcounter.org/code-of-practice-five-sections/7-processing-rules-underlying-counter-reporting-data/ For the reports and REST API, it remains to be discussed. A lot of what COUNTER R5 is about (counting unique items, etc.) can be done not directly by ezPAARSE but with our ezMESURE portal (based on Elastic and Kibana).
No branches or pull requests
Are there any plans for ezpaarse to support the new R5 spec ?
The text was updated successfully, but these errors were encountered: