collection problem, 6.7.0033
I've been working to tag all of the title in my library, and have been using some of the collection rules from the theology/denomination tag rules. Any way I created a collection called un-collected, used the rules box to add every title from my library, and the exclusions box to exclude any title included in any of the denom. stream, or denomination collections.
However, there have been a couple of times where I found an author / title in this group, that had actually been included in a collection.
Then a few days ago I decided to check my commentaries to make sure all of them were appropriately tagged, and included in the relevant collections. Tonight I noticed that the number of commentaries had increased by double without having purchased any new commentaries.
So I investigated the list, and books that were included book based collections (EG Commentaries on Amos), whose collections were on the exclusion list for the un-tagged commentaries collection, were still showing up in the untagged commentaries collection even though they were both in a collection, and properly tagged.
SO I added text to the rule that created the collection in the first place: ANDNOT Mytag:Amos, and the book remained in the collection. I did the same for books from other collections - genesis, daniel, and so forth.
I'm guessing that there is a limit to the number of arguments that can be included in a collection, and am wondering if it can be increased?
Make sense?
L2 lvl4 (...) WORDsearch, all the way through L10,
Comments
-
Sounds strange but from your description it doesn't sound as though the rule itself is too long.
Can you post a screenshot showing it?
And how many collections do you have in the "do not include" box?
0 -
One for almost every book of the bible. Genesis through Revelation. 1, 2, & 3 john are lumped together, as are 1 & 2 of any other book.
As to the theology and denomination tags collection, there are easily over a hundred. I gave up counting at 50, and was still on "Denom. Stream Converge Worldwide", and had not yet gotten to each of the individual "denomination" collections.
Note: the denomination collections are redundant really because all of their content was included in the denom stream collections. I was just trying to see if adding them fixed any of the titles I saw that should have been excluded but weren't. In any case, its a sizeable number of collections, and more than could be shown in a single screen shot.
I can however show the issue in a single shot:
You'll notice there are 9 commentaries on hosea that have the tag "hosea" and show up in this list despite being excluded. The sort view is "mytag" despite the appearance of being sorted by "title" as well.L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
Those remain whether "ANDNOT mytag:Hosea," is in the rule box or not.
The rule for the commentary collection is as follows:
Mytag:commentary, OR type:bible-commentary,
The rule for the Hosea collection is as follows:
Title:Hosea,Subject:Hosea AND Type:Commentary
Changing it to:
Mytag:Hosea OR (Title:Hosea,Subject:Hosea AND Type:Commentary)
Seems to fix it. So its possibly just a syntax error on my part. However, shouldn't I have been able to exclude any titles with that tag from the rule box like I was trying to do? Also, I will double check before posting them, but those 9 titles that have "Hosea" as a tag, but don't show up using using the rule "Title:Hosea,Subject:Hosea AND Type:Commentary" - perhaps this is showing us some metadata that is in need of correction.
Edit: Ok so I checked out the titles, ALL 9 are books that cover the minor prophets incl hosea. Surprised that my first rule didn't include them. I'll check the other rules and see if its more meta data issues, or if there is some other thing going on.
Still not sure why the "un-tagged" collection would have doubled in size...
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
In each case it seems to be a meta data issue (thus far).
Commentaries on prophecy that cover more than one book, not having the book name as a subject, commentaries on the minor prophets (As mentioned) that lack the books the commentaries cover as a subject. Commentaries on johanine books, lacking individual names of books in the subject field.
Adding: "mytag:book name here" seems to be fixing my issue.
But there are probably between 1 & 300 commentaries in my library with seemingly incomplete metadata
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
abondservant said:
I can however show the issue in a single shot:
In the screenshot there is a space between "mytag:" and "Hosea"
What happens if you remove the space?
0 -
Nope. Here is another screen shot for another book.
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
abondservant said:
Title:Hosea,Subject:Hosea AND Type:Commentary
Most commentaries are type "Bible Commentary" so suggest changing the rule to that.
May not address it but worth getting that sorted.
0 -
The Plus these Resources is not filtered by your filter string.
If you remove the item in Plus these Resources and add the filter text for those commentaries before your current filter text. It will work.
e.g.
Current filter text: ANDNOT Mytag:GK
(GK is my tag for Greek books)added the filter text for my collection 'All Bibles': Type:bible
by adding these & removing the Plus these Resources 'All Bibles' the filter text would be:
Type:bible ANDNOT Mytag:GKEdit:
The Plus these Resources and Minus these Resources are over-rides to what the filter string finds.
0 -
abondservant said:
However, shouldn't I have been able to exclude any titles with that tag from the rule box like I was trying to do?
The clue is that the rule box states "Start with resources matching:"
If you entered ANDNOT mytag:Hosea by itself in a new Collection you would see it did nothing. More importantly, if you then add a collection with the rule mytag:Hosea you would see it had no impact! You need something like type:commentary ANDNOT mytag:Hosea to get resources without that tag.
abondservant said:Changing it to:
Mytag:Hosea OR (Title:Hosea,Subject:Hosea AND Type:Commentary)
Seems to fix it.Be careful as this rule allows myatg:hosea on any type of resource. If you want them all to be commentaries, use
type:Commentary AND (Mytag:Hosea, Title:Hosea, Subject:Hosea)
--> be careful when using comma for OR as you can get unpredictable results.
Dave
===Windows 11 & Android 13
0 -
This thread proves that what would be awesome is if the resource metadata included Collections it was a member of, so that we could not only see it in the Library pane but then click on the column and group by it - then the resources not in collections would be easy to find and manage.
Or maybe Steve Clark's Logos Library Reporter could be updated to show it, I suspect it's a join of 2 or 3 tables to produce the list?
0 -
Don Awalt said:
Or maybe Steve Clark's Logos Library Reporter could be updated to show it, I suspect it's a join of 2 or 3 tables to produce the list?
Not going to happen.
The Collections database primarily has the Rules (text string you type into the collection), which would mean that i would have to write code that mimicked the interpretations for Logos' rules against the Library contents and all its flagging (Type, Tag, etc). That is no small task and keeping up with when Logos changes these rules or database would be an endless task.
0 -
steve clark said:Don Awalt said:
Or maybe Steve Clark's Logos Library Reporter could be updated to show it, I suspect it's a join of 2 or 3 tables to produce the list?
Not going to happen.
The Collections database primarily has the Rules (text string you type into the collection), which would mean that i would have to write code that mimicked the interpretations for Logos' rules against the Library contents and all its flagging (Type, Tag, etc). That is no small task and keeping up with when Logos changes these rules or database would be an endless task.
Ah make sense - when I made that remark I thought that calculation would already be completed in a table, but reading your reply I realized it needs to be done dynamically by them otherwise a new resource added isn't automatically dropped into a Collection whose rule it complies with. This may also be the reason we'll never see the Collections a resource is a member of as the data in a metadata column in the Library :-(
0 -
Don Awalt said:
This thread proves that what would be awesome is if the resource metadata included Collections it was a member of, so that we could not only see it in the Library pane but then click on the column and group by it - then the resources not in collections would be easy to find and manage
Do you mean this?
or this?
or something else?
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0
