You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Primo Studio version of this plugin is based on a very outdated fork of this repo. It does not work with Primo VE at all, and as far as I can tell, it has been abandoned. Oddly, the plugin metadata points to this repository and not the forked repo.
It should be possible to modify this plugin to work both with and without Primo Studio by checking the $injector service for an instance of primoExploreHathiTrustAvailabilityStudioConfig and then overriding the component bindings as needed.
This has been lingering as a low-priority item on my to-do list for a while because I don't use Primo Studio and haven't had a compelling reason to start. If you'd like to see the Primo Studio support for this plugin, please let me know by adding a +1 or comment to this issue. Or better yet, if you're a Primo Studio plugin wiz, feel free to submit a pull request 🙂 .
The text was updated successfully, but these errors were encountered:
I suggest that we remove the HathiTrust option from Primo Studio. This package is based on an unmaintained private fork that does not work with VE. Given that most of the community is now on VE, the presence of this forked package seems to cause nothing but confusion. More info: UMNLibraries/primo-explore-hathitrust-availability#13.
The Primo Studio version of this plugin is based on a very outdated fork of this repo. It does not work with Primo VE at all, and as far as I can tell, it has been abandoned. Oddly, the plugin metadata points to this repository and not the forked repo.
It should be possible to modify this plugin to work both with and without Primo Studio by checking the
$injector
service for an instance ofprimoExploreHathiTrustAvailabilityStudioConfig
and then overriding the component bindings as needed.This has been lingering as a low-priority item on my to-do list for a while because I don't use Primo Studio and haven't had a compelling reason to start. If you'd like to see the Primo Studio support for this plugin, please let me know by adding a +1 or comment to this issue. Or better yet, if you're a Primo Studio plugin wiz, feel free to submit a pull request 🙂 .
The text was updated successfully, but these errors were encountered: