Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error at confirm a ILL request #7

Open
hagud opened this issue Mar 15, 2021 · 7 comments
Open

Error at confirm a ILL request #7

hagud opened this issue Mar 15, 2021 · 7 comments

Comments

@hagud
Copy link

hagud commented Mar 15, 2021

Good morning

After searching and get a record for import, when we try to confirm a request, we get this error

ILS-di is enable and accessible
username and password at configuration is fine
url is working (but https)

Se encontró un error:

ILDI Service Error: Request - ?password=&service=AuthenticatePatron&username=, Status - 400 URL must be absolute, Content - 400 URL must be absolute
, ?password=&service=AuthenticatePatron&username= ()

Confirmar la solicitud de PIB

We encountered an error:

ILDI Service Error: Request - ?password=&service=AuthenticatePatron&username=, Status - 400 URL must be absolute, Content - 400 URL must be absolute , ?password=&service=AuthenticatePatron&username=

any help on this, please?

@AndrewIsh
Copy link

Hi @hagud

It looks like the URL you have specified for the ILSDI target is wrong. The value for the ILSDI parameter here should be the full URL to your Koha instance's ilsdi.pl.

That said, this ILL backend has not had any work done to it for a long time, so it's conceivable that it is broken in some way that is causing this error.

I hope that helps!

Andrew

@hagud
Copy link
Author

hagud commented Mar 17, 2021

Hi

Thanks for the answer, Base.pm was already edited, then I guess is the second option... is broken somewhere else

Thanks !

@AndrewIsh
Copy link

Are you sure the ILSDI URL is correct? The error is coming directly back from the request to the ILSDI service, which suggests the URL isn't correct.

@hagud
Copy link
Author

hagud commented Mar 17, 2021 via email

@AndrewIsh
Copy link

Yes, that all looks OK to me. So, yes, I think you're right, there must be something broken. I don't think we have any time available to look at this at the moment I'm afraid. It may be that another member of the Koha community would be willing to take it on.

@hagud
Copy link
Author

hagud commented Mar 17, 2021 via email

@gveranis
Copy link

gveranis commented May 27, 2021

In order to solve that , you need to have the same name 'Koha' to you Z3950 target on Koha as a label.
because Base.pm at lines 533-534 build a hashref array based on labels that you have on Z3950 target as 'Name' .
So if you name it 'Koha' on Base.pm then you should have name the same your target otherwise not is going to work. Maybe on that we can add a patch for that to the community.

George Veranis
Dataly Tech

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants