EPrints Technical Mailing List Archive
Message: #00424
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] EPrints COUNTER Compliance
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] EPrints COUNTER Compliance
- From: Mark Gregson <mark.gregson@qut.edu.au>
- Date: Thu, 19 Apr 2012 10:19:29 +1000
The reference to the PIRUS PUSH code made me think of
EPrints’ and COUNTER. I was under the impression that EPrints didn't log
accesses in a COUNTER compliant way. Looking at our 3.2.7 install, the problems appear to be
that it doesn't log 304 requests as COUNTER requires and the robots list is
incomplete (assuming EPrints::Apache::LogHandler is the correct place to look). I seem to remember some type of issue with logging or not
logging HEAD requests but I can't find any details about HEAD requests in the
COUNTER code so perhaps I have this wrong. Also, is the double-click filtering implemented? Cheers Mark Mark Gregson |
Application and Development Team Leader |
- Follow-Ups:
- [EP-tech] Re: EPrints COUNTER Compliance
- From: Tim Brody <tdb2@ecs.soton.ac.uk>
- [EP-tech] Re: EPrints COUNTER Compliance
- Prev by Date: [EP-tech] Re: Google analytics
- Next by Date: [EP-tech] Simple Search Parameters
- Previous by thread: [EP-tech] Unable to login after upgrading from 3.2.8 to 3.3.8
- Next by thread: [EP-tech] Re: EPrints COUNTER Compliance
- Index(es):