Bug 41196

Summary: Additional sushi authentication params potentially required
Product: Koha Reporter: John Vinke <jvinke>
Component: ERMAssignee: Jonathan Druart <jonathan.druart>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: jonathan.druart, jonathan.field, martin.renvoize, matt.blenkinsop, pedro.amorim
Version: 25.05   
Hardware: All   
OS: All   
GIT URL: Initiative type: ---
Sponsorship status: --- Comma delimited list of Sponsors:
Crowdfunding goal: 0 Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description John Vinke 2025-11-05 20:55:43 UTC
Some SUSHI 5 providers require additional parameters beyond those listed in the Data Provider SUSHI Credentials fields.

One such example is Harvard University Press, which requires a "platform" parameter.  There is a field in the data provider record for "service platform" but this does not seem to be used.

From their SUSHI page:
Multiple platforms available, populate the Platform parameter with the platform name you wish to report on
        Loeb+Classical+Library
        DARE+Dictionary

So a functional link for me looks like:

https://ams.hup.harvard.edu/rest/COUNTER/v5/reports?customer_id=[REDACTED]&api_key=[REDACTED]&platform=Loeb+Classical+Library

For now, I can get this target to work by injecting the additional parameter in my API key field, but it would be nice to have a way to handle odd extra params like this.
Comment 1 Pedro Amorim 2025-11-06 09:38:26 UTC
(In reply to John Vinke from comment #0)
> Some SUSHI 5 providers require additional parameters beyond those listed in
> the Data Provider SUSHI Credentials fields.
> 
> One such example is Harvard University Press, which requires a "platform"
> parameter.  There is a field in the data provider record for "service
> platform" but this does not seem to be used.
> 
> From their SUSHI page:
> Multiple platforms available, populate the Platform parameter with the
> platform name you wish to report on
>         Loeb+Classical+Library
>         DARE+Dictionary
> 
> So a functional link for me looks like:
> 
> https://ams.hup.harvard.edu/rest/COUNTER/v5/
> reports?customer_id=[REDACTED]&api_key=[REDACTED]&platform=Loeb+Classical+Lib
> rary
> 
> For now, I can get this target to work by injecting the additional parameter
> in my API key field, but it would be nice to have a way to handle odd extra
> params like this.

Hi John, what version of Koha are you using?
I believe the platform parameter was added in bug 37856.
Comment 2 John Vinke 2025-11-06 14:20:57 UTC
Ah yes, I'm on 25.05.04 and did not see that one, so this is a duplicate of one that has been resolved.
Comment 3 Pedro Amorim 2025-11-06 14:26:08 UTC

*** This bug has been marked as a duplicate of bug 37856 ***