Figure out what (if anything) we need to do to make multiple Blacklight controllers work side-by-side

[mbarnett]

In the current hydra stack I've run into enormous issues with trying to have more than one Blacklight controller/config active in the same application. This severely limits us in the case of Hydranorth, because all of our blacklist-dependent pages share the same config -- therefore, the catalog/search results have the same default sort order and sort options as the collection and community show pages, which isn't desirable.

We need investigation to see if this is still true in the up-to-date stack (docs suggest that the issue we have isn't intentional, but some kind of bug).

Worth also investigating how much blacklight config we can share among controllers to avoid copy and pasting shared setup into multiple controllers (pass lambdas into the config block maybe?)

[ghost]

I'm running multiple controllers in the discovery project: https://github.com/ualbertalib/discovery/tree/master/app/controllers

It probably depends on what you need to do - some of my controllers inherit from the main catalog controller so that I can override some behaviour, but keep the rest; other controllers handle completely separate functionality (i.e. the bento_controller).

On Thu, Nov 17, 2016 at 11:19 AM, Matthew Barnett notifications@github.com wrote:

In the current hydra stack I've run into enormous issues with trying to have more than one Blacklight controller/config active in the same application. This severely limits us in the case of Hydranorth, because all of our blacklist-dependent pages share the same config -- therefore, the catalog/search results have the same default sort order and sort options as the collection and community show pages, which isn't desirable.

We need investigation to see if this is still true in the up-to-date stack (docs suggest that the issue we have isn't intentional, but some kind of bug).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ualbertalib/Hydranorth2/issues/64, or mute the thread https://github.com/notifications/unsubscribe-auth/ABCtysiaEriiFRx88Rtd1tGCrCF9nGuKks5q_JqagaJpZM4K1oxO .

Fender F-35 Cordoba 45FP Ibanez M522SBS Loar LM-520 Lafferty LB

[ghost]

Also, at the Blacklight summit, there was a discussion about using the config object separate from any controller. Because the Blacklight config is a PORO, you can instantiate it and use it outside of a controller (not sure how you would go about that, or if it would help with the issues you're having).

On Thu, Nov 17, 2016 at 11:23 AM, Sam Popowich spopowich@gmail.com wrote:

I'm running multiple controllers in the discovery project: https://github.com/ualbertalib/discovery/tree/master/app/controllers

It probably depends on what you need to do - some of my controllers inherit from the main catalog controller so that I can override some behaviour, but keep the rest; other controllers handle completely separate functionality (i.e. the bento_controller).

On Thu, Nov 17, 2016 at 11:19 AM, Matthew Barnett < notifications@github.com> wrote:

In the current hydra stack I've run into enormous issues with trying to have more than one Blacklight controller/config active in the same application. This severely limits us in the case of Hydranorth, because all of our blacklist-dependent pages share the same config -- therefore, the catalog/search results have the same default sort order and sort options as the collection and community show pages, which isn't desirable.

We need investigation to see if this is still true in the up-to-date stack (docs suggest that the issue we have isn't intentional, but some kind of bug).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ualbertalib/Hydranorth2/issues/64, or mute the thread https://github.com/notifications/unsubscribe-auth/ABCtysiaEriiFRx88Rtd1tGCrCF9nGuKks5q_JqagaJpZM4K1oxO .

Fender F-35 Cordoba 45FP Ibanez M522SBS Loar LM-520 Lafferty LB

Fender F-35 Cordoba 45FP Ibanez M522SBS Loar LM-520 Lafferty LB

[mbarnett]

Yeah, they were talking about using the config separately at HydraConnect, too, which would work really well for us. I think a lot of our issues just come from being pinned to a really creaky version of Hydra/Sufia's Searchbuilder. The list of bugs I've hit with it in the last few months is...lengthy.

[ghost]

Ah, gotcha.