One of the unfortunate side effects of posting the TIP of the day series, is that I am brought face-to-face with those features I unconsciously avoid because of issues with the implementation and/or data and/or documentation.
One such case that is always high in my mind, is my dropping the use of the Bible Browser when they quit updating it for new labels. Or my decreased use of label data when they dropped the corresponding interactives that allow me to see and analyze the data in a glance. No table removed the analytic value of the data and reduced it to a lookup with characteristic that rarely met my needs.
Specific to the newly started TIP of the day series ... the Event datatype having to match capitalization and apostrophe hex-code to match for a search or visual filter. Mismatches in the events in the Biblical Event Navigator and the actual tagging in the Bible (I thought the LCV was intended to prevent this). The lack of the lookup link to Andersen-Forbes semantic domains . . .
Others have mentioned the documentation, which is out of date, especially re: the format of the search argument.
Logos gives their usual "we know but it isn't high priority" which at times makes sense but during a period where they are trying to simplify the application, the inconsistencies are a significant barrier to learning Logos -- consistency and accuracy should be high priority.
Okay, I'll get off my high horse and ask you, plead with you, to give examples of where incomplete data, erroneous data, incomplete implementation, and/or defective documentation keeps you from using Logos features. What Logos sees is statistics that we don't use a feature, not that I would use the feature if it actually worked as documented.
