Hi Heather,
the COUNTER_SUSHI API usually is used for application to application communication, so I'm wondering why SAML should be considered for this case. Which libraries/consortia have suggested this and what is their use case?
Best regards, Bernd
On 16.07.20 18:31, Heather Flanagan wrote:
HI Bernd,
This would be very much like extending COUNTER. Authorization attributes are a different thing; the feedback from the group discussing this feels that authorization should be handled via an entitlement attribute, whereas this kind of reporting should be in something else.
I don’t know if the answer is to extend the API, or do something else. It would be good to get folks together to talk about the possibilities.
Heather Flanagan — Translator of Geek to Human https://sphericalcowconsulting.com On Jul 16, 2020, 9:02 AM -0700, Bernd Oberknapp bo@ub.uni-freiburg.de, wrote:
Hi Heather,
there have been discussions to use SAML to transmit information (e.g. group membership) to publishers and then break the usage reports down by that information, which has been discussed before and would be possible by using extended COUNTER Master Reports, but that doesn't seem to be the goal? Is the intention to protect access to the usage reports by SAML? That would be possible for the administrative web sites, but I don't think that it would make sense for the COUNTER_SUSHI API since that would add a lot of complexity. I'm a member of the group that has written the COUNTER specification, and the intention was to keep this as simple a possible which is why a) only the methods listed in section 8.2 of the Code of Practice are permitted and b) the parameters are simply passed in the URL, including the authentication information.
Best regards, Bernd
On 16.07.20 17:37, Heather Flanagan wrote:
Hello FIM4L members!
How many of you get reports from publishers on usage stats for billing purposes (maybe by using the COUNTER-SUSHI standards)? Have any of you done anything different to get this kind of information into a SAML workflow? A small group is spinning up in the REFEDS Schema area that’s discussing the possibilities here, and while we have publishers on hand to describe the use case, I was wondering what this might look like
from
the library perspective.
Feedback and further information most welcome!
Heather Flanagan — Translator of Geek to Human https://sphericalcowconsulting.com
FIM4L mailing list FIM4L@lists.daasi.de http://lists.daasi.de/listinfo/fim4l
-- Bernd Oberknapp Gesamtleitung ReDI
Albert-Ludwigs-Universität Freiburg Universitätsbibliothek Platz der Universität 2 | Postfach 1629 D-79098 Freiburg | D-79016 Freiburg
Telefon: +49 761 203-3852 Telefax: +49 761 203-3987 E-Mail: bo@ub.uni-freiburg.de Internet: www.ub.uni-freiburg.de
FIM4L mailing list FIM4L@lists.daasi.de http://lists.daasi.de/listinfo/fim4l