--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/9d0bbbc7-d27c-4aba-9d3c-9f4b0c805e2an%40googlegroups.com.
A little more info:
1) The challenge in combining the numbers is that MDC, as implemented in Dataverse with counter_processor, does a good job of removing requests from robots, separates machine and human accesses, only counts rapid repeat requests from the same user as one count, etc. The internal accounting in Dataverse prior to MDC didn’t do such filtering and the base guestbookresponses table (where non-MDC counts come from now) doesn’t really have enough info to do such filtering. If you have other logs (such as the Apache log or optional glassfish/payara logs) you might be able to use those, possibly in combination with the guestbookresponses to do some filtering. Harvard has been looking into that. For QDR, we did not have complete apache logs and didn’t want to just combine the unfiltered pre-MDC counts with the new MDC ones, so, in cases of datasets with counts prior to when MDC logging was turned on, we made a code change to show both. (If you recall, I was pushing people to turn on MDC logging even if they weren’t ready to turn on display of MDC and to set up all the daily/weekly processing. This was the reason – it’s only the downloads prior to the start of MDC logging that would disappear in the community Dataverse releases, and only things prior to the MDC logging start would have to be custom processed (ala Harvard) or handled by a code change (ala QDR)).
2) is ~independent of MDC – right now Dataverse isn’t reporting related things entered as Dataverse metadata to DataCite. QDR has added that, making some choices about which fields mapping to which relationships.( I think #2778 is awaiting consensus on such a mapping and then whatever minor coding is needed to enact it). If/when Dataverse sends that info to DataCite, it could, in theory be picked up so that the paper could indicate a connection back to the data in Dataverse (I’m not sure what’s actually in place at CrossRef/elsewhere w.r.t. this). MDC is actually involved in the opposite direction – if you enable MDC and run the weekly script, Dataverse will pick up any instances where a paper cites data in Dataverse and display those citations in a list on the page.
-- Jim
--
|