Bug: Incomplete Metadata after re-installing

I re-installed 4.2b SR-1 on Desktop via Method 3 (actually used Logos4.msi to install) and soon began to notice discrepancies with the metadata.

Type Desktop Laptop

type:commentary 308 301

type:Notes 10 12

type:encyclopedia 11 32

type:lexicon 7 25

type:dictionary 42 3

This metadata does not reflect the re-classification of type:dictionary.

Example resources with Type:

Title Desktop Laptop

Apologetics Study Bible Commentary Notes

Believer's Study Bible Commentary Notes

You Can understand the Bible Seminar Commentary Monograph

Treasury of Scripture Knowledge Notes Cross-reference

Titles with Series metadata (no resources are missing):

Series Desktop Laptop

Bible Lessons Int 13 17

Opening Up 8 32

I also note the following:-

After uninstalling the Documents and Users folders were preserved whilst the Data folder was wiped
I did not have to sign-in after installing; but
My Collections were not restored (this old bug needs to be fixed)

I used the usual manual procedure to restore the Collections, but the logos4.log indicates it is only looking for metadata updates after 16 June 2011.

Find more posts tagged with

Comments

Dave Hooton

Well I did the standard thing and deleted the metadata.db, which has fixed everything above except for type:commentary = 302 vs. 301. The extra resource is Sermon Outlines on the Book of Proverbs (LLS:36.0.64) which should be monograph along with other resources in the Sermon Outlines series.

How to correct that (there may be other differences that I have not explored)?

EDIT: Is it possible to re-issue the metadata update for that resource?

Dave Hooton

https://community.logos.com/discussion/comment/262061#Comment_262061

bump

Melissa Snyder

https://community.logos.com/discussion/comment/262666#Comment_262666

Checking on this...

Dave Hooton

https://community.logos.com/discussion/comment/262804#Comment_262804

The delay is frustrating, but not just on my part. See this issue.

Dave Hooton

https://community.logos.com/discussion/comment/265017#Comment_265017

bump!

Dave Hooton

https://community.logos.com/discussion/comment/270978#Comment_270978

It would help me if Logos could confirm that Sermon Outlines on the Book of Proverbs
(LLS:36.0.64) should be a monograph and offer some explanation why its metadata has not been updated.

Melissa Snyder

https://community.logos.com/discussion/comment/271033#Comment_271033

It would help me if Logos could confirm that Sermon Outlines on the Book of Proverbs (LLS:36.0.64) should be a monograph and offer some explanation why its metadata has not been updated.

It should be a monograph. I'm not sure why the metadata has not been updated on your system. I don't yet have answers to the metadata update issue, but will try again.

Dave Hooton

https://community.logos.com/discussion/comment/271301#Comment_271301

I don't yet have answers to the metadata update issue, but will try again.

Thanks for your efforts, Melissa.

Dave Hooton

https://community.logos.com/discussion/comment/271301#Comment_271301

It should be a monograph. I'm not sure why the metadata has not been updated on your system. I don't yet have answers to the metadata update issue, but will try again.

What a pleasant surprise. I hadn't logged into this desktop system for a while but it started with a massive Resource Discovery followed by a metadata update that included LLS:36.0.64. Consequently, my issue is resolved.

Could you let me know what triggered these events?

Many thanks,

Melissa Snyder

https://community.logos.com/discussion/comment/272245#Comment_272245

It should be a monograph. I'm not sure why the metadata has not been updated on your system. I don't yet have answers to the metadata update issue, but will try again.

What a pleasant surprise. I hadn't logged into this desktop system for a while but it started with a massive Resource Discovery followed by a metadata update that included LLS:36.0.64. Consequently, my issue is resolved.

Could you let me know what triggered these events?

Many thanks,

Typically, a long resource discovery indicates that the program is scanning a disc or a drive, possibly prompted by the scan command or by an uninstall/reinstall where the Resources folder was saved prior to uninstall and moved back to the Logos4 folder after reinstall.

Dave Hooton

https://community.logos.com/discussion/comment/272461#Comment_272461

Typically, a long resource discovery indicates that the program is scanning a disc or a drive, possibly prompted by the scan command or by an uninstall/reinstall where the Resources folder was saved prior to uninstall and moved back to the Logos4 folder after reinstall.

I don't think that applies. Perhaps the logs may help

2148.Logos4_Discovery.zip

Melissa Snyder

https://community.logos.com/discussion/comment/272509#Comment_272509

We'll review the logs. Thanks.

Bradley Grainger (Logos)

Metadata should be (re)downloaded for recently-unlocked resources in the release following 4.5b RC 1.

Dave Hooton

https://community.logos.com/discussion/comment/361822#Comment_361822

Metadata should be (re)downloaded for recently-unlocked resources in the release following 4.5b RC 1

I'm puzzled how that resolves my issue as the resources affected were not "recently unlocked", and what does that term really mean?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/361959#Comment_361959

Metadata should be (re)downloaded for recently-unlocked resources in the release following 4.5b RC 1

I'm puzzled how that resolves my issue as the resources affected were not "recently unlocked", and what does that term really mean?

I should have written "recently discovered" (which is actually what is implemented, and also what should solve the issue).

Dave Hooton

https://community.logos.com/discussion/comment/362023#Comment_362023

I should have written "recently discovered" (which is actually what is implemented, and also what should solve the issue).

Yes, but it sounds like a one-off "Discovery". The resolution for this first instance was protracted but the second occurrence was resolved in a matter of days. Both resolutions were initiated by a large "Discovery" process.