ady <terry.br...@georgetown.edu>
> *Cc:* DSpace Technical Support <dspace-tech@googlegroups.com>; DSpace
> Community <dspace-commun...@googlegroups.com>
> *Subject:* Re: [dspace-community] Re: [dspace-tech] Can I create the
> monthly stat report without calling &quo
My feeling is that with the development of DSpace 7, we need to refactor
and improve the way DSpace logs and processes stats/events:
- Add more event types like OAI requests and user logins. But we could
even take this further and provide a *complete audit trail* (log edits,
deletes,
Bram,
Thanks for the feedback on this. If the data in these reports should not
be used anymore, I wonder if we should suppress the inclusion of these
reports by default and require an explicit action to continue to display
them.
Terry
On Thu, Jan 12, 2017 at 4:25 AM, Bram Luyten
The code for these reports can be found here if I'm not mistaking:
https://github.com/DSpace/DSpace/tree/master/dspace-api/src/main/java/org/dspace/app/statistics
I was looking for a trace of robot detection/filtering but couldn't find
any.
Our (Atmire) point of view on these legacy stats is
I am re-sending this question hoping to get some additional feedback.
Alan, thank you for your earlier response.
Is there a current recommendation on the use of the "legacy statistics"
reports? I see that these reports continue to be produced on
demo.dspace.org.
How trustworthy is the data
Hi,
We still use these legacy stats as well in DSpace 5.5, which is annoying
because we need to keep all dspace.log.* files around for the entire month.
Anyways, this is the cron job I run every night:
/dspace/bin/dspace stat-general && \
/dspace/bin/dspace stat-monthly && \
/dspace/bin/dspace
The DSpace Wiki indicates that the "stat-report" commands are deprecated.
https://wiki.duraspace.org/display/DSDOC6x/Command+Line+Operations#CommandLineOperations-Legacystatistics
Looking at demo.dspace.org, I see the following pages are available
- http://demo.dspace.org/xmlui/statistics
