-
Notifications
You must be signed in to change notification settings - Fork 501
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
Spike: Test Counter Processor for use by Dataverse in implementation of Make Data Count #5385
Comments
Reasons for processing:
|
It's pretty hacky but I started trying to stand up counter-processor in Vagrant in 02c5538 |
Outcome of this spike will be a well informed decision to use the processor, fork it, or write our own. Also, we will need a plan to handle how multiple-server situations are handled. |
Counter-processor is creating sushi more or less as expected. We haven't been able to test the outputted sushi against DataCite at this point but its a step in the right direction. There are some questions about counter-processor and the outputted sushi:
Sample raw logs piped into counter processor. Two lines are from Dataverse and one is from the counter-processor sample logs:
Outputted sushi from counter processor:
|
After discussion with @djbrooke , we decided this spike investigating Counter Processor is done and can be closed. |
For Dataverse to generate aggregated usage data to comply with the Make Data Count specifications, raw data access logs will need to be processed for a variety of reasons. Furthermore, this aggregated data needs to be sent to the Make Data Count servers for centralized access and further use.
An implementation exists that will fill both of these needs for us, namely Counter Processor. Before we decide to go forward with this tool we need to ensure that it provides enough value to require an additional dependency. Even if we decide not to use this tool inside Dataverse, exploring this tool allows us to better understand practical considerations in generating and processing or logs. Furthermore, this tool could be used as a "mock" implementation for us to test with as we develop our own implementation in-house.
The text was updated successfully, but these errors were encountered: