Anahide Tchertchian wrote: > Hi again, > > Joachim Schmitz a écrit : > >>> Ok so other data need to be editable by other users (student >>> administrator perhaps? >> >> >> sure, but it also must not be even viewable by other students > > > So you'll just have to ensure that only this student has the > WorkspaceMember role on his document, and not the other students. > Are there any other actors you can define for your workflow? > Yes at least the studentmanager, whom would be assigned the sectionmanager role I assume.
>>> Yes, we use CPS and its workflows for purposes like this one very often. >> >> >> Are there examples, where I could take a look at ? > > > I dont understand why the publication process bothers you so much : if > you ignore transitions related to publication in default workflows, it > seems to me that you have your example. > >>> I would advise (if you chose workspaces as the main container) to make a >>> mapping between different users and roles available in workspaces. Let's >>> say student administrators will be defined by the fact that they have >>> the WorkspaceManager role, and students will be defined by the >>> WorkspaceMember role. >>> >>> Then you'll define your workflow using these roles taking care of your >>> conditions. >> >> >> >> Ok I chose a section as the main, container in our prototype. How would >> I achieve that a student only see's his/her data, can I (ab)use the >> owner-attribute for that ? >> Or the question asked CPSWorkflow specific. What is the role of the >> student I put on the workflow-stack or do I put the student-memberid on >> the workflowstack, if only he is allowed to do something at this stage. > > > I'm confused : I dont see why you need workflow stacks here, maybe I > missed something in your requirements? > You'll have to set a local role to the student when its (folderish) > document is created : I suggest you use the basic section roles, e.g > SectionManager, SectionMember (I dont think you need another role like > SectionReader here). > You can of course use the Owner role in your workflow instead of the > SectionMember role: I did not understand that the student created his > own document. > I am not sure either, perhaps I missunderstand something. At the moment we have a little bit simplified the following: - there is a students-folder for all students. - a studentmanager creates the folderish studentrecord in this studentsfolder, and creates a new member with a password set. By doing so, the student is admitted to the university. - the student logs in (with a special procedure), and changes his password. - he than can create for example a semester-folder and subscribe to courses and lectures, a copy of each course is put in his semester-folder. - the course-manager and only him can enter examination results, which this student should be able to view. In the prototype all student-records a viewable by all students. If I understand it correctly I have to assign the following local roles: in the studentsfolder sectionmanager to the studentmanager in the studentrecord sectionmember to the specific student >> By the way, do you use any tools for describing and visulisation of >> workflows ? > > > You can use the last release of the DCWorkflowGraph product to get a > graphical representation of your worklfow (a 'graph' tab will be added > in the ZMI): > http://www.zope.org/Members/panjunyong/DCWorkflowGraph thanks looks interesting. -- Mit freundlichen Grüßen Joachim Schmitz ...................................................................... AixtraWare eK ..Joachim Schmitz ..www.aixtraware.de ..t: +49-2464-8851 Hüsgenstr. 33a .....d-52457 Aldenhoven .............f: +49-2464-905163 _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
