II have two resources with the same exact name: "Biblia Hebraica Stuttgartensia: SESB 2.0 Version". Why is this and which should I hide?
There was a blog post (I believe) about the various BHS texts some time ago. The advice was to hide the version on the right (the 2016 publishing date) and keep the one on the left (the 2019 date). Sorry I can't find the original post which explained the reason(s) for this.
This is the SESB version to keep: LLS:1.0.204 2009-03-12T22:17:45Z BHSSESB.lbxlls hide the other: LLS:BHSSESB2 2006-12-16T00:22:51Z BHSSESB2.lbxlls I still hold some hope that someday we might be able to update BHS/WIVU, particularly since it is still in the base packages - if you hide it, you'll never see if it gets updated. I just wouldn't use that one, personally, in its present state, when there are more up to date options. The main structural difference between BHS/WIVU and BHS SESB is that the pronominal suffixes are split into separate segments in our snapshot edition. More on this in the last paragraph. All the old Westminster editions with the file names BHSWTSxx can be hidden, the BHW replaces all of them. Personally, I'd love it if everyone used LHB as their go-to Hebrew Bible, because I'd like to gather as much feedback on that edition as possible, since that's the one we can improve in house. There's another, perhaps more compelling, reason to do with pronominal suffixes (see below). In terms of searching, one major feature LHB currently has that BHW does not is searching on roots (in addition to lemmas), though BHW tags some morph features that LHB does not (like more particular tagging of the volitives for form vs. function). LHB has a slightly fuller treatment of Kethiv-Qere in that it includes the hybrid form with the consonants of the K and the vowels of the Q. (That was something we added to one older edition of the Westminster database, but probably shouldn't have - it wasn't part of their data and they got typo reports for a couple of my mistakes!) BHW and BHS SESB currently treat pronominal suffixes in the same 'segment' as the word they are attached to, and then have the suffix information tacked on to the end of the morph code. While LHB, AFAT and BHS/WIVU all split the pronominal suffixes out into separate segments. So if you're using only BHS SESB or BHW, you're going to miss out on some of our in-house data work that involves hanging data on individual segments. For example, we've done work disambiguating pronouns by tagging their referent (e.g. where 'him' or 'his' = Moses in some particular instance). You'll miss out on some of that context-sensitive information that comes not from the Hebrew Bible itself, but from our in-house ancillary databases, when you're working with databases that segment the text very differently than the LHB and AFAT. And this, then, is also a reason why one might keep BHS/WIVU around even if one had BHS/SESB - assuming BHS/WIVU gets an update at some point.
This is the SESB version to keep:
LLS:1.0.204 2009-03-12T22:17:45Z BHSSESB.lbxlls
hide the other:
LLS:BHSSESB2 2006-12-16T00:22:51Z BHSSESB2.lbxlls
I still hold some hope that someday we might be able to update BHS/WIVU, particularly since it is still in the base packages - if you hide it, you'll never see if it gets updated. I just wouldn't use that one, personally, in its present state, when there are more up to date options. The main structural difference between BHS/WIVU and BHS SESB is that the pronominal suffixes are split into separate segments in our snapshot edition. More on this in the last paragraph.
All the old Westminster editions with the file names BHSWTSxx can be hidden, the BHW replaces all of them.
Personally, I'd love it if everyone used LHB as their go-to Hebrew Bible, because I'd like to gather as much feedback on that edition as possible, since that's the one we can improve in house. There's another, perhaps more compelling, reason to do with pronominal suffixes (see below). In terms of searching, one major feature LHB currently has that BHW does not is searching on roots (in addition to lemmas), though BHW tags some morph features that LHB does not (like more particular tagging of the volitives for form vs. function). LHB has a slightly fuller treatment of Kethiv-Qere in that it includes the hybrid form with the consonants of the K and the vowels of the Q. (That was something we added to one older edition of the Westminster database, but probably shouldn't have - it wasn't part of their data and they got typo reports for a couple of my mistakes!)
BHW and BHS SESB currently treat pronominal suffixes in the same 'segment' as the word they are attached to, and then have the suffix information tacked on to the end of the morph code. While LHB, AFAT and BHS/WIVU all split the pronominal suffixes out into separate segments. So if you're using only BHS SESB or BHW, you're going to miss out on some of our in-house data work that involves hanging data on individual segments. For example, we've done work disambiguating pronouns by tagging their referent (e.g. where 'him' or 'his' = Moses in some particular instance). You'll miss out on some of that context-sensitive information that comes not from the Hebrew Bible itself, but from our in-house ancillary databases, when you're working with databases that segment the text very differently than the LHB and AFAT. And this, then, is also a reason why one might keep BHS/WIVU around even if one had BHS/SESB - assuming BHS/WIVU gets an update at some point.
Thanks. That was what I thought. But I could not tell if there was a reason to keep both. It is odd that the later file did not replace the earlier file, when they both have the same name and description.
I could not tell if there was a reason to keep both.
If you did some highlights, notes, to mark up relevant study or interesting things in the old version, you may want to keep it. I keep mine just to check if issues with BHS reported on the forums come from using the deprecated version. I tagged it as such (back then, based on Vincent's information or another in the same context) and enough people did so, so it will be shown in the community tags. I also changed the name and short name to make sure.
