Incorrcet information on Factbook

I have picked up an extensive amount of incorrect information displaying under the Factbook feature. I have engaged with logos through their support function more than two weeks ago and subsequently no fixes were implemented (empty promises).

Currently, I am using google for searches as it is far more reliable using the Factbook service.

Below some examples of hundreds of errors that I have picked up:

When you search for Athlete, the following description is given: Christian churches predominantly in Eastern Europe and the Middle East.

Asleep: A formal admission or acceptance into an organization of group.

The list carries on an on.

Find more posts tagged with

Comments

Sean

When you search for Athlete, the following description is given: Christian churches predominantly in Eastern Europe and the Middle East.

Asleep: A formal admission or acceptance into an organization of group.

Those examples are bizarre. Factbook showed me the same information.

Lew Worthington

https://community.logos.com/discussion/comment/1321379#Comment_1321379

I do not get the same bizarre results. What platform are you on? I'm on the mobile app on Android.

diederick pütter

https://community.logos.com/discussion/comment/1321390#Comment_1321390

I get the incorrect info on my Windows Desktop.

Sean

https://community.logos.com/discussion/comment/1321395#Comment_1321395

I get the incorrect info on my Windows Desktop.

Me too. I also just checked Android and the web app for "Athlete" and got the same. Something is definitely wrong.

Lew Worthington

https://community.logos.com/discussion/comment/1321406#Comment_1321406

Ahh, I see what you're talking about. I customarily ignore that stuff on the top and I was just looking at articles FB referred to. Yes, I also get the weird results.

Bradley Grainger (Logos)

Thanks for reporting this; I've passed it along to our data team.

I've also passed on your feedback (about engaging with Logos support) to our head of Customer Success.

diederick pütter

https://community.logos.com/discussion/comment/1321432#Comment_1321432

Thank you, Bradley, for reporting the issue.

However, logos did not find the time to investigate the issue or apply any fixes.

Providing incorrect information to their users does not seem a priority.

MJ. Smith

https://community.logos.com/discussion/comment/1324104#Comment_1324104

However, logos did not find the time to investigate the issue or apply any fixes.

We don't know how much time they have spent diagnosing the problem nor do we know how time intensive the correction is. Give them a bit more time

diederick pütter

https://community.logos.com/discussion/comment/1324158#Comment_1324158

It is now going for two months since the initial support engagement.

MJ. Smith

https://community.logos.com/discussion/comment/1324161#Comment_1324161

It is now going for two months since the initial support engagement.

I was going by this thread - which is a bit less than 2 weeks.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1324166#Comment_1324166

This data issue is actively being worked on. I hope we will be able to deliver an update soon.

diederick pütter

https://community.logos.com/discussion/comment/1324242#Comment_1324242

Bradley, the only thing logos is doing, is actively ignoring the issue.

Kyle G. Anderson

https://community.logos.com/discussion/comment/1324270#Comment_1324270

Data updates are pushed out every other Tuesday. This update will be pushed out on Tuesday, November 5.

Aaron Hamilton

https://community.logos.com/discussion/comment/1324270#Comment_1324270

Bradley, the only thing logos is doing, is actively ignoring the issue.

So, a high level employee thanks you for reporting the issue and tells you it's actively being worked on. In response, you contradict this employee and provide an entirely unfounded and ignorant accusation. The level of disrespect people feel comfortable showing on the internet is even worse than when they are behind the wheel.

diederick pütter

https://community.logos.com/discussion/comment/1324359#Comment_1324359

Hi Aaron, I appreciate your concern, but as previously stated, it is now almost two months since this issue has been raised with logos. Not sure how to identify a high-level employee? However, the issue remains.

Aaron Hamilton

https://community.logos.com/discussion/comment/1324364#Comment_1324364

Hi Aaron, I appreciate your concern, but as previously stated, it is now almost two months since this issue has been raised with logos. Not sure how to identify a high-level employee? However, the issue remains.

I'm sure it may be difficult for us to understand from the perspective of a user, but I have no doubt that Logos has their schedule full regarding things to work on. The last issue I raised didn't even receive a reply, even though it relates to a bug that has been around for a very long time. I don't fault anyone for this; it would be egocentric to assume that my priorities are everyone else's priorities. Consider yourself lucky that the issue you raised was addressed (and presumably solved - you'll have to verify that next Wednesday) in a timely manner.

MJ. Smith

https://community.logos.com/discussion/comment/1324364#Comment_1324364

t is now almost two months since this issue has been raised

Two months in which you know that a significant portion of the workforce was focused on releasing the new subscriptions and libraries i.e. a very, very busy time for them. Logos is a small company but requiring knowledge and skills that a temp worker off the street cannot provide additional workforce in crunch times.

DAL

https://community.logos.com/discussion/comment/1324364#Comment_1324364

Hi Aaron, I appreciate your concern, but as previously stated, it is now almost two months since this issue has been raised with logos. Not sure how to identify a high-level employee? However, the issue remains.

It has never been a click, report and people automatically drop what they’re doing to fix something just because you reported it. So a little patience goes a long way and it’s part of the fruit of the Spirit. Fixing things in a program so huge as Logos requires time and effort.

DAL

diederick pütter

https://community.logos.com/discussion/comment/1324367#Comment_1324367

This might be true, but when you are providing incorrect data on your platform, I would assume that this should be a priority to investigate. This affects the integrity of the data that logos provide. It is not a developer function per say, but a different team that should ensure that the content is relevant and correct.

MJ. Smith

https://community.logos.com/discussion/comment/1324370#Comment_1324370

It is not a developer function per say, but a different team that should ensure that the content is relevant and correct.

The Content team is, in fact, separate from the application team. The Content team is led by a Logos employee who for years has shown himself to be responsive to error reports and has actively involved himself in the forum community. That is why historically there are many threads titled ATTN: KYLE. You may have uncovered the underlying issue - those of us who have been on the forums for many years know that occasionally something slips through the cracks but if Kyle is on it, it will get fixed as soon as the schedule and staffing level permits.

Aaron Hamilton

https://community.logos.com/discussion/comment/1324370#Comment_1324370

when you are providing incorrect data on your platform, I would assume that this should be a priority to investigate. This affects the integrity of the data that logos provide. It is not a developer function per say, but a different team that should ensure that the content is relevant and correct.

I assume this is one reason why Logos chooses to engage with the user forums as much as they do. Feedback like what you provided goes a long way in helping Logos deliver a superior product.

diederick pütter

https://community.logos.com/discussion/comment/1324373#Comment_1324373

I am glad that someone will address the issue.

Kyle G. Anderson

https://community.logos.com/discussion/comment/1324327#Comment_1324327

Data updates are pushed out every other Tuesday. This update will be pushed out on Tuesday, November 5.

I hope this piece of information didn't get missed.

My team found out about the issue on October 22. We had a fix ready to go within the week and now the update is scheduled to go out at the earliest possible window: November 5.

diederick pütter

https://community.logos.com/discussion/comment/1324370#Comment_1324370

Thank you for addressing the issue. Everything seems to be in order.

diederick pütter

https://community.logos.com/discussion/comment/1325209#Comment_1325209

There might still be an issue with the content.

Jan Krohn

https://community.logos.com/discussion/comment/1326969#Comment_1326969

There might still be an issue with the content.

Indeed, especially in the German (and probably other non English) versions.

In English, "division" in the sense of a military unit, and in the sense of separating, is the same word. In German, those are two entirely different words, but they share the same factbook page.