RESOURCE BUG: missing Bible milestones

The Benedictine Monks of Conception Abbey. The Revised Grail Psalms: A Liturgical Psalter. Chicago, IL: GIA Publications, Inc., 2010. and The United States Conference of Catholic Bishops. The Abbey Psalms and Canticles. Washington, DC: United States Conference of Catholic Bishops, 2018. are essentially the first and second edition of the same book. However, the first contains the required bible milestones to make it work smoothly in Logos/Verbum while the second has only page milestones. This is unacceptable. In use, the psalm and canticle milestones are essential to find the required position in the book.

This is an error that I find it hard to understand how it "slipped" through as both volumes are type:Bible. Please correct ASAP so we receive the value for which we paid.

Find more posts tagged with

Desktop App

Comments

Elias Gali

MJ, the reason of why "The United States Conference of Catholic Bishops. The Abbey Psalms and Canticles" is currently missing the bible milestones is that it requires a new data type (so you can scroll alongside your preferred Bible). The data type is ready and the resource can get its much needed bible milestones, I'd expect that to happen before the next recycle queue (May 7th).

MJ. Smith

https://community.logos.com/discussion/comment/1296310#Comment_1296310

Are you saying it required a new verse map?

Christian Alexander

https://community.logos.com/discussion/comment/1296314#Comment_1296314

I agree we need it to be equivalent as to date of release. Do not release items that are not fully systemic in need. Missing Bible milestones is a huge mischaracterization. Was this a call from the publisher or from Logos Bible Software? If the latter it means Logos is doing inferior work in their own resources.

Rosie Perera

https://community.logos.com/discussion/comment/1296310#Comment_1296310

I agree with Christian. Pushing books out before they are fully functional does a disservice to users. I'd rather wait for a book that works than wonder when it will be fixed. Often those "fixes" slip through the cracks or take longer than intended. Just do it right the first time, even if it takes a bit longer.

Christian Alexander

https://community.logos.com/discussion/comment/1296325#Comment_1296325

[Y]

Yasmin Stephen

https://community.logos.com/discussion/comment/1296325#Comment_1296325

I agree with Christian. Pushing books out before they are fully functional does a disservice to users. I'd rather wait for a book that works than wonder when it will be fixed. Often those "fixes" slip through the cracks or take longer than intended. Just do it right the first time, even if it takes a bit longer.

We've accepted this sloppiness enough times, that now it's become a habit. Just ship whatever comes off the conveyor belt. Customers will complain but someone from Logos will come say it's been reported to the book team or (*cue applause*) a case has been created ...

MJ. Smith

https://community.logos.com/discussion/comment/1296353#Comment_1296353

We've accepted this sloppiness enough times, that now it's become a habit

Unfortunately, this is true but it seems to me that there has been a regression after some improvement in quality control. However, it is very hard to imagine how they could release a Bible without Bible milestones. I've long since lowered my expectations on patristic resources because of the "difficulty" in creating new datatypes.