Library Filter Field for Collection

Page 1 of 1 (9 items)
This post has 8 Replies | 1 Follower

Posts 24
Ron Hale | Forum Activity | Posted: Thu, Jul 11 2019 12:06 PM

I have been using Logos since v.3, and have setup many collections over the years that fit what I do.  And, it would be great if I could search my library using "collection:".  I am surprised this Filter Field does not exist, especially since nearly every other conceivable Filter Field is included.  Thanks.

Posts 18670
Rosie Perera | Forum Activity | Replied: Thu, Jul 11 2019 1:53 PM

You can. Click the icon in the upper left of the Library to open the sidebar. Then click the little triangle beside Collection to open the Collection filter. Click on whatever collection name you're interested in seeing.

There's no way to combine these facets, though. So for example, you couldn't filter for books that are in Collection A AND Collection B.

Posts 24
Ron Hale | Forum Activity | Replied: Thu, Jul 11 2019 2:37 PM

Hi Rosie,

Yes I know it is possible to get to collections from the Collections filter.  I guess what I would find easier is instead of typing search patterns into two places like so:

It would be easier to just type below:

I know this may not be the best example, but you get the drift.

I am basically able to do what I want to do, just making a suggestion.

Thanks.

Posts 2085
LogosEmployee

https://wiki.logos.com/Library__#Search_Fields_that_you_can_use_in_the_Find_box

Try: {Collection "~ Subject (LoC): Theology"}

Note that you need to exactly match the desired collection name.

Posts 18670
Rosie Perera | Forum Activity | Replied: Thu, Jul 11 2019 6:18 PM

Andrew Batishko (Faithlife):
Try: {Collection "- Subject (LoC): Theology"}

That's not a particularly realistic example. Who would name their collection that?

Something like this is more likely:

{Collection "Theology: Puritan"}

And note that Collection is case-sensitive. I first tried it as {collection "Theology: Puritan"} and it didn't work.

It's too bad, because the other filter fields (e.g., author:calvin) are case-insensitive. Author:Calvin works just as well. I really prefer case-insensitivity for filtering.

Posts 5025
DIsciple II | Forum Activity | Replied: Thu, Jul 11 2019 6:45 PM

Rosie Perera:

Andrew Batishko (Faithlife):
Try: {Collection "- Subject (LoC): Theology"}

That's not a particularly realistic example. Who would name their collection that?

Ron Hale named his collection with that name hence why Andrew used it in his example.

Posts 18670
Rosie Perera | Forum Activity | Replied: Thu, Jul 11 2019 10:26 PM

DIsciple II:

Rosie Perera:

Andrew Batishko (Faithlife):
Try: {Collection "- Subject (LoC): Theology"}

That's not a particularly realistic example. Who would name their collection that?

Ron Hale named his collection with that name hence why Andrew used it in his example.

Whoops! Embarrassed

Posts 24
Ron Hale | Forum Activity | Replied: Fri, Jul 12 2019 10:50 AM

Hi Team, thanks for the feedback.

I was able to use the following search successfully. author:spurgeon AND {Collection "Theology - Soteriology"}

Did not know you could use { } in Library search.  I also agree that case sensitivity makes it harder.  Further, the collection name has to be exact.  Would be nice if you could put in a partial collection name or use wild card like so:

author:spurgeon AND {Collection "Theology"}

Which would search all books within collections that had theology as part of the collection name.

Posts 2085
LogosEmployee
Andrew Batishko (Faithlife) | Forum Activity | Replied: Fri, Jul 12 2019 11:29 AM

Ron Hale:
Further, the collection name has to be exact.

The syntax is not particularly user-friendly, and is not even formally documented. It was created explicitly to be an exact match in order to support the faceting functionality, which requires exact matching.

The syntax of the various exact match extensions were detailed in public primarily to support power users creating collections that would benefit from better performance and the exact matching that it provides.

There are currently no plans to make the syntax of any of these extensions support partial or case-insensitive matches.

Page 1 of 1 (9 items) | RSS