Chamilo LCMS Connect » Core » Repository

Would be good to have a list of which applications currently support roles and rights, and a help (maybe a page on the wiki) about how to actually implement roles and rights in an application, and possibly define new roles and rights.

What about a basic rights system for learning objects in the repository, such as:
*all objects are searchable (standard)
*viewable (by all or one or more specific users or groups of users)
*shareable (with all or one or more specific users or groups of users; the object remains the same)
*reusable (idem, new instance of the object)

This is very important to make it possible for people to work together and to stimulate them to do so.

As far as I know Sven already implemented this ...

Looks nice, the only question I have is why all objects owned by X show X to have no rights.
Also the logical order is search/view/use/reuse. It should be possible to set the standard search right on for all objects.

Next big part in roles and rights:
introduce subtrees so that the performance in the roles and rights will receive a boost

Changed to subtrees in
http://code.google.com/p/chamilo/source/detail?r=60dab61d20a326e397997ab0e7d00b85abfb71b2&repo=chamilo
http://code.google.com/p/chamilo/source/detail?r=78f2b1d9c10166960acd2e36d4ff52d01b772cd8&repo=chamilo
http://code.google.com/p/chamilo/source/detail?r=2d58a05caa50f3cc244a9581441047b7f8e66361&repo=chamilo
http://code.google.com/p/chamilo/source/detail?r=60fbf0854505301a8179f05984053a07bc31c7f1&repo=chamilo
http://code.google.com/p/chamilo/source/detail?r=6b9844b982e52e7c1549c120621d19eada546a7e&repo=chamilo

CDA / Reservation tool rights need to be redefined
Still some bugs with defining rights in repository

Fixed the rights in the repository in
http://code.google.com/p/chamilo/source/detail?r=b0bf699f63e25b1da185fb3afa1bb801cc3379f0&repo=chamilo