KMLM List

[Bernd Oberknapp <bo@xxxxxxxxxxxxxxxxxx>]

On Thu, 23 Jun 2011, Oliver Pesch wrote:

> On the simplest level it would use something like the MISO client to
> make sure reports can be retrieved.  But, that still leaves some room
> for subjective interpretation of the standard.  The plan is to develop
> what would amount to a SUSHI/COUNTER Community Profile which would
> remove the subjectivity.  This may take the form of a detailed FAQ or
> some other form. 
>
> Some of the things that have some up on this list and would be
> included are:
> - Report names in the request should be as specified in the "Report
> Registry" on the NISO SUSHI site.
> - Date ranges for the usage dates must be included and follow the
> prescribed format.
> - Do not include the "Totals" entries in the COUNTER XML
> - The usage data returned should be for the dates requested (if that
> usage is available) -- and not for the entire year.
> - The item Identifier ID tag must be included, BUT if there is not
> identifier the ID tag should be empty (e.g. <ID/> and not
> <ID>N/A</ID>)
>
> Other things would be that the COUNTER report should validate against
> the COUNTER schemas on the NISO site (including the enumeration schema
> which will validate values for Metric Type, Categories, etc.)
>
> This list is a good place to discuss concerns and confusions and
> suggestions. This is the group that has to make this all work!

Recommendations or more strict rules would also be helpful for:

- Authentication/authorization: Recommended method(s)?

- SUSHI error handling: Currently some vendors use exeption numbers
  0-999 for errors instead of the predefined SUSHI exceptions. Using
  the predefined exceptions should be mandatory.

- Customer/ReportItem: Reports shouldn't contain duplicate Customers,
  and Customer no duplicate ReportItems (I think there's already a rule
  for that somewhere in the specification but I couldn't find it).

- Category/Metrics: Which categories and metrics are required, optional
  or not allowed in which report? For example: Must a JR1 report include
  ft_pdf and ft_html for all items/periods? Are turnaways allowd in CR2?

- JR5: The XML version of this report (which currently is badly broken
  for some vendors) differs significantly from the Excel/CSV version
  and therefore probably need additional recommendations/checks.

An online validation service that checks if a report is schema-valid
and conforms to the community profile (as far as this can be tested
automatically) would be great...

Best regards,
Bernd

-- --------------------------------------------------------------------- --
Dipl.-Math. Bernd Oberknapp          Universitaetsbibliothek Freiburg
Tel: +49-761 / 203-3852              Rempartstrasse 10-16  | Postfach 1629
Fax: +49-761 / 203-3987              79098 Freiburg        | 79016 Freiburg