Jump to content

Creating vocabulary lists for specific texts


Keith Hill

Recommended Posts

Hi,

 

I'm trying to create a vocab list for words that occur in Gen 37, with a frequency of 1-99 times in the whole OT. Is anyone able to walk me through the process?

 

Thanks,

Keith

Link to comment
Share on other sites

Hi, Keith!

 

Try this: [COUNT 1-99] <AND> [RANGE Gen 37]

 

Enjoy!

Edited by Timothy Jenney
Link to comment
Share on other sites

Hello Tim

 

Why not a search for [COUNT 1-99]  Select Gen-Mal and then a new Tab with [HITS] <and> [Range Gen 37]?

 

With your solution I have in my Bible 183 hits and the other 503 hits.

 

Because he wrote "that occur the whole OT"

 

Greetings

 

Fabian

Link to comment
Share on other sites

I agree. I was trying to do it all on a single screen, as I was on my iPhone.

Link to comment
Share on other sites

Hello Tim

 

Thank, 'cause I was even not really sure if my solution is right.

 

Greetings

 

Fabian

 

To Keith, It was nice to help you. I'm in the learning process too...

Link to comment
Share on other sites

Hi maybe I am missing something here, but using the HMT-W4, both the methodologies give the same results (108 hits). They perform the same function.

 

The COUNT 1-99 will always count the entire search text, unless it is constrained by a custom range (not a RANGE command). The RANGE command then just displays the results from the pericope specified in the RANGE command.

 

That is exactly what the more complex Fabian system does. They are only not equivalent when the search text  (in this case) is not just the OT - e.g. if we were doing an English or other language text.

Link to comment
Share on other sites

I was going to post this last night and then my Mac played up for a bit. Anyhow here it is.

 

Ok so I wanted to suggest a way to do this with just a single tab. And it works in Greek lemma searches just fine. But if you go to an English text you get different numbers.

 

So the plot is to combine both of Fabian's tabs into one. Set a range in the Search Conditions to the OT. And use the combined search string of "[COUNT 1-99] <AND> [RANGE Gen 37]".

 

This works fine for Greek (LXX) and gives the same answer as the two tab method. It is also faster. Incidentally the search ranges defined in the search ranges file on the exchange are such that the OT range when run against Rahlfs does not include the entirety of Rahlfs. I just mention this so it's clear that the search condition range is having an impact in this test.

 

BUT .... If you try this with the ESVS you get very different results. I have not yet been able to explain it. I initially thought it was because you cannot do a lemma search in English but I'm searching the same English translation in both cases. The one tab solution finds 163 flex hits, the two tab 347.

 

 

 

Any ideas why this is ?

 

thx

D
 

Link to comment
Share on other sites

To clarify "in my Bible" was the Elberfelder-LEM. Also a text like the ESVS which Daniel also tested, and had different results. 

 

Greetings

 

Fabian

Link to comment
Share on other sites

Ahh - OK. Thanks.

 

My assumption was that if we wanted a vocab list (see OP) we wanted an OL text.

 

BTW - Daniel - no image attachment there 

Edited by Ken Simpson
  • Like 1
Link to comment
Share on other sites

I hate it when I do that. My Mac needed a sudden reboot in the middle of the prepped post and I forgot to reattach the image. Here it is.

 

post-32023-0-42968500-1433315378_thumb.jpg

 

Thx

D

Link to comment
Share on other sites

It’s very interesting, and I am not sure what’s going on here, but the two step process finds many terms wit “no key number” - I haven’t had enough time to see if that explains all the differences. But the interesting question is why is the single step process is not picking up the “no key number”.

 

I think it’s a question beyond my pay-grade...

Link to comment
Share on other sites

There are other possibilities as well. Sometimes translators will break up very long sentences. In those cases, they will often substitute a proper name (or a noun) for a pronoun in order to make its antecedent clear. The proper name (or noun) can get tagged with the key number for the original language word, rather than the pronoun. That means that those doing word counts in the original language text will get one more pronoun and one less proper name/noun than those vs. doing counts in the translation.

 

There are other kinds of instances, but I hope this example will help explain why both texts may be perfectly tagged, but the word counts are different.

Link to comment
Share on other sites

Hi Tim, thanks.

But the text is exactly the same (ESVS in this case) it’s just a different way of doing the searches - one a single step approach and the other a two-step. That’s why it doesn’t make sense to me.

Link to comment
Share on other sites

Ken beat me to it.

That's the thing that's puzzling. Clearly the two approaches to the search have different outcomes with non-OL texts.

 

Thx

D

Edited by Daniel Semler
Link to comment
Share on other sites

I actually wasn't addressing the two different search with a translated text. I was trying to explain a previous question: the differences that arise between a lemma search of an OL text and a key number search in a tagged translation.

Link to comment
Share on other sites

To put it simply, a COUNT search is case sensitive, while a HITS search is not.  So, if you do [COUNT 1] [RANGE gen], you'll get all exact forms that occur just once in the Bible, as they are used in Genesis.  If you do [COUNT 1] in one tab, then [HITS Tab1] [RANGE Gen], you'll get all case variants of the exact forms found in the bible, as they are used in Genesis.

 

A good, clear example of this can be shown in the HCSB.  In a normal COUNT 1 search, 'GOD' (in all caps) is a result in Acts 17:23.  However, when you take the hits of that search, it will now try to find all times God is used, regardless  of case, which adds in thousands of other uses, such as in Genesis 1:1.

 

I hope this helps clarify!

  • Like 1
Link to comment
Share on other sites

Ah. So I need to test an absorb this but, does this mean that the reason we get the same results in OL texts is that there is no case variation ?

 

thx

D

Link to comment
Share on other sites

Basically, yes.  For tagged texts, Accordance uses the proper lemma and inflected forms when doing COUNT and HITS, which are all case insensitive, so the results are consistent.  For keyed or untagged texts, all it has is the data in the text itself (and maybe key numbers and other items, of course), so words of different case are considered differently.

Link to comment
Share on other sites

OK - learning all the time. Thanks Joel.

 

Sorry Tim, I misunderstood what you were addressing. Blessings brother.

Edited by Ken Simpson
Link to comment
Share on other sites

Hi 

 

This is a related question. How do you search (in Greek or Hebrew) all the words which occur more than a certain number of times within a particular range? E.g. In Genesis 1, all the lemmas that occur more than 3 times.

 

Thanks

Link to comment
Share on other sites

Again, the key is the [COUNT ?] command, joined by the [RANGE ?] command. In this case, [COUNT 4-10000] <AND> [Range Genesis 1]

 

The [RANGE ?] command will accept any book of the Bible or any custom range. If you want to search within a book, say for a chapter, just create a custom range for that chapter.

 

The [COUNT ?] command will accept any number or range of numbers (e.g. 1-10, 99-199, 100-10000, etc.) Its default is to look for lemmas, but it can be modified to look for inflected forms or roots.  Here's the relevant section from Accordance Help:

 

The [COUNT ?] command searches only for words that occur the specified number of times in the search range. This command always uses a list of exact words (sensitive to case, punctuation, and accent).

The default COUNT search in a tagged text uses the list of lemmas that occur the specified number of times. Additional modifiers can be used inside the brackets to choose a different list for the search. These modifiers (Keys, Inflected, and Tags) are entered with an equal sign directly after the numeral. Only the first character of each modifier needs to be entered.

[COUNT 1] uses the list of lemmas that occur only once.

[COUNT 1=i] uses the list of inflected forms that occur only once.

[COUNT 1=t] uses the list of entire tags that occur only once.

[COUNT 1=k] uses the list of Key numbers that occur only once.

Example 1: To find all hapax legomena (words that occur only once) search for [COUNT 1].

Example 2: To find any complete tags that appear less than 10 times in the range, search for [COUNT 1-9=t].

Link to comment
Share on other sites

I must clarify here. If you use the COUNT with the RANGE command, the count applies to the range showing in the pop-up menu NOT to the range of the command. The range in the command will limit your hits, but the count first finds the number of words in the entire range, which is All Text by default. If you want words that occur more than three times in a book, for example, you must set that book in the Range pop-up menu, and use [COUNT 3+].

  • Like 1
Link to comment
Share on other sites

Oops, yes, what Helen just said. I misread the question.

Link to comment
Share on other sites

Thanks for that

 

I must be doing something wrong.

 

Tim, when I try your method on 1 Corinthians 12 [COUNT 4-10000] <AND> [Range 1 Corinthians 12] , the term θελω in verse 1 is highlighted even though the lemma occurs only twice in 1 Corinthians 12.

 

Helen, the same happens when I create a range for the book of 1 Corinthians in the pop up. 

 

Is there a simple way to search for only the words that occur more than a certain number of time in that particular chapter? Or do I need to do a construct chain search as in this link: http://www.accordancebible.com/forums/topic/15217-is-there-a-way-to-find-words-that-occur-more-than-once-in-a-chapter/? I'm still getting my head around learning how to use construct searches.

 

Thanks!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...