Modernized config interface, added Collections browsing

[DBinaghi]

I've extended the plugin feature to Collections; so far, the two models are kept separate, but as it was suggested the ability to merge results (both Items and Collections) could be added (with a correspondent option in configuration).

Tieded up config interface, added tooltips, added option for Admin interface.

Hope it helps.

[zerocrates]

I think the way we'll probably go with this is to actually put the ability to search the elements better directly into the core Collections (and Files probably) implementations: all of the things that use the elements should be able to share the same filters for this stuff to some extent.

[DBinaghi]

I think the way we'll probably go with this is to actually put the ability to search the elements better directly into the core Collections (and Files probably) implementations: all of the things that use the elements should be able to share the same filters for this stuff to some extent.

I agree it's a good idea: it seems many users are trying to improve the search capabilities, so having it available by default (or even as a config option) seems like a good idea. I'd keep the option to choose which fields to use for search, as users could need to enable it only for specific fields.

[zerocrates]

So, I meant specifically just the "allow Collections to do advanced search" part would be integrated into the core.

This piece of having the elements linked and auto-searching for matches, where you pick the elements to enable that on and all that, that would still live in this plugin. (I think I understood your comment correctly as talking about integrating that part also).

[DBinaghi]

Yes, that's correct, John.
As you're at it, see whether the same could be usefully done for Files and/or Exhibits too (not sure whether it could be useful for any user, just thought the model could be applied to them too).