KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxxxxxx>]

One point to note on ft_html; ft_pdf; and, ft_total

 

HTML and PDF are just two possible formats for full text; others, though 
possibly not widely used, are Postscript and possibly things like XML; etc.  
When COUNTER came up with the breakdown of the ft_total into html and pdf 
counts; this was done specifically to provide the library some insight into the 
effect of the user interface on the usage; however, it was made clear at that 
time that ft_total is not always going to be the sum of ft_html and ft_pdf.  
All this to say that a SUSHI client will have no way to know if your html and 
pdf counts can be added to imply a total; or if other formats have been 
downloaded and just not counted.  It is recommended that you include the 
ft_total metric to remove any possibly ambiguity. 

 

Thanks

Oliver

________________________________

From: Marco van Schagen [mailto:marco@xxxxxxxxxxxxxxxxxx] ;
Sent: Friday, April 17, 2009 11:26 AM
To: Colin Prince
Cc: sushidevelopers@xxxxxxxxxxxxx
Subject: Re: [sushidevelopers] COUNTER XML - three questions

 

Hi Colin,

We are working on a similair implementation, finding similair challenges.

 

Try to open your sample in Internet Explorer as that will check validity of 
your XML to some level. Your sample does not open well, as you have used the à 
character. Ypu may need to replace this with the &...; equivalent.

 

I believe the vendor, University of Toronto Journals, decides a platform name 
for their hosting platform. I would expect this is the name for the website 
where your customer accesses the publications. We use SD or ScienceDirect for 
anything published on ScienceDirect.com.

 

Having values or not, counter mentions all entitled publications need to be 
listed. We have interpreted this as a desire to include zero values listed as a 
int 0 value.

Thinking of how we expect the values to be read by the harvesting tool; I 
expect this does not need totals (if you listed more than one month); and if 
you have both ft_html and ft_pdf, I would expect totals also is not needed. You 
list ft_total only, so I expect you have no breakdown available.

 

Hope this helps,

hope this may lead to a bit of discussion.

 

Good luck,

Marco

 

 

On Fri, Apr 17, 2009 at 4:16 PM, Colin Prince <colin.prince@xxxxxxxxxxx> wrote:

Hello Everyone,

I'm putting together a COUNTER XML report and referencing the schema here: 
http://www.niso.org/schemas/sushi/counter3_0.xsd

Attached is my first attempt, report.xml. I'd be grateful for any comments.

It's not clear to me what I could put in the ItemPlatform element.

From the docs:

"The platform is the name of the online host as determined by the service 
provider, e.g.,  EBSCOhost, ScienceDirect, etc."

We host journals at the University of Toronto Libraries using OJS software. 
There are many different publishers.

Perhaps "University of Toronto Libraries" is the platform, or is it "OJS" maybe?

Two more questions regarding XML details:

Should the ItemPerformance instances be symmetrical, that is, if I put ft_html 
in one ItemPerformance instance, do I have to make sure it is in all of them?

If we do not have a particular piece of data, is it preferable to skip the 
element, put an empty element, or put an element containing the integer zero?

Thanks,
Colin

--
Colin Prince
416-978-7636
Scholarly Communication Initiatives
University of Toronto Libraries



 



CONFIDENTIALITY NOTICE

This email and any files transmitted with it are confidential
and solely for the use of the intended recipient. It may contain
information which is covered by professional or other privilege.
If you are neither the intended recipient of this email nor the 
person responsible for delivering it to the intended recipient, 
be advised that you have received this email in error and that 
any use of it is strictly prohibited. Please notify the sender 
immediately by reply email and then delete it from your system. 
EBSCO accepts no liability for any loss or damage suffered by 
any person arising from the use of this email.

Please consider the environment before printing this email.