Reading Plans Duplicating Themselves

I'm not sure why or how (perhaps related to using the reading plan one day on one computer, not closing it, and then using it the next on the other computer), but I have had reading plans duplicate themselves a number of times...so there is definitely something up. I will try to pay attention in the future to the exact circumstances under which this happens; nevertheless, I know it has happened to me at least a few times.

Find more posts tagged with

Performance

Comments

Scott Fleischman

Duplication of documents (including reading plans) can happen with synchronization. One common scenario is when you have a document on two different computers. If you modify it on one computer offline, and also modify it on another computer offline, then when both computers go online and sync, there will be two versions of the same document. Both versions will show up on both computers. The best thing to do is to look at both copies, make the changes you want to keep to one document, and delete the other document.

The reason for the duplication is so that none of the changes you made are lost. When you make changes to the same document on different computers before they are able to synchronize, the sychronization code doesn't know whether: A) the change on the first computer is the "correct" change, the change on the second computer is the "correct" change, or C) both changes should be kept. So to be safe, it keeps both documents and lets you decide what to do.

But if you don't think this is what is happening in your case, then feel free to indicate the steps that causes the duplicates and we'll look into it.

Note: keeping the reading plan open shouldn't make a difference - it should be saving it and syncing it, if you are online.

Scott

Jacob Hantla

https://community.logos.com/discussion/comment/19968#Comment_19968

That is probably what happened.

Although we certainly don't want to lose data due to syncing, don't you think that duplicating documents isn't a good final answer to this? With most sync programs, when there is a conflict like this (simultaneous changes) it gives the user some kind of power of the results. I think it would be good to have a popup ask us what we want to have happen:

Duplicate files
OR
Merge
OR
Adopt the changes from one computer, discarding those from another.

There could be a checkmark or something saying "Don't ask me again" for those who don't want to mess with this kind of thing and trust the computer to guess right. I'm assuming the computer won't guess right, and creating duplicate documents only creates confusion for the user that the user will have to unsort (but the non-techie user).

So in summary, please change this behavior.

Simon’s Brother

https://community.logos.com/discussion/comment/20062#Comment_20062

That is probably what happened.

Although we certainly don't want to lose data due to syncing, don't you think that duplicating documents isn't a good final answer to this? With most sync programs, when there is a conflict like this (simultaneous changes) it gives the user some kind of power of the results. I think it would be good to have a popup ask us what we want to have happen:

Duplicate files
OR

Merge
OR

Adopt the changes from one computer, discarding those from another.

There could be a checkmark or something saying "Don't ask me again" for those who don't want to mess with this kind of thing and trust the computer to guess right. I'm assuming the computer won't guess right, and creating duplicate documents only creates confusion for the user that the user will have to unsort (but the non-techie user).

So in summary, please change this behavior.

Agree. Ideally I would like to be able to set on a per file type basis, say for reading plans I simply want to keep the most recent version.. but for say notes I might want to keep the separate documents and review the differences myself. Given Logos approach though I don't think control will get that granular but it would be my ideal result. Some choice would be better than none, even it it has to be set at the application level.