RESOLVED BUG: Deferred data updates

I slack off on nagging and what happens? The list of Bible with pericopes that are not supported in the Compare Pericope feature grows to nearly equal those that are supported. And that's based on sloppy visual checking on Bibles selected by slapdashery.

What can be done to encourage keeping features current? Is there anything that users could do to format the data in a manner that would speed the update process?

Find more posts tagged with

Desktop App

Comments

Kyle G. Anderson

Creating new Bible data types is something my team took over about a year ago. Unfortunately updating the pericope sets was something that fell between the cracks when we took that one.

I'm working on updating our processes so that updated pericope data will be shipped on or around the same time the new Bible is shipped. Once I get this process underway we should be able to go back and fill in the gaps of all the Bibles we've shipped over the last couple of years.

MJ. Smith

https://community.logos.com/discussion/comment/1075434#Comment_1075434

That is fantastic news Kyle. I'll try to be patient.

Kiyah

https://community.logos.com/discussion/comment/1075434#Comment_1075434

Creating new Bible data types is something my team took over about a year ago. Unfortunately updating the pericope sets was something that fell between the cracks when we took that one.

I'm working on updating our processes so that updated pericope data will be shipped on or around the same time the new Bible is shipped. Once I get this process underway we should be able to go back and fill in the gaps of all the Bibles we've shipped over the last couple of years.

Kyle,

Can you prioritize creating a Pericope set for the CSB on your list? Right now when I do an Inline search or use the Bible Browser with the CSB I cannot select to display the results by Pericope in the dropdown. In an Inline search I can only select Verse or Paragraph, in the Bible Browser I can only select Verse. I'm assuming this is because there is no Pericope set for the CSB, is that correct?

Also, for the NET Bible, I have the same issue above, plus I can't even select the NET Bible as a translation in the Bible Browser at all. There appear to be several reverse interlinear translations missing from the Bible Browser (NET, MEV, LES2, and ASV).

Also, see my post here about having a Pericope set for the UBS5 (since it has the English subheadings in that text. It looks like there is a Pericope set for the UBS4 but I don't own that edition).

MJ. Smith

https://community.logos.com/discussion/comment/1143862#Comment_1143862

plus I can't even select the NET Bible as a translation in the Bible Browser at all.

You might want to check for any other Bibles with a RVI that are missing from the Bible Browser ... getting them added is not automatic but requires action on the FL end.

Kiyah

https://community.logos.com/discussion/comment/1143867#Comment_1143867

plus I can't even select the NET Bible as a translation in the Bible Browser at all.

You might want to check for any other Bibles with a RVI that are missing from the Bible Browser ... getting them added is not automatic but requires action on the FL end.

That's why I included the MEV, LES2, and ASV along with the NET in the next sentence. Those are the new reverse interlinear sets that were released with Logos 9 in addition to the NET. I don't yet own the ESV-CE so I don't know if that one has been added to the Bible Browser or not.