Closed MCBoarder289 closed 1 week ago
Another goal for this should be to make the time it takes to support a new library very quick.
Perhaps we can decouple Libby and Physical Books, so that we can partially support a library with just Libby first, and then add Physical books later?
We should definitely decouple LIbby and Physical Books. Here's a gameplan for that:
Update Supported Library List
Make LIbby the default, Physical Book an optional select
Add URL parameter for selected library (prevent search each time)
Going to reopen this issue on the refactor/cleanup, and repurpose this one. I believe the decoupling of Libby/Physical Book libraries is more useful in the short/medium term.
When implementing some of the newest library parsers, I picked up on a few patterns that could be abstracted out.
For example: Phoenix was basically a copy last with Syracuse, because those likely have very similar backend systems.
Would like to be more DRY and make some of those classes more modular.