Can I simplify this Search?

"Psalm 152",  "Ps 152" ,<Add Ps 152-155> ,"Psalm 153",  "Ps 153", "Psalm 154",  "Ps 154", "Psalm 155",  "Ps 155"

This search yields 264 results in 142 articles. I personally think the 3rd term should be sufficient and would remove the false positives. Any idea how to simply the search argument? If not, would adding community tagging with the right Add Ps reference "solve" the problem? Or do I have to wait for Logos to properly tag the references?

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."

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 36,109

    Compared to using your search, I get more results from:-

    <Pseudepigrapha More Psalms of David 152-155>, <BibleOTP Ps 152-155>

    There are a few untagged ones like Psalm 154..., Psalm 155... but they are part of a title.

    Strangely <BibleDSS Ps 152-155> duplicates results from <BibleOTP Ps 152-155>!

    Dave
    ===

    Windows 11 & Android 13

  • Francis
    Francis Member Posts: 3,885 ✭✭✭

    MJ. Smith said:

    I personally think the 3rd term should be sufficient and would remove the false positives.

    What kind of false positives are you getting?

    BTW, I notice that searching from a reference in the context menu insert a = in the search string and that it needs to be removed in order for it to work (e.g., <BibleOTP = Ps> which does not work, but <BibleOTP Ps> works). Has this been reported already?

  • MJ. Smith
    MJ. Smith MVP Posts: 54,797

    Thanks Dave & Fracnis. I've got to run but will try further when I get back.

    Francis, the false positive I noticed were of the form "153, psalms or even ..."

    Dave, my counts:

    with my search     264 results in 65 resources

    with your search   252 results in 38 resources including some not in mine

    with added term    267 results in 38 resources

    with yours & mine 424 results in 71 resources

    No Francis, I don't think the right click search error has been reported

    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."

  • Francis
    Francis Member Posts: 3,885 ✭✭✭

    "(Ps, Psa, Pss, Psalm, Psalms) (151, 152, 153, 154, 155)", <BibleOTP Ps 152-155><Pseudepigrapha More Psalms of David 152-155>, <BibleOTP Ps 152-155>

  • MJ. Smith
    MJ. Smith MVP Posts: 54,797

    I've modified it a bit because some Dead Sea Scroll versions were still being missed ... I'm still not sure it is complete but:   <BibleOTP Ps 152-155>, <Pseudepigrapha More Psalms of David 152-155>, "(Ps, Psa, Pss, Psalm, Psalms) (152, 153, 154, 155)", "Syriac Psalm", <DSSSE = 11Q5 Col. xviii> seems to work best so far ... although I think I need to identify each possible DSSSE element ...

    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."

  • Francis
    Francis Member Posts: 3,885 ✭✭✭

    MJ. Smith said:

    although I think I need to identify each possible DSSSE element ...

    I don't have the time to do this myself right now, but perhaps there is a resource that lists the ranges in which these psalms are found. Or the DSS index may be used to put together such a list. 

    See here.

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    Strangely <BibleDSS Ps 152-155> duplicates results from <BibleOTP Ps 152-155>!

    This isn't any more strange than the fact that <BibleESV Gen 1> duplicates results from <BibleNIV Gen 1>.

    According to the Wiki, parts of Psalms 152-155 are supported by the following Bible datatypes: dssdssb, and otp.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • MJ. Smith
    MJ. Smith MVP Posts: 54,797

    But according to the Logos list of supported Bible books they should the Ad Ps or Add Ps which bring forth zero results in my library ....

    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."

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    MJ. Smith said:

    This search yields 264 results in 142 articles. I personally think the 3rd term should be sufficient and would remove the false positives. Any idea how to simply the search argument? If not, would adding community tagging with the right Add Ps reference "solve" the problem? Or do I have to wait for Logos to properly tag the references?

    As you know, not all of the additions to the Psalms are properly tagged (and some older/Vyrso resources probably never will be). The best syntax to find those Psalms without using datatype references is probably this one:

    (Ps, Pss, Psalm) BEFORE 1 WORDS ("152","153","154","155","152-153","152-154","152-155", "153-154","153-155","154-155")

    Then to find those that are tagged, you can use this:

    <BibleOTP ~ Ps 152-155>, <Pseudepigrapha ~ More Psalms of David 152-155>

    Personally, I don't think there's any point including the DSS fragments, any more than you'd include them for Bible searches, although if you did it would be:

    <DSSSE ~ 11Q5>

    You can put all that together as:

    ((Ps, Pss, Psalm) BEFORE 1 WORDS ("152","153","154","155","152-153","152-154","152-155", "153-154","153-155","154-155")), <BibleOTP ~ Ps 152-155>, <Pseudepigrapha ~ More Psalms of David 152-155>, <DSSSE ~ 11Q5>

    (Edited to remove unwanted references to Psalm 151).

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Francis
    Francis Member Posts: 3,885 ✭✭✭

    I used "BEFORE 1 WORDS" in one of my attempts, but reverted to the "(...) (...)" format because the former included instances in which punctuation was present between the two terms (since it is not counted as a word).

    Another challenge is that DSS psalms are often written Psa where the a is a superscripted character. "Psa" does not return these instances.

    It seems to me that the ability for searching special characters would be a useful addition to the search capabilities in Logos. This would apply in the case above but also others like searching sigla.

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    MJ. Smith said:

    But according to the Logos list of supported Bible books they should the Ad Ps or Add Ps which bring forth zero results in my library ....

    It's Add Ps, not Ad Ps.

    And that's the additional psalm (singular), not additional Psalms plural.

    So <Add Ps> is equivalent to <Psalm 151>.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    Francis said:

    I used "BEFORE 1 WORDS" in one of my attempts, but reverted to the "(...) (...)" format because the former included instances in which punctuation was present between the two terms (since it is not counted as a word).

    I don't think the punctuation matters, but BEFORE 1 WORDS doesn't find occurrences in footnotes, so your method is probably better.

    Francis said:

    Another challenge is that DSS psalms are often written Psa where the a is a superscripted character. "Psa" does not return these instances.

    I've not seen an example where that's an issue. 11QPSa finds 11QPSa.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • MJ. Smith
    MJ. Smith MVP Posts: 54,797

    I need to get to bed ... and Logos has become extremely slow but your search is coming up with only about 1/2 the resources that my search does, even removing the DSSSE ... but I should be heading to bed as it is 3:24 AM ... I said I was a night owl.

    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."

  • Francis
    Francis Member Posts: 3,885 ✭✭✭

    I've not seen an example where that's an issue. 11QPSa finds 11QPSa

    It would appear that you are right! I looked up the last reference from which I searched and I had not noticed that there was a typo that interfered with my search (it was written 1 1QPsa instead of 11QPsa). I reported the typo and fixed the search and all is well.

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    OK, here's my final offer:

    "(Ps, Psa, Pss, Psalm, Psalms) (152*, 153*, 154*, 155*)", <BibleOTP ~ Ps 152-155>, <Pseudepigrapha ~ More Psalms of David 152-155>, <DSSSE ~ 11Q5>

    That gives me 3,556 results in 1,179 articles in 358 resources; compared with 651 results in 300 articles in 133 resources. I don't see any false positives, either.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Francis
    Francis Member Posts: 3,885 ✭✭✭

    <DSSSE ~ 11Q5>

    This is still too broad, as 11Q5 includes other psalms, use <DSSSE = 11Q5 Col. xxviii> <DSSSE = 11Q5 Col. xviii> instead.