2.4.5 Counter XML report/export

Software Support
1

Hi. We are currently using OJS 2.4.5. We are noticing a strange problem with the COUNTER XML report. One of our journals has .doc galleys and we initially were wondering if there was a way to view this in the XML report. Looking into this, I understand that this isn’t possible (the .doc mimetype isn’t in the SUSHI schema nor in the COUNTER protocol). In lieu of this, we wanted to know if the XML report could display a total count of every galley downloaded. Turns out, that this is supposed to be a part of the report.

Here is an example report:

<ItemPerformance>
<Period>
<Begin>2015-06-01</Begin>
<End>2015-06-30</End>
</Period>
<Category>Requests</Category>
<Instance>
<MetricType>ft_html</MetricType>
<Count>711</Count>
</Instance>
<Instance>
<MetricType>ft_pdf</MetricType>
<Count>57</Count>
</Instance>
</ItemPerformance>

In reportxml.tpl we see this:

<ItemPerformance>
<Period>
<Begin>{$requests.start}</Begin>
<End>{$requests.end}</End>
</Period>
<Category>Requests</Category>
{if $requests.count_total neq ''}<Instance>
<MetricType>ft_total</MetricType>
<Count>{$requests.count_total}</Count>
</Instance>{/if}

{if $requests.count_html neq ''}<Instance>
<MetricType>ft_html</MetricType>
<Count>{$requests.count_html}</Count>
</Instance>{/if}

{if $requests.count_pdf neq ''}<Instance>
<MetricType>ft_pdf</MetricType>
<Count>{$requests.count_pdf}</Count>
</Instance>{/if}

</ItemPerformance>

I note that the first MetricType tag ought to be ft_total yet this isn’t shown in the resulting report. I feel like the expected report ought to have a

<MetricType>ft_total</MetricType>
<Count>x</Count>

Hoping for some feedback as to why this might not be working (and if I ought to submit an issue report about this). Help with troubleshooting and fixes are welcome.

Thanks.

2

I am refactoring the counter plugin to support COUNTER 4 and SUSHI-Lite, and in the proposed changes the JR1 will support the ft_html, ft_pdf, and ft_total Metric Types.

I think this will cover your use-case above.

3

Oh, great!

But I’m guessing this will be available in a future release? (Not for 2.4.5). We just upgraded here…

I won’t do a issue report, but any guidance for maybe fixing this problem in 2.4.5 for the interim?

4

The target release for this new functionality is presumably 2.4.7 (release date to be determined).

I have a build of the functionality for 2.4.6 which we are currently testing at the Pitt ULS: GitHub - ulsdevteam/ojs at stable246_sushiLite

5

Okay, great. Thanks for the info.