Right now, we are looking up NoveList Select information as recommendations lanes are accessed. If the work has been looked up before, the recommendations feed and the POST to NoveList will be cached. But if it hasn't, that lookup work is happening at runtime.

The

NoveListCoverageProvider

isn't being used right now, and it doesn't work with multi-tenancy at this time. With an update for 2.0 and a script, some of the lookup work could happen in the background and the wee hours as a script.

┆Issue is synchronized with a GitHub issue
┆Repository Name: circulation
┆Issue Number: 683