On Mon, Feb 2, 2009 at 11:10 AM, Robin Taylor <[email protected]> wrote:
> Hi Kim,
>
> Apologies for sort of hijacking your thread, I have renamed the title to
> allow separate replies. It sounds to me like you have taken a similar
> approach to the Minho guys
who? eh?
> in that you take the dspace log as your starting point for compiling the
> stats. In fact if you are not familiar with their package it would be worth
> your while having a look.
URL, please?
> Whilst this is an attractive approach in that you don't have to mess around
> with the existing Dspace code, I have some reservations about its
> reliability. To date the log message format has been pretty well maintained,
> but in an Open Source environment where patches, plugins, etc could come
> from various sources I am not confident that will always be the case.
I agree. the log record would have to be formally specified.
> So my question is, are there any current/planned solutions that integrate
> the compiling of stats into the heart of the Dspace code ?
I hope not. Or if there is I hope that using logfiles will still be
supported. IMO the builtin reports will never be enough for the needs of
some people. It's great to provide some reports out of the box and I hope
that over time this will include COUNTER-compliant reports. But my DSpace
definitely has needs noone else knows about.
> Sorry if I am going over old ground here but its just come onto my radar so
> I have only just started paying attention.
>
> Thanks, Robin.
>
> --
Regards,
Andrew M.
http://www.andrewpetermarlow.co.uk
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
