I have a Window's based program that i built which generates reports on your Logos Library. It is useful to see what has changed between updates in your Logos Library. As you in the future get new updates, you can run the program to generate reports which show you the differences. [if you happen to have backed-up your Logos files, then you might even be able to find your old catalog files and run a report on them]
i have been working on a webpage in the hope of sharing my program with those of you on the forum. But it has turned into a much larger project than i expected. So i have decided to place this post to see how many of you are interested in this program before i put any more time into finishing the webpage (which will provide the installation program as well as detailed info on how to use the program). So if you are interested in using this program, then post a Thumb's-Up Reply to this post. i have the user's manual part of the webpage built, but still have to detail all the Reports, build the page for installation, and a few other webpage to help.
Click on a report image below to view the actual report
Reports on differences between my 2013 Library and my 2014 Library (pulled old copy of my Library from a Backup). This is where the program REALLY becomes useful !
(used really old backup from 2010 so these report would be populated)
Reports on a Single Library Catalog
QLinks, Bibl2, LLR, MacrosDell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1
Cool stuff! The metadata hounds should love this. Be great to run when logos releases unidentified updates to see some of what's changed in those updates.
Forum Theme ◆ Enhanced Forum Search ◆ VotD for Rainmeter
Resource type changes are very useful to me. A report on Mytags and (My)Ratings differences would also be useful.
Dave===
Windows & Android
Steve, I am entirely in favor of you expending your time and effort on my behalf! Good on ya, mate!
"I read dead people..."
Martin Grainger Dean:Interesting! But all the data from "Logos version" are false (all books in your library)?
Hi Martin,
That is true, in the LogosVer report, there is a footnote at the bottom of the report as shown below:
============================================
Logos book Version number as found in your Catalog does NOT reflect the actual version number for your book stored on your computer. (this seems to be updated in the Catalog file when opening Logos, to reflect what is currently available on the Logos site). The actual book's Version number seems to be locked away inside the book's data file and when viewing a book's info in the Logos program, it retrieves the version number from the actual book file.
In my case, i don't have Logos set to Auto Update (for personal reasons). And i have noticed the discrepancy, but decided to leave the report as it is (thus why i added the footnote at the bottom). If you viewed the Full Report, then i just turned on a flag which included much of the info that is stored in the catalog file (thus the LogosVer showing up under each title. In the program the user just checks what extra info that they want added under each title. So it would be very easy to exclude the Logos Ver info in the reports.)
Since i am not a Logos employee, i have no inside information as to why the Logos version for each title is not representing the actual Logos version for each title.
Dave Hooton:A report on Mytags and (My)Ratings differences would also be useful.
In the current version of the program, these fields are not saved into the program's database. Also there are not current reports for these fields. Doesn't mean that i could not improve the program to add these fields.
Are we speaking about the same fields in the Catalog.db file?
User Tags ?
User Ratings ?
Yes, please. Thanks
The Added/Missing report and the PBB's report would be good to try out at this time. I created a PB, deleted it, and it still shows in my library. Maybe one of your reports will uncover something.
steve clark: Logos book Version number as found in your Catalog does NOT reflect the actual version number for your book stored on your computer. (this seems to be updated in the Catalog file when opening Logos, to reflect what is currently available on the Logos site). The actual book's Version number seems to be locked away inside the book's data file and when viewing a book's info in the Logos program, it retrieves the version number from the actual book file.
Martin Grainger Dean:so if the book's version is not stored (at all) on our computer,
My program uses only 1 of the many databases which are part of the Logos Bible Software program. i am only making a copy of the catalog.db file and my program reads the copy of this database.
EDIT: i am guessing that the actual book version is stored inside the actual book file itself.
Martin Grainger Dean:from where is taken in your report since you have "set the auto update to off"?
As mentioned above, i am making a copy of Logos' catalog.db. It is from this database that the program glean info to generate the reports.
My mentioning that i have "auto update turned off" was to help you understand that my catalog.db may/is not fully up-to-date. i periodically will allow Logos to update my Library and it is at this time that my catalog file is fully updated. i have noticed that even though i don't permit an update, the catalog file is updated after opening the program (Logos), this doesn't occur every time i open Logos but i do notice it happening periodically.
The reason for my controlling the "Auto Update" process is so that i can control when Logos wants to run the Indexer.
Martin Grainger Dean:maybe "Logos version" should be "Last updated"? Can you check this hypothesis?
Guessing at a resource's Version number is not going to happen in the program that i have built (Logos Library Reporter).
By using the Com-API interface i could positively get a resource's Version number. But in other programs that i have written to work with Logos, i have found that there are inconsistencies with the Com-API interface working on several user's computers. Plus this interface runs pretty slow. This would slow down the reporter program as it interrogated Logos for each title in your library. So i will not be adding the Com-API interface to the Logos Library Reporter program. After contacting Logos in the past, they have better things to attend to than tracking down why the Com-API interface is inconsistent.
Sorry....
Is having each title's Version number that critical in a report?
Martin Grainger Dean:Depends. But most important I guess we have to have true data in a tool (?). Or maybe you can skip this step at all...
Perhaps viewing the webpage that i am working on would give you a better idea how the program functions. Please keep in mind that it is incomplete at this time (the reason for this thread). And yes, before releasing it to the public, i might disable the Version attribute/report (viewing the screenshot, you probably can guess how i would do that).
Regards, SteveF
It definitely would be a great tool.
Rog {BlueBird}
steve clark: Are we speaking about the same fields in the Catalog.db file? User Tags ? User Ratings ?
Yes.
UserTags, UserRating,
Dave,
Dave Hooton:UserTags, UserRating,
i have added the Rating & Tagging reports to the program (see short example reports below)
Click on images below to view the Reports
steve clark: Dave, Dave Hooton:UserTags, UserRating, i have added the Rating & Tagging reports to the program (see short example reports below)
Thank you. The report with more details is the best.