RBdigital integration

Bug #1772680 reported by Terran McCanna on 2018-05-22
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned

Bug Description

PINES is working with Recorded Books, Inc. on integrating their RBdigital e-resources with Evergreen. The intention is to allow searching of RBdigital resources from the Evergreen catalog without needing to import and maintain bibliographic records for the RBdigital resources.

Because some members of the PINES consortium have access to RBdigital through another consortium called GADD, and some members of the PINES consortium have access to RBdigital through independent non-GADD contracts, and some members do not have access to RBdigital at all, the integration will require that the patron is logged into their My Account, and it will only show RBdigital resources that the patron has access to.

The RBdigital search results will appear in the OPAC on a different tab - a search in basic or advanced Evergreen search will carry over to the RBdigital tab (along with filters when mapping is feasible) so that the user can type in a search once and see both sets of results. The design of the RBdigital tab will make use of the OPAC styling for consistency (see screenshot).

The overall framework could also be leveraged for integration of Overdrive or other vendor products.

All of the code, of course, will be released for broader testing and consideration for inclusion in Master.

We are looking forward to being able to post screenshots here soon!

Revision history for this message
Diane Disbro (ddisbro) wrote : Re: [Bug 1772680] [NEW] RBdigital integration
Download full text (3.5 KiB)

This is exciting!

Diane Disbro
Branch Manager/Circulation Coordinator
Union Branch
Scenic Regional Library
308 Hawthorne Drive
Union, MO 63084
(636) 583-3224
<email address hidden>

On Tue, May 22, 2018 at 10:21 AM, Terran McCanna <
<email address hidden>> wrote:

> Public bug reported:
>
> PINES is working with Recorded Books, Inc. on integrating their
> RBdigital e-resources with Evergreen. The intention is to allow
> searching of RBdigital resources from the Evergreen catalog without
> needing to import and maintain bibliographic records for the RBdigital
> resources.
>
> Because some members of the PINES consortium have access to RBdigital
> through another consortium called GADD, and some members of the PINES
> consortium have access to RBdigital through independent non-GADD
> contracts, and some members do not have access to RBdigital at all, the
> integration will require that the patron is logged into their My
> Account, and it will only show RBdigital resources that the patron has
> access to.
>
> The RBdigital search results will appear in the OPAC on a different tab
> - a search in basic or advanced Evergreen search will carry over to the
> RBdigital tab (along with filters when mapping is feasible) so that the
> user can type in a search once and see both sets of results. The design
> of the RBdigital tab will make use of the OPAC styling for consistency
> (see screenshot).
>
> The overall framework could also be leveraged for integration of
> Overdrive or other vendor products.
>
> All of the code, of course, will be released for broader testing and
> consideration for inclusion in Master.
>
> We are looking forward to being able to post screenshots here soon!
>
> ** Affects: evergreen
> Importance: Wishlist
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: EV bug mail
> https://bugs.launchpad.net/bugs/1772680
>
> Title:
> RBdigital integration
>
> Status in Evergreen:
> New
>
> Bug description:
> PINES is working with Recorded Books, Inc. on integrating their
> RBdigital e-resources with Evergreen. The intention is to allow
> searching of RBdigital resources from the Evergreen catalog without
> needing to import and maintain bibliographic records for the RBdigital
> resources.
>
> Because some members of the PINES consortium have access to RBdigital
> through another consortium called GADD, and some members of the PINES
> consortium have access to RBdigital through independent non-GADD
> contracts, and some members do not have access to RBdigital at all,
> the integration will require that the patron is logged into their My
> Account, and it will only show RBdigital resources that the patron has
> access to.
>
> The RBdigital search results will appear in the OPAC on a different
> tab - a search in basic or advanced Evergreen search will carry over
> to the RBdigital tab (along with filters when mapping is feasible) so
> that the user can type in a search once and see both sets of results.
> The design of the RBdigital tab will make use of the OPAC styling for
> consistency (see scree...

Read more...

Jane Sandberg (sandbej) on 2018-05-22
tags: added: opac
Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

Very exciting!

Is it safe to say this will build on the existing RBdigital API integration in Evergreen?

For those who wish to have a single integrated result set and/or the ability to show ebook results for non-logged-in patrons, will the current approach (MARC record imports + overlay on EG search results) continue to be supported?

Revision history for this message
Terran McCanna (tmccanna) wrote :

Hi Jeff,

This development is completely separate from the existing RBdigital API integration. If libraries wish to import and maintain those bib records in the Evergreen database, then sticking with the existing method and not implementing the new method would be best.

This new approach will work for those of us who do not wish to import those records and who do not want to show materials to patron groups who will not be able to access those materials.

You could theoretically implement both methods if you wished to, but that might be confusing for patrons because they might see different result sets on the regular search results tab than they would on the new RBdigital tab - it would be worth testing once we get to that point, though!

Revision history for this message
Terran McCanna (tmccanna) wrote :

Attached are a few screenshots of the progress so far (keep in mind that wording / links / etc. will likely change as progress continues).

Revision history for this message
Terran McCanna (tmccanna) wrote :

Jeff - actually, it looks like it *will* be leveraging the existing integration pieces.

Revision history for this message
Galen Charlton (gmc) wrote :

A series of patches are available in the collab/gmcharlt/lp1772680_rbdigital_enhancements branch:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/gmcharlt/lp1772680_rbdigital_enhancements

This represents code developed primarily by RBDigital for the GADD and PINES project, with some adjustments for master. The pull request is ready for general testing, but a number of tweaks are anticipated before the final 3.2 cutoff.

tags: added: pullrequest
Changed in evergreen:
status: New → Confirmed
milestone: none → 3.2-beta
Revision history for this message
Chris Sharp (chrissharp123) wrote :

I'm unable to get this working, first on a realistic PINES test server, then on a stock server. Here's the perl error I'm seeing:

OpenSRF Listener [open-ils.ebook_api]: [ERR :1479:Application.pm:116:] Error loading application_implementation: OpenILS::Application::EbookAPI -> Can't locate object method "json_hint" via package "Fieldmapper::extra::rbdigital_:digital_services" (perhaps you forgot to load "Fieldmapper::extra::rbdigital_:digital_services"?) at /usr/local/share/perl/5.22.1/OpenILS/Utils/Fieldmapper.pm line 228.

And so far I'm unable to track down the problem.

Jane Sandberg (sandbej) on 2018-08-23
tags: added: needsreleasenote
Revision history for this message
Terran McCanna (tmccanna) wrote :

Removing pullrequest, as it needs further work.

tags: removed: pullrequest
Revision history for this message
Galen Charlton (gmc) wrote :

Sorry about that; I've corrected typos in fm_IDL.xml, rebased against master, and force-pushed to the collab branch.

tags: added: pullrequest
Changed in evergreen:
milestone: 3.2-beta → 3.2-rc
Revision history for this message
Galen Charlton (gmc) wrote :

Force-pushed to collab/gmcharlt/lp1772680_rbdigital_enhancements with some additional updates, including some release notes.

Changed in evergreen:
milestone: 3.2-rc → 3.2.1
Changed in evergreen:
milestone: 3.2.1 → 3.next
Revision history for this message
Jason Stephenson (jstephenson) wrote :

Moved the target to 3.next because this is definitely a new feature.

Revision history for this message
Galen Charlton (gmc) wrote :

I've force-pushed to collab/gmcharlt/lp1772680_rbdigital_enhancements again to reflect additional updates.

Dan Wells (dbw2) on 2019-02-06
Changed in evergreen:
milestone: 3.next → 3.3-beta1
Changed in evergreen:
milestone: 3.3-beta1 → 3.3-rc
Changed in evergreen:
milestone: 3.3-rc → 3.next
Jane Sandberg (sandbej) on 2019-08-29
tags: removed: needsreleasenote
Revision history for this message
Jane Sandberg (sandbej) wrote :

One quick question about this branch: there appear to be two new files in live_t: 100-ebookapi-rbdigital.t and 101-ebookapi-rbdigital.t. I am all for more automated tests, but I'm wondering if both of these are supposed to be added? One appears to be a more extensive version of the other.

Revision history for this message
Jessica Woolford (jwoolford) wrote :

Curious about the state of this development, since RBDigital is no longer going to be a thing. Any plans to transfer the work to the OverDrive APIs?

Revision history for this message
Elaine Hardy (ehardy) wrote :

We have reached out to the RB Digital team behind the development for more information and have not received a response.

tags: removed: pullrequest
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers