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

25.01.00 restore ebsco searchers #2193

Conversation

Chloe070196
Copy link
Contributor

Fixes a bug that prevents patrons form searching in 'Article Databases' when Aspen Discovery is set to use the EBSCO EDS or EBSCO host integrations.

Detailed description in the Jira ticket: https://aspen-discovery.atlassian.net/browse/DIS-221
Test plan in commit messages

When attempting to run a search in 'Articles and
Databases' using the EBSCO EDS or host integration, the
attempt to display the results fails, and the
following error message is displayed instead:

SearchObject_EbscoEdsSearcher::processSearch():
Return value must be of type AspenError|array|null
, stdClass returned

For EBSCO host, the same error appear, but the
data type mentioned is SimpleXMLElement.

This bug was introduced in 25.01.00.

This patch adds stdClass to the list of valid
return types, restoring functionality to the
EBSCO EDS and host integration.

note: valid EBSCO EDS and host credentials are
required

To replicate:

- checkout to a 25.01.00-based branch
- enable the EBSCO EDS / host module
- create an EBSCO EDS / host setting
- run a search in 'Article and Databases'
- notice that EBSCO EDS / host search
results do not display
- notice the error message

Test plan:

- apply this patch
- run a search in 'Article and Databases'
- notice that EBSCO EDS / host search results
display normally
…earcher

25.01.00 restore ebsco eds and host searcher
@mdnoble73 mdnoble73 merged commit db1c211 into Aspen-Discovery:25.01.00 Jan 14, 2025
3 checks passed
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

Successfully merging this pull request may close these issues.

2 participants