https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41196 Bug ID: 41196 Summary: Additional sushi authentication params potentially required Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart@gmail.com Reporter: jvinke@austinseminary.edu QA Contact: testopia@bugs.koha-community.org CC: jonathan.druart@gmail.com, jonathan.field@openfifth.co.uk, martin.renvoize@openfifth.co.uk, matt.blenkinsop@openfifth.co.uk, pedro.amorim@openfifth.co.uk 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. -- You are receiving this mail because: You are watching all bug changes.