Biblical Term NOT appearing for a specific verse

Question

I know how to add a term to a project’s Biblical Terms.
But sometimes in some verses, the term I am looking for is just not there.

Why do not ALL my terms appear in ALL verses?
It is very frustrating when I want to demonstrate this tool and the term I want them to check, use as an example is just not there in that verse.

I can attach screenshots if needed.

Roelie

Answer 1

A very old reason for that behaviour is if the \id lines at the very top of the file get edited and no longer match. This line identifies the file and if it is changed them paratext biblical terms tool can’t find the verses in that book.

Do a find on \id with show text ticked and all books selected. The line should look like this in every book

\id MAT - Project name

The MAT must be the three letter book code that Paratext uses to identify the book. You see it at the top menu line when you select which book you want to edit. Teams sometimes translate that into their own language, putting something like Matiyu instead. This
is wrong.

The project name must match the long project name that you see in the project properties and settings menu. Teams often change this too. If they wish to change this (a legitimate change may be from Language Name NT to Language Name Bible), they should change
it in project properties first.

Then do your find and make sure that every \id line exactly matches the others, differing only in using the proper book code and with the project name matching the project properties project name.

After that, the biblical terms tool should work as expected.

Blessings Shegnada

Comments

WOW! Thanks! That’s got to be the best kept PT secret ever! Never before has adding a term to my project’s KT list been so instant and painless as it is now, after changing that \id line to have the full project name in it. We had always been told that as long as the original 3-letter ID is accurate, everything else after that doesn’t matter and is up to the team. And all my complaints about difficulties adding key terms to my project’s list with endlessly switching around, trying and failing, never found me a solution. I’ll watch it a while. But for now, the improvement is just mind-boggling!

---

Another source of problems is how you are adding terms to your list. If you are using the method where you find the verses using a Bible in a major language Bible such as English or French, then they do not always translate the same Greek or Hebrew lemma the same way. I go through the process of checking for the term in the All Biblical terms list and adding it from there, or if it is not there, I add it from the source language tool doing a lemma search first.

---

Yes the old problem of search and replace being used with out understanding the power of it.

---

I’m just now realizing some of my projects are not consistent in having the file name after \id, but I haven’t noticed any problem myself. If you could help me understand this phenomenon, what exact functionality within the Biblical Terms tool is enabled/hindered by having/not having the project name following the \id in the individual books?

As a note, it seems that creating new books in a project puts this project name into the \id line, but importing books into a project does not. As the Biblical Terms tool is an incredibly essential tool, if this project name is indeed very important for the functioning of the Biblical Terms tool, then perhaps PT should reproduce the correct name by default at book creation in the target project, whether that book is created or imported.

---

Phil:

If you could help me understand this phenomenon, what exact functionality within the Biblical Terms tool is enabled/hindered by having/not having the project name following the \id in the individual books?

Paratext ignores everything following the book ID in the \id marker, so nothing can be broken or enabled by having anything specific following it.

---

Thanks very much! Good to know.

---

I normally do add them from the source language and I normally look for them in the source languages alphabetical list

Answer 2

Another common problem is versification mapping problems. This is most commonly caused by users customizing the versification of the project using a custom.vrs file, but not putting in the mapping lines that let Paratext know how a given verse maps to the original verse.

A screenshot might be helpful.

Answer 3

Thanks a lot for the suggestion to look at the book ID -I found a few that were not correct!
But the term still does not appear.
When I wanted to add it, the OK button was not active.
From inside the Terms window, it said it has been added - but it still doesn’t show up there.
This time I was looking at the small (and maybe insignificant) term for neighbour רֵעַ

By the way, why do so many term don’t appear in the Terms List?
I am always working with the selection All Terms.
Thanks
Roelof

Answer 4

anon718622:

By the way, why do so many term don’t appear in the Terms List?

Terms that only appear in books that are not in the project are always filtered out. Could that be what you are seeing?

Comments

Every now and again, in different projects, when I want to look at a Key Term, it is just not there.
There are other Key Terms in those projects, it is not as if there are no term at all. Look at the attached screen shots I started to gather:

Paratext key term not there Didaskale Luk10.25 Sghn1366×664 56.1 KB

Paratext key term not there epistata Luk5.5 Sghn1366×709 65.4 KB

Why would terms like DIDASKALOS AND EPISTATES not appear in this project?

---

This short contribution fixed our problem, thank you muchly!!

---

We recommend that you create all of the books you plan to translate when setting up the project. It simplifies many things not just that Biblical terms that are shown in the Biblical terms list. Another would be so you can define all of the book names and their abbreviations in the Scripture Reference settings.

In the follow video about project Biblical terms lists, I mention the effect of not creating all the books you plan to translate in the beginning of your translation program. Project Biblical Terms: Find Specific Terms on Vimeo

Answer 5

Sorry, but what are we supposed to see in those screenshots?
Maybe because I only read English, but I don’t see anything that points to a missing term.

Answer 6

That the Greek words that is highlighted in yellow dont appear in the Key Terms window original language column.
I am showing ALL the Biblical Key terms that appear in the Key Terms window.
Why is Didaskalos or Epitate not in the small Biblical Key Terms Original Language column?

Answer 7

Paratext key term not there Didaskale Luk10.25 Sghn1366×664 57.6 KB

Comments

Roelof, The title bar of the Biblical terms tool showing in your screen shot says, “Major Biblical terms”. You say that you want to work with a term that is on the “All Biblical terms” list. You will need to either temporarily change the Biblical terms list being used by the Biblical terms tool to “All Biblical terms”, or associate the project to the “All Biblical terms” list. This is done on the Associations tab in the Project properties dialogue window.

image963×977 215 KB

It you want to use words from multiple list, then you can make a custom Biblical terms list.

image962×1006 260 KB

---

I just confirmed that “ἐπιστάτης” and “διδάσκαλος” are not in the “Major Biblical terms” list, but they are in the “All Biblical terms” list. I would recommend associating your project to the “All Biblical terms” list or making a custom list that has the terms your interested in. The “All Biblical terms” list has all but about 5 of the words that occur in the Grk text. These are small functor words like eis, so unless you are doing a major study on Koine Greek discourse, the words you need should be there.

I should also mention that it is possible to add phrases to one’s custom Biblical terms list. Some people like to add terms such as “Kingdom of God”, Kingdom of Heaven, Son of Man etc, to their Biblical terms list. The Help explains how to do this. Write back if this is a need that you have and are not able to add a phrase.

Answer 8

Had similar problems, this thread helped me fix it for one project:

All the “normal” books were already selected or activ in > project settings > books and appeared in blue.

But several (empty) books had not been created yet, in order to not-clutter the navigation. So PT has been withholding many key terms over several years, just because certain books were not created.

I would think such “best kept secrets” should be shouted or sung from all roof tops. This is a happy day, as perceived “erratic” PT behaviour has been cleared up and is gone now.