While a "presentation behaviour", i.e. not checked-out document is remotely opened, then checked-out in LO and after editing checked-in or cancelled works OK, in many other cases works incorrect.
e.g.
Open already checked-out document (user has no flag, that the document is locked), doc. is opened in read-only mode (problematic - better is open working copy and best is inform user about checked-out status and enable him to switch to working copy) but user is offered to switch into editing mode, what is incorrect. The document (locked, i.e. read-only on server) is then opened remotely (no local copy - but even if it would be a local copy, user should be informed) in editing mode, so user is able to make changes and save button is enabled but ignored. In menu save option is disabled but Check-in option is enabled, but using it leads to error. "Cancel Checkout" is enabled as well but using it leads to error message followed by confirmation message and after confirmation the document is again switched to read-only mode but without any checked-out cancellation  was done. 
A specific case is crash recovery, which could lead to quite strange (from user point of view) behaviour.
With thinking out about the user-logic, please take into account, that it is absolutely not necessary, that working copy is in the same folder and/or the current user has access rights to edit or even read the working copy.
That is why I think, the logic should be revised. With Alfresco logic, testing and user logic I can help, with LO programming not.