Integration of Book Manager with Coherent Access

Interesting idea. I need to think about some implications of generalizing this.

The general case would be "if a user can edit a book then they should be treated as the author." I'll investigate this as a behavioral option via config.

I'm also very interested in handling permissions the described way!

I'm interested in a variation of this -- I am using Organic Groups and want to allow anyone in the same group to edit the book. I think this could be done by creating a hook of some kind in the access function that would allow another module to allow access even if it isn't the book's author.

Looks like this hasn't gone anywhere in a very long time. Most things in this module fit my needs pretty well if I can figure out a way to let other group members get access to the book.

We are trying to implementing this functionality at my workplace.

One possible strategy is to have a sort of hook_coherent_access_update() inside coherent_access_nodeapi(), so that other modules can implement hooks that get fired when updating/inserting/deleting a node.

I'm thinking the permissions can only be assigned on the "root" node of a book, and all children in the book would inherit those permissions. Also, a single email would have to go out, ideally with different subject/body to inform users have the option to edit/view any node under the book.

coherent access is no longer maintained