HELP! my memory cache is full
Comments
-
Mark Barnes said:
because it would be confusing if Top Bibles kept changing depending on what passage you were studyin
But in real life my top Bibles do need to constantly change e.g. LEB LXX for books not otherwise translated; JPS for Masorectic set otherwise NRSV (not CE). In real life I used to reset my top Bibles constantly ... now I've moved more towards layouts but may have to move back given this thread. Assuming canon from top Bible isn't a smart assumption.
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."
0 -
fgh said:
They already do, don't they? I'm too tired to try, but prioritizing e g Fox, Göttingen, JPS, NA28, NABRE and NRSV, in that order, should have that effect, shouldn't it?
No, because if you choose "Top Bibles" in a search/text comparison, then Logos will just run that search/TC in your five top Bibles. If you're searching in the NT and one of your Bibles is an LXX, Logos won't add in your sixth Bible to make up, it will just display no results from the LXX.
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!
0 -
Mark Barnes said:
Logos won't add in your sixth Bible to make up,
Which to me is a bug affecting all Christians who love the JPS.
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."
0 -
Mark Barnes said:fgh said:
They already do, don't they? I'm too tired to try, but prioritizing e g Fox, Göttingen, JPS, NA28, NABRE and NRSV, in that order, should have that effect, shouldn't it?
No, because if you choose "Top Bibles" in a search/text comparison, then Logos will just run that search/TC in your five top Bibles. If you're searching in the NT and one of your Bibles is an LXX, Logos won't add in your sixth Bible to make up, it will just display no results from the LXX.
Ah! Being tired, it didn't occur to me that you were using "top Bibles" as a collection name, especially as you didn't capitalize the 't' the first time. I'd done so many Cross Reference PG's and looked at so many verse lists, that my mind automatically thought only of popups.[:)] And in those I believe you would get six different texts/translations if you prioritized like that.
And for the purpose of this thread, popups are what matters to me. If I put an NRSV first in my Priority list and tell it to "apply only to" Ps 151, I neither expect nor want the NRSV to turn up in every other popup as well. That's illogical as well as annoying.
But you're right, Search and TC need to be considered as well. I just don't think of top Bibles in that connection, as I never use the Top Bibles collection. It's not very practical when your top Bibles aren't in the same language... When I think about prioritization, I think about what I want done with links.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
And for the purpose of this thread, popups are what matters to me. If I put an NRSV first in my Priority list and tell it to "apply only to" Ps 151, I neither expect nor want the NRSV to turn up in every other popup as well. That's illogical as well as annoying.
That does work correctly.
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!
0 -
Mark Barnes said:
If you're searching in the NT and one of your Bibles is an LXX, Logos won't add in your sixth Bible to make up, it will just display no results from the LXX.
I just tried a Top Bibles search with the following prioritization:
Not very helpful:
It seems to me that a Top Bibles search ought to start by looking at the reference range (down to book level should be enough), and then exclude Bibles that don't include that range and replace them with more relevant ones. Some 'wrong language' replacement would also be helpful, but that's trickier. It seems Logos searches the morphology as well, so the UBS4 is actually useful even in an English search, while the BHS is not (an OT search like this shows only the RSVCE -- so much for 'Top Bibles'). And Swedish/English would be even trickier. Normally a Swedish Bible would be irrelevant for an English search, but then there are those words that are the same...
Mac Pro (late 2013) OS 12.6.2
0 -
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
It seems to me that a Top Bibles search ought to start by looking at the reference range (down to book level should be enough), and then exclude Bibles that don't include that range and replace them with more relevant ones.
That's more complex than you imagine, given the different order of the Bible books in different versions. As a pre-defined collection "Top Bibles" is something of a beginners' feature — as you said, you rarely use it, and nor do I. It's best kept simple, therefore.
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!
0 -
fgh said:
What do you mean by 'correctly' in this case?
I meant that it worked exactly as you described. The only bug that's been discussed on this thread is that the Cross References section of the passage guide only includes references that are supported by the datatype of the most highly prioritized Bible. A work-around is to change your prioritisation, but that as other adverse affects, as I pointed out. But there are no other problems with Bible prioritisation that I'm aware of.
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!
0 -
Mark Barnes said:
there are no other problems with Bible prioritisation that I'm aware of
If "apply only to" nevertheless applies it to everything else as well, I'd say that is a problem. A UI shouldn't say one thing and then do something else. If I find that confusing and unintelligible after nearly three years, you can bet a newbie finds it even more confusing and unintelligible.
Mark Barnes said:That's more complex than you imagine
I imagine it is.[:D]
Mark Barnes said:As a pre-defined collection "Top Bibles" is something of a beginners' feature — as you said, you rarely use it, and nor do I.
Eh? It's not because I'm 'advanced' that I don't use it; it's because I'm Swedish. The current implementation wouldn't be less of an issue if I were a beginner, it would be far more of an issue. Now I know how to work around it, as a beginner I wouldn't.
Mark Barnes said:It's best kept simple, therefore.
Exactly. And for those of us whose first language isn't English, or who want a Greek and/or Hebrew Bible among the top 5, it isn't simple. It's very complex. From a user perspective, my suggestion would make it far more simple (though I'm sure the developers' perspective is another[:)]).
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
If "apply only to" nevertheless applies it to everything else as well, I'd say that is a problem.
But it doesn't apply it to everything else as well. Prioritisation works as advertised, and there are no bugs and no problems.
Where there might be a problem is how "Top Bibles" are chosen. If you think that "Top Bibles" should be a dynamic collection, calculated at query time and change depending on the passage that is being examined, then "Top Bibles" doesn't work. If you think that "Top Bibles" is a simple collection of the five most highly prioritised Bibles in your library, and that it should only change if you change your prioritisation, then "Top Bibles" works very well. It's a design choice, not a bug.
I do understand why you (or others) might want it to adjust every time you do a search, but that's not how it's been designed. And there are advantages with it running the way it does now. For example, if you want to compare how frequently an English word was used in the OT and the NT, you can set up two searches (one on each range), and get a comparable result.
Top Bibles is a very simple concept. It's like the "Go" button on the home page. It's primarily for people learning Logos. Once you've learned how to make collections, you'll probably not use it again (because you can create a collection of Swedish Bibles or English Bibles). So whilst I agree that it's doesn't really work for Swedish customers, I don't think adding complexity is going to help.
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!
0 -
This is a case where I'd say Verbum requirements differ from Logos proper partially because of the instances in which everything translated in a Bible translation does not always appear in the Logos resource
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."
0
