API Key, requestor ID and customer ID are defined as varchar(80). We had reports that this can be not enough in some cases. Suggestion is to extend to varchar(255). https://schema.koha-community.org/24_05/tables/erm_usage_data_providers.html
And for service_url 80 characters are not enough as well
*** Bug 38807 has been marked as a duplicate of this bug. ***
Is there a specification in SUSHI documentation regarding the lengh of those fields? I tried to search but I only found in their OpenAPI specification that those fields have "ApiKey" datatype, which does not seem to have a lenght limit.
(In reply to Mathieu Saby from comment #3) > Is there a specification in SUSHI documentation regarding the lengh of those > fields? I tried to search but I only found in their OpenAPI specification > that those fields have "ApiKey" datatype, which does not seem to have a > lenght limit. I have wondered the same thing in order to make sure we pick the right datatypes here. Did you encounter anything close to 255 chars yet?
(In reply to Katrin Fischer from comment #4) > (In reply to Mathieu Saby from comment #3) > > Is there a specification in SUSHI documentation regarding the lengh of those > > fields? I tried to search but I only found in their OpenAPI specification > > that those fields have "ApiKey" datatype, which does not seem to have a > > lenght limit. > > I have wondered the same thing in order to make sure we pick the right > datatypes here. Did you encounter anything close to 255 chars yet? (In reply to Mathieu Saby from comment #3) > Is there a specification in SUSHI documentation regarding the lengh of those > fields? I tried to search but I only found in their OpenAPI specification > that those fields have "ApiKey" datatype, which does not seem to have a > lenght limit. I think the NISO standard is the place to look - https://groups.niso.org/higherlogic/ws/public/download/29097/Z39-93-2014_SUSHI-1_7.pdf - However, there don't seem to be restrictions on length. So, I guess we need to work with the longest examples we have. I think increasing to 255 would cover that, wouldn't you?
> I think the NISO standard is the place to look - > https://groups.niso.org/higherlogic/ws/public/download/29097/Z39-93- > 2014_SUSHI-1_7.pdf - However, there don't seem to be restrictions on length. > So, I guess we need to work with the longest examples we have. I think > increasing to 255 would cover that, wouldn't you? I believe so. It would be interesting to hear what the longest encountered were to see how close we get.