ATTN: Some resources may be locked temporarily

I agree with you Joe, the cloud is nice, but unless there is sufficient redundnacy in place to ensure that this does not happen then it should not be used. Working on computers the last 20 years, it WILL happen so this give one concerns about it.

The concept is good, but it should be setup in such a way that the Logos application should fall back to a local copy of the license as it was last sync'd with the license server. This is a way that would hopefully prevent resources from being locked even if there was an issue on the server (cloud).

Any thoughts?

The concept is good, but it should be setup in such a way that the Logos application should fall back to a local copy of the license as it was last sync'd with the license server. This is a way that would hopefully prevent resources from being locked even if there was an issue on the server (cloud).

I agree. There needs to be some local override system. I lost close to 1/3 of my 1400 resources. I needed to use them.... glad I have LDLS 3 to fall back on

Guess that is why we call it beta testing. But this needs to be figured out before going live.

Jim

Simlar question raised here and other places that I can't recall off-hand..... I am sure the publishers like licenses being totally out of our control and that might open up opportunities for more publishers coming on board... but I am a customer and I want to have control of my license files for the reasons outlined here.

At this point, I'm apprehensive of the cloud.  If my books can be "lost" for whatever reason than I think the benefit is of less value than its cost and it is not in my best interest as a consumer.  I realize this present problem is beta glitch but it highlights a serious consumer issue in that the publisher has all the control over the books even after full payment has been made.  Who would pay $100 for a paper reference if the publisher held the right to take back the book whenever they wanted. I understand that publishers want to control their books etc., but there must be a balance between their rights as publisher and my rights as a consumer.

If the cloud is going to control our resource updating (which I think on its own is a great idea), it should never delete files from the resource directory (forcing a re-download when things get corrected) and there needs to be a way to override the cloud with a local copy of our licenses.

I had an update come up that I ran this afternoon, apparently in response to the problem we were having with some resources being locked.  After running the install, I did have resources show back up, but I am not certain all of them are actually available.  Like many of you, my library is very extensive on Libronix and I would like to know if I still have all the books I have paid for over the years.

The license server has now been fixed.

From what I can tell on this end, this bug only affected users who changed their licenses in the last few days (e.g., purchased a new resource on logos.com, activated a new prepub, etc.) However, to make sure everyone is fixed, we have instructed the license server to send everyone a full copy of their licenses; this means that the new time you sign in, the program will assume that your licenses have changed and will rescan your LDLS3 discovery paths for newly-unlocked resources. The "Preparing your library" screen will appear during this phase, while the program scans your hard drive. If new resources are found, your library will be re-indexed. If the "Preparing" phase concludes that everything is the same as before, no indexing will occur.

The bug was a result of inadequate testing of the server code; we will add more tests to prevent another regression error of this sort. (Also, this is a beta test, so everything is not tested as thoroughly as it would be in a production environment.)

Regarding “resources that have a perpetual licence”, many customers have asked (for many years) to be able to legally transfer resources to other users. Supporting the removal of licenses is a built-in feature of Logos 4 for this purpose. (See also http://www.logos.com/support/lbs/faq#transferlicenses.) Allowing users to easily override the official record of their licenses with a local copy would allow unscrupulous users to greatly abuse the system. (We do have a non-insignificant amount of piracy, which pushes up the cost for you: the ethical, legitimate users.)

Regarding revoking licenses due to publisher demands, please see this thread: http://community.logos.com/forums/t/1734.aspx

Thank you, Bradley!   Peace and Joy to you!         *smile*

        You come through loud and clear!  Indeed!  I truly appreciate all the hard work you are doing for us, and many of you I am sure are physically very tired.  I know some of our concerns are your concerns also.  What I want to communicate in this "post" is that I, for one, do trust Logos.  A number of very clear statements have been made by Bob and you and others at Logos.  Thank you for them.

Yours in Christ,

          ......    Mel

Bradley,

I am glad that the problem has been fixed and that steps are being taken to ensure it cannot happen again. Not so happy about reindexing again - 3rd time this week - but I understand that these things can happen in Beta testing.

At the very least I can check out the indexing logs - they make for fascinating reading - hope that indexing of LSJ can be improved (but it is a whopper of a file).

While this problem had been reportedly informally on the forums,

How exactly do we "formally" report such a problem? I would have thought that describing what happened, including screen shots, on these forums would be described as formal reporting of the problem. Is there another mechanism which we should use in cases such as this?

I have to be honest, as much as I do like a lot of what V4 seems to offer or will offer, things like this disturb me. I do not look forward to the indexing fiasco whenever there is an update or a new purchase as it is, but now there could be potential for something like this to happen again and with a slight possibility of indexing being necessary due to it...

I'm really not liking the thought of this "cloud"/"big brother" deal. I would much rather have full control over library management, license back-up, etc. It's a shame that those that can function with these "power user" tools will not have that option due to those that can't handle it. I understand the cost savings, but if the cost savings costs the customers valuable time and energy - this could be a severe negative overall.

I really hope that something can be done to alleviate this deal, as of today if all does stay the same, unless there is significant upgrades to the base packages, something Bob alluded to, but did not get into specifics I may stay a V3 user....

I know as beta testers we are getting these free upgrades, which I appreciate, but I hope for what the estimated cost of upgrade that was mentioned there are some very good additions of resources, otherwise as of B3 for this user the negatives outweigh the positives...

Sorry, that was a confusing choice of words

As we say Down Under: No worries. 

This activation file can function as a license backup (that restores all the licenses that were on the account when it was created).

That sounds like good news considering the two treads running at the moment discussing the risks of loosing data in many ways.

I have always kept a backup of my licences and I look forward to having one for L4.

When will the e-mailed file be available?

I'm a bit confused by the term "non-insignificant" which sounds straight from Washington, D.C.

And I'm surprised (a little) that people monkey around with Bible licenses. On the other hand, the local Lifeway store reports that the theft of Bibles is a big problem.