BUG?: Why didn't this search work?

Did a Basic Search in Everything for "Psalms of Solomon." I own Charlesworth's Old Testament Pseudepigrapha (OTP1 and OTP2) as well as Charles' Pseudepigrapha of the Old Testament, both of which have the full text. The search results landed on preliminary material about the text, but did not guide me straight to the text (e.g., to the title). Why would this be? The Topic Guide also does not bring me to the text.

Find more posts tagged with

Comments

MJ. Smith

When you search for "Psalms of Solomon" in a basic search you are looking for the string of letters "Psalms of Solomon" and (optionally) words that Logos recognizes as related e.g. "Psalm of Solomon". If you want the text of the Psalms of Solomon, you need a more complex syntax ... you just happened to ask for one of the more confusing. Do the following:

Open Charles, Robert Henry, ed. Pseudepigrapha of the Old Testament. Oxford: Clarendon Press, 1913.
Go to Psalms of Solomon and select the first verse of the first Psalm
Right click
Change the selection on the right to reference
Select Search this resource
You will get a search argument <Pseudepigrapha = Psalms of Solomon 1.1>. If you run this, you will get all the references to this verse.
Modify the argument to look like {Milestone <Pseudepigrapha = Psalms of Solomon 1.1>} . If you run this, you will get all the occurrences of this verse which should give you what you wanted

The take away:

to search for the string use: Psalms of Solomon
to search for references to the text use: <Pseudepigrapha = Psalms of Solomon 1.1>
to search for the text itself use: {Milestone <Pseudepigrapha = Psalms of Solomon 1.1>}

Rob Bailey

https://community.logos.com/discussion/comment/988489#Comment_988489

Following your instructions, I do not get the same search string you do. (I can't figure out how to copy the image from my computer, or I would paste it) My search string is just the verse I highlighted, all in quotes.

MJ. Smith

https://community.logos.com/discussion/comment/988490#Comment_988490

Oops - I left out a step. When you have right clicked to open the context menu, change the focus on the right hand side of the menu down to reference. While you are hovering the word reference will show on the right

Rob Bailey

https://community.logos.com/discussion/comment/988492#Comment_988492

Ok, that worked!

However, that is not a very easy way to find "Psalms of Solomon" in my library. I have to know first of all, that it is there (I frequently don't know what I have). In your demo, I had to go to it to find it, so how is that helpful? [:)]

MJ. Smith

https://community.logos.com/discussion/comment/988495#Comment_988495

Well ... er...ah ... <shuffle, shuffle> ...

The problem is that the coding for the <Pseudepigrapha = Psalms of Solomon 1.1> portion is not straight forward. I deliberately didn't include it so you could see the basic principle of the Search. Now that you understand the Search see https://wiki.logos.com/Finding_the_right_datatype_name_and_reference for the rest of the picture.

Rob Bailey

https://community.logos.com/discussion/comment/988496#Comment_988496

Well, that looks like something I don't want to have to learn.

I just did a Search Everything with "heading:"psalms of solomon"" and that worked great. (I thought I had done that before and it didn't work). However, doing that brings up a different problem I've experienced. When I see Pseudepigrapha listed in the search results and go to it, the entire text that comes up is highlighted in yellow, and there is no getting rid of it. Is there a way to get rid of the highlighting?

MJ. Smith

https://community.logos.com/discussion/comment/988497#Comment_988497

The highlighting can come from several sources. Try this:

The highlighting may be showing the results of the Search - close the Search
The highlighting may be showing a visual filter. Open the panel's visual filter icon and turn off any filter you think might be responsible.

Rob Bailey

https://community.logos.com/discussion/comment/988498#Comment_988498

Closing the Search tab did the trick! Thanks so much. There's another one I can delete from my "problems" list. [:)] (It would be nice to be able to keep my search results though, so I don't have to keep rerunning it.)

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/988489#Comment_988489

Right click

Change the selection on the right to reference

Select Search this resource

You will get a search argument <Pseudepigrapha = Psalms of Solomon 1.1>. If you run this, you will get all the references to this verse.

Modify the argument to look like {Milestone <Pseudepigrapha = Psalms of Solomon 1.1>} . If you run this, you will get all the occurrences of this verse which should give you what you wanted

Instead of steps 3-5, just select “Power Lookup” (instead of Search) on the menu and you'll be shown all translations/transcriptions you have in your library for that reference.

Jack Caviness

https://community.logos.com/discussion/comment/988499#Comment_988499

It would be nice to be able to keep my search results though, so I don't have to keep rerunning it.)

To do this, first clear the Search field—Esc works on the Mac OS. Then, select a different search type—i.e., if doing a Bible search, select Basic. The results highlighting should clear, and the Search panel remain open.

Dave Hooton

https://community.logos.com/discussion/comment/988526#Comment_988526

It would be nice to be able to keep my search results though, so I don't have to keep rerunning it.)

To do this, first clear the Search field—Esc works on the Mac OS. Then, select a different search type

?? That will lose search results.

But, you can't really keep results. You could try Print/Export... from the panel menu, otherwise re-run the Search from the Search History menu.

Rob Bailey

https://community.logos.com/discussion/comment/988526#Comment_988526

That worked for me! Thanks. I could click to a different type of search and back again, and the search string and results remained (e.g., Basic to Bible and back to Basic). (I use a PC).

I appreciate the tip!

Kiyah

https://community.logos.com/discussion/comment/988489#Comment_988489

MJ, Why doesn't the Milestone search also bring up the Lexham English Septuagint (LES), which also contains the Psalms of Solomon?

NB.Mick

https://community.logos.com/discussion/comment/988657#Comment_988657

Why doesn't the Milestone search also bring up the Lexham English Septuagint (LES), which also contains the Psalms of Solomon?

Very good observation! It seems that Ps Sol are sometimes tagged with two different datatypes, the one named "Pseudepigrapha", the other one "BibleLXX2".

I found that {Milestone <BibleLXX2 = Ps Solomon 1:1>} seems to get me all 16 works in my library that include the Psalms of Solomon - be they LXX or other works. The ones that fire for the milestone search above (4) will be included, since those four works are keyed to both datatypes. Most prudent would be to OR both milestone searches, just in case:

{Milestone <BibleLXX2 = Ps Solomon 1:1>} OR {Milestone <Pseudepigrapha = Psalms of Solomon 1.1>}

(note that this will increase the number of hits: those books that are double-tagged will fire twice per chapter so I get 20 hits in 16 articles/resources now)

Kiyah

https://community.logos.com/discussion/comment/988659#Comment_988659

Mine is actually tagged LXX-S, so yet another separate tag. Everything but the LES came up when I tried the BibleLXX2 search.

MJ. Smith

https://community.logos.com/discussion/comment/988659#Comment_988659

It seems that Ps Sol are sometimes tagged with two different datatypes, the one named "Pseudepigrapha", the other one "BibleLXX2".

Great catch - I had remembered this was true of some books but couldn't remember which ones. Now I know how to find them.

NB.Mick

https://community.logos.com/discussion/comment/988661#Comment_988661

Mine is actually tagged LXX-S, so yet another separate tag. Everything but the LES came up when I tried the BibleLXX2 search.

Strange - I worked from LES to figure out the datatype name, so it comes up with this. I see that the resource info refers to index "Bible (LXX-S)", which according to the wiki is referring to the datatype name BibleLXX2 (The -S stands for Swete's Septuagint - there must be an internal conversion in Logos, as this search finds Rahlf's type LXX as well - in fact the search gets the same results when run against BibleLXX, which is the datatype for Bible (LXX-R) indexes.

Can you post a screenshot for the search not working with BibleLXX2 and/or an alternative search term that does work?

Dave Hooton

https://community.logos.com/discussion/comment/988664#Comment_988664

the search gets the same results when run against BibleLXX

Or use plain old Bible datatype! The verse mapping is the same as BibleLLX, whilst BibleLXX2 has the same chapters, but usually more verses per chapter e.g. you need BibleLXX2 for Ps Sol 2:38. You are pretty safe looking for the first verse with any of the datatypes.

Phil Gons (Logos)

Did a Basic Search in Everything for "Psalms of Solomon." I own Charlesworth's Old Testament Pseudepigrapha (OTP1 and OTP2) as well as Charles' Pseudepigrapha of the Old Testament, both of which have the full text. The search results landed on preliminary material about the text, but did not guide me straight to the text (e.g., to the title). Why would this be? The Topic Guide also does not bring me to the text.

If you just want to navigate to that location in a resource, the easiest solution is to paste Psalms of Solomon into the Command Box and hit enter. It'll open your highest prioritized resource that has a milestone for that data type reference.

If it doesn't open the right resource, you can (1) modify your prioritized resources in the Library or (2) use the parallel resources menu to switch to another resource that has the same milestone coverage. In this case, the parallel resources menu will fall short, since we constrain the list of parallel resources by type, and this particular data type milestone can resolve in Bibles (i.e., the LXX), monographs (e.g., Charlesworth's OTP), and others. We might need to modify our type restrictions in cases such as this. I'll look into this with the team.

The short of it is that you're probably better off using the Command Box to navigate to data type references rather than running a search. Longer term search should do a better job of both finding instances of a reference and taking you to a milestone for a reference.

Let me know if you need more detail on any of this.