DSpace 6.3 IRUS patch troubleshooting

[alawvt]

We installed the IRUS patch on our DSpace 6.3 server as described in our issue, Implement IRUS-US statistics #765 and request help troubleshooting the installation. In summary, the installation seemed ok but we aren't seeing the DEBUG messages listed in 8. Testing and verification and the IRUS support staff have not seen our IP address in their logs.

[davidatmire]

Hi @alawvt ,

I have had a look at VTUL/vtechworks#765, and I can see that you have already made a lot of progress in your investigation.

If the patch is correctly installed and the DEBUG logs correctly enabled, there is no reason for the ExportUsageEventListener logs not to be displayed in the dspace logs.

As @keithgee has discovered, events are not sent to IRUS for admin users (they are still sent for regular logged-in users with no admin rights though). The logic behind this is that view/download events generated by admin users are not to be considered as normal activity.

The code responsible for this exclusion is here.
If the code of the repository is not customised, the only users who are able to edit an item are admin users.

This is probably a bit late, but I hope this is still helpful.
I have also updated the documentation on https://atmire.github.io/IRUS/#/functionality:
"The patch will automatically send bitstream download hits and item views (originating from non-admin users) to the IRUS-UK service."

[bbranan]

Just to chime in here, as @davidatmire mentioned, make sure you have logging set to DEBUG: https://github.com/atmire/IRUS/blob/stable_6x/dspace/config/log4j.properties#L119, otherwise you won't see any of the IRUS output in the logs.

If you're still not seeing any output, you can post your config file (config/modules/stats.cfg) here, just to verify the settings found there are correct.

[alawvt]

@davidatmire, thank you very much for the information about excluding admins.

@bbranan, thanks. I believe the stats.cfg is ok. We have the logs set to DEBUG.