ACKNOWLEDGED BUG: BONKERS Morphology search that ignores coding scheme

It would be much easier to show the extent of the problem if the Search results were expandable/collapsible by resource. (Hint, hint).

Open Search Panel
Select Morph
Select a collection that should include everything with morphological coding.
Select one of the smaller morphological coding scheme e.g. GRAMCORD
Choose some morphological coding to search for
Get frustrated that the first result is the application of a Greek only scheme to Latin ...
Add to you frustration by working your way down to Biblia Hebraica transcripta - the application of a Greek only scheme to Hebrew
Drink your coffee while you rue the fact that there is no data that will lead you to the erroneous results applied to Coptic or Gothic ... and recognize that the poor FL people logging problems don't necessarily share your sense of humor.

Find more posts tagged with

Comments

Dave Hooton

Open Search Panel

Select Morph

Select a collection that should include everything with morphological coding.

Select one of the smaller morphological coding scheme e.g. GRAMCORD

Choose some morphological coding to search for

Get frustrated that the first result is the application of a Greek only scheme to Latin ...

Add to you frustration by working your way down to Biblia Hebraica transcripta - the application of a Greek only scheme to Hebrew

Drink your coffee while you rue the fact that there is no data that will lead you to the erroneous results applied to Coptic or Gothic ... and recognize that the poor FL people logging problems don't necessarily share your sense of humor.

6. I can't reproduce without GRAMCORD morphology. The Vulgate should only respond to Logos morphology for Latin, Greek and Hebrew.

7. I can't reproduce without GRAMCORD morphology, but at least you can find that it should be <BHtMorph ...>, which is the only one offered if you choose that resource in the Morph Search. For your search, further restrict the filter to Greek resources!

8. Get rid of your GRAMCORD resources and you won't have any issues[:)]

Bradley Grainger (Logos)

When I follow your steps and search in a custom collection (or "All Resources") for <GrMorph ~ M?>, I only get hits (as expected) in two GRAMCORD resources: NA27 and NA27 Int.

I'm not sure how to reproduce the problem you're showing (or even how it's possible to get hits in a Latin resource when searching for Greek morph).

If you explicitly search just the Clementine Vulgate for GRAMCORD Greek Morph coding, do you get results?

MJ. Smith

https://community.logos.com/discussion/comment/1075996#Comment_1075996

I followed my steps with identical results although I searched a few more resources as I had download some that had been in the cloud. I got exactly the same results.

If I search only the Clementine Vulgate, I get no results.

If I search "type:Bible lang:(Greek, Latin)", I get no results

If I search lang:Greek, I get no results

If I clear the search argument and re-enter it, then I get results on lang:Greek of 2 resources

If I clear the search argument and re-enter it, then I get results on type:Bible of 5 resources including Vulgate

If I clear the search argument and set the resource to only the Clementine Vulgate, I can only enter one of the Logos morphology. Using Logos Greek (yes on a Latin text) I get over 66,000 results

In short, it appears that the search argument MUST be cleared and re-entered if other parameters change and that results are inconsistent.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1076008#Comment_1076008

I'm trying to follow your instructions, but I'm not getting the same results.

For example, if I'm searching for <GrMorph ~ M?> in Clementine Vulgate, then change the resource picker to "lang:Greek", I instantly get results in GRAMCORD-tagged resources as soon as I pick the new resource range from the drop-down list.

I might need to see a screencast in order to figure out why you're getting unexpected results.

If I clear the search argument and re-enter it, then I get results on type:Bible of 5 resources including Vulgate

I still don't know why you would ever get GRAMCORD results in a Latin Bible.

Philana R. Crouch

https://community.logos.com/discussion/comment/1076008#Comment_1076008

If I clear the search argument and set the resource to only the Clementine Vulgate, I can only enter one of the Logos morphology. Using Logos Greek (yes on a Latin text) I get over 66,000 results

MJ,

The Clementine Vulgate has RVI's for both Greek and Hebrew. I think that is why you are getting those options.

MJ. Smith

https://community.logos.com/discussion/comment/1076588#Comment_1076588

The Clementine Vulgate has RVI's for both Greek and Hebrew. I think that is why you are getting those options.

I'll go through the odd ones and see if you are right. That is a very plausible explanation.

Philana R. Crouch

It would be much easier to show the extent of the problem if the Search results were expandable/collapsible by resource. (Hint, hint).

Open Search Panel

Select Morph

Select a collection that should include everything with morphological coding.

Select one of the smaller morphological coding scheme e.g. GRAMCORD

Choose some morphological coding to search for

Get frustrated that the first result is the application of a Greek only scheme to Latin ...

Add to you frustration by working your way down to Biblia Hebraica transcripta - the application of a Greek only scheme to Hebrew

Drink your coffee while you rue the fact that there is no data that will lead you to the erroneous results applied to Coptic or Gothic ... and recognize that the poor FL people logging problems don't necessarily share your sense of humor.

MJ,

I'm not able to reproduce this at all in 8.10 Beta 2. Can you confirm that you can still reproduce this? With GRAMACORD I get results in 4 Greek resources as I would expect to.

MJ. Smith

https://community.logos.com/discussion/comment/1076593#Comment_1076593

I get 5 results, the first of which is still the Clementine Vulgate. Is it a bug that I cannot collapse on the resource so I can easily see what the other 4 are?