<blockquote>Is there any project documentation page where we can timely learn about
what specific features you are planning for special needs of your own
institution that might be more difficult or less useless to adopt for others,
</blockquote>
1. the package will be released by the end of next week and will be documented, right now we dont have something formally written yet.
2. we are tight to the standard, that means that if you have a DTD that is compliant, should work, anyway, I would say that is not difficult to do minor changes on the code in the case you need further customization (in other words, the package isn't written specifically for Galileo)
<blockquote>vs.
what will enhance the common use group administration, and how it fits with
the IMS Enterprise usage that is already present in OpenACS 5.0 (External) Autentication?
</blockquote>
The IMS Enterprise v.1.1 spec is divided in 3 parts, <person>, <group>, <membership>.
Right now auth has only <person> which is the import of users from the DTD to .LRN, now we have added:
* <group> which creates automatically from the DTD the departments, subjects, and class instances
* <membership> which creates automatically from the DTD the *relation* between users and a given class instances, and the specific roles (professors, TA's, students, etc) for that class.
Its more clear now?
