New International Biblical Commentary (NIBC) does not show in Passage Guide

Well, so far, I like my new NIBC, but a few issues that maybe relate to the metadata for the set.

1) In Logos 4.0b, the NIBC titles do NOT appear under the "Commentaries" portion of "Passage Guide".

In "Library", sorted by Type, all the NIBC titles appear correctly under "Bible Commentaries", but they dont show up during Passage Guide.

2) The "short name" title sometimes show up on the tab, and are good. e.g. "NIBC Ro", but at other times the "long name" title is used, and for the NIBC set, these are most unhelpful. e.g. "Romans".

This does not seem to happen for other sets. Test case: Add all the Commentaries you have for John to an otherwise emtpty layout. Most titles, will have their set-name in the tab. For NIBC, is only says "John", which is not so helpful. Most everything else I have would have used "NIBC John" as the expected format on the tab.

The problem seems to be that the "long name" = "John", and is shorter than the more useful "short name" = "NIBC Jn".

3) This is out-of-place in the Logos 4 forum, but a search/filter for NIBC in Logos 3 Library window, finds the titles, but "Biblical Commentary" does not.

I have to say, its only point (1) I see as a big problem. I wish them to show up in my passage guide please.

Regards.

Find more posts tagged with

Comments

Kevin A. Purcell

1) In Logos 4.0b, the NIBC titles do NOT appear under the "Commentaries" portion of "Passage Guide".

When you run a passage guide the commentaries listed are your prioritized commentaries unless you have not prioritized any. In that case they are the program defaults. Under the first few listed is a "more" link. Did you click that. If not that is likely where you will find the NIBC listed. If you want it higher then prioritize it in the library.

2) The "short name" title sometimes show up on the tab, and are good. e.g. "NIBC Ro", but at other times the "long name" title is used, and for the NIBC set, these are most unhelpful. e.g. "Romans".

This also happens for NICOT & NICNT. The office name of the book is "the book of romans" and then has the set as maybe a subtitle or something. I think this has been reported and they may be trying to fix it.

As for the Logos 3 issue, ask that in the Logos 3 forum.

JimTowler

https://community.logos.com/discussion/comment/102040#Comment_102040

When you run a passage guide the commentaries listed are your prioritized commentaries unless you have not prioritized any. In that case they are the program defaults. Under the first few listed is a "more" link. Did you click that. If not that is likely where you will find the NIBC listed. If you want it higher then prioritize it in the library.

Kevin, Thanks for your prompt comments.

Yes, I had clicked "MORE" to see all my commentaries, rather than just the first 6 by default. However, NIBC does not appear.

I added the series with "Prioritize" as your suggested, and NIBC came up, but it was gone again when I deleted it back to before.

I would expect that "All Commentaries" would include them ALL!!!

I am running "Rebuild Index" in case there is something not right with that, but its going to be 3+ hours before that completes.

For now, I can use your "prioritize" solution, but it does not address the initial concern, and possible bug in version 4.0b.

Thanks.

Ron Barry

https://community.logos.com/discussion/comment/102059#Comment_102059

The Logos 3 issue - go to Tools-Options-General-Interface-uncheck "Use primary resource titles in My Library"

JimTowler

https://community.logos.com/discussion/comment/102088#Comment_102088

Ron,

Thanks - YES, that is the answer for Version 3. Sorry this sub-part is in the wrong forum.

Jim

JimTowler

https://community.logos.com/discussion/comment/102059#Comment_102059

Well, the version 4.0b "Rebuild Index" changed nothing:

My NIBC still does not show up under Passage Guide.

(Unless I set it to prioritize the NIBC Series)

So, the "All Commentaries" within Passage Guide DOES NOT give me ALL.

To me, that looks like a bug with 4.0b, or a fault with the metadata of the NIBC set.

Q: What else am I missing when I have "ALL" selected, but I dont get all?

Dave Hooton

https://community.logos.com/discussion/comment/102207#Comment_102207

Well, the version 4.0b "Rebuild Index" changed nothing:

We are (sadly but with some justification) getting to use Rebuild Index as a universal cure, but the need for that would have been a crash during indexing of those resources.

To me, that looks like a bug with 4.0b, or a fault with the metadata of the NIBC set.

Metadata - see http://community.logos.com/forums/p/13035/101404.aspx

Mark Barnes

https://community.logos.com/discussion/comment/102207#Comment_102207

My NIBC still does not show up under Passage Guide.

(Unless I set it to prioritize the NIBC Series)

Are you saying that the NIBC only shows up when it's prioritised in your library? If so, that's my experience too. I'm reporting it as a bug.

JimTowler

https://community.logos.com/discussion/comment/102469#Comment_102469

Mark,

YES - As you say, it ONLY shows up if prioritised.

Logos,

Please confirm that this BUG has been picked up and logged into your internal systems for attention in due course.

Thanks.

P.S. Can we have some simple way of reporting and tracking bugs we have reported?

Random feedback in the forums does not seem to work well.

Mark Barnes

https://community.logos.com/discussion/comment/112145#Comment_112145

I did report it as a bug, but it didn't get picked up by Logos. However, it does work for me now in 4.0c beta 1.

JimTowler

https://community.logos.com/discussion/comment/112191#Comment_112191

Thanks Mark, for reporting this, and providing feedback here.

I just retested this, and it now works.

I may well still want NIBC back on my priority list. Not sure yet. Still learning which of the many resouces I have give helpful answers, and which can be left alone unless I want to dig deeper or compair many views and version.

Again, thanks for the help on this one.

And of course, thanks to the Logos team that actually fixed something somewhere.

MJ. Smith

https://community.logos.com/discussion/comment/112191#Comment_112191

If you add the bug to the wiki, you'll see feedback from Logos.

Mark Barnes

https://community.logos.com/discussion/comment/112423#Comment_112423

If you add the bug to the wiki, you'll see feedback from Logos.

He did, but he didn't (if you see what I mean).

I think it this case it was a metadata problem, and therefore perhaps it wasn't classified as a bug.

JimTowler

https://community.logos.com/discussion/comment/112423#Comment_112423

If you add the bug to the wiki, you'll see feedback from Logos.

MJ,

I had already reported it there, but it continues to have no effect.

I seem little value or point in adding new items to that bugs list, as its know grown into a long "monster" that has no sort order, structure, or much clear sign of official Logos support.

To fix it, it needs a date field, for when an item is created, last updated, offical Logos bug id, and the build number that fixes it, or a date that a server or metadata update addressed it. And finally a closed status once its done, and moved to the archive page of the same list - so it stays managable.

I dont seem much point in the current list as it continues to get longer with few updates.

Mark Barnes

https://community.logos.com/discussion/comment/112497#Comment_112497

In fairness, Logos employees do update the bugs on the Wiki pretty often: http://wiki.logos.com/recent.aspx - but I agree, it could be better.

MJ. Smith

https://community.logos.com/discussion/comment/112460#Comment_112460

I think it this case it was a metadata problem, and therefore perhaps it wasn't classified as a bug.

You're correct - data corrections are not usually classified as bugs.

MJ. Smith

https://community.logos.com/discussion/comment/112497#Comment_112497

I seem little value or point in adding new items to that bugs list, as its know grown into a long "monster" that has no sort order, structure, or much clear sign of official Logos support.

To fix it, it needs a date field, for when an item is created, last updated, offical Logos bug id, and the build number that fixes it, or a date that a server or metadata update addressed it. And finally a closed status once its done, and moved to the archive page of the same list - so it stays managable.

It certainly is not as I would have designed it. But it does make it easier for me to know if a problem has already been reported. I had not been bothering to add to the wiki list until recently.

However, I think you overstate its problems. It can easily be sorted, it has the version of the correction and it has a fixed status. Yesterday Rosie found it did have a Logos id - I don't remember what dates it has and I've not paid attention to its update frequency. But we asked Logos for a bug list we could see and they set something up for us quickly. Whether or not it evolves depends to some extent on our use of it.