L/V 10 Tip of the Day #95 Documentation

MJ. Smith

Another tip of the day (TOTD) series for Logos/Verbum 10. They will be short and often drawn from forum posts. Feel free to ask questions and/or suggest forum posts you'd like to see included. Adding comments about the behavior on mobile and web apps would be appreciated by your fellow forumites. A search for "L/V 10 Tip of the Day site:community.logos.com" on Google should bring the tips up as should this Reading List within the application.

This tip is inspired by the forum post: Psalms Explorer Dataset - Logos Forums 

In the application menu, just under the open help option, is a browse all documentation item.

This is helpful but misleading. The option actually opens the library filtered by type:manual.

Unfortunately, not all documentation is included in manuals. For example, the Psalm Explorer interactive has the documentation embedded internally under the "about" function.

Values for many of the Faithlife tags are found under type:Glossary. Documentation for some of the Andersen-Forbes coding is found in their textbooks. Some books are sufficiently complicated to require their own "documentation" e.g.Wonneberger, Reinhard. Understanding BHS: A Manual for the Users of Biblia Hebraica Stuttgartensia. 2nd rev. ed. Vol. 8. Subsidia Biblica. Roma: Pontificio Istituto Biblico, 1990. With this broader understanding of documentation, I have manually tagged 243 resources as documentation. I tend to browse my collection rather than the more limited one brought up through the menu.

Dave Hooton

Unfortunately, not all documentation is included in manuals.

There has to be better consistency, and this includes the formatting and placement of the content e.g. some glossaries are a separate type:Glossary resource.