Checkout module support the following use cases at this time and each has its own problems.

Case 1: Users are allowed to check-in documents locked by other users.
Issue: There will be conflicts (complains :-) if a user checks in the node that is being edited by someone else.

Case 2: User are not permitted to check-in documents locked by other users. Automatic check-in is used for unlocking the documents that are left being locked.
Issue: The documents cannot be edited in case Automatic check-in doesn't work well, for example, something wrong with cron.

The above issues can be resolved perfectly if we add such an option:
* User (by role) can check in only on the locks expire - they are aged older than the Automatic check-in interval but haven't been unlocked yet.

By using this feature along with cron based Automatic check-in, we can avoid both conflict and delay.

Joel, can you consider adding this to your development plan?

Comments

Anonymous’s picture

Anonymous (not verified) commented

Thumbs up for this, very important in my opinion. Today one of my users tried to edit his content, clicks "save" and then oops, content locked by other user. Not very smart.