Changes between Version 4 and Version 5 of CaTissue

Timestamp:

10/26/10 13:51:15 (14 years ago)

Author:

Nick Holden

Comment:

--

CaTissue

@@ -11 +11 @@
    * what would it take to be able to process more than one participant at a time through the collection protocol? Currently the submission process includes checking for empty data in form elements which presumably have the same ID in each open tab or window, thus throwing an error.
 
-= = = 
+ = = = 
 
 A note on user privileges in caTissue from Jeff. It is not our favoured model of privileges, but probably defined in the caBIG CSM (Common Security Model). We'd like more fine-grain privileges, but in the meantime this is how it works:
@@ -19 +19 @@
 "I (naively) thought that setting up privileges for each individual user would suffice. Seems reasonable. Then the penny dropped. What if I were doing admin on the protocol and wanted to stop people using it whilst changes were underway? If I were relying upon individual user privileges alone, I would have to go into each user and change their privilege, then do the protocol admin, then go back into each user again to re-enable their use. Very tedious. The way it is set up in caTissue, I can disable / enable wholesale privileges for one protocol with one admin action. Quite clever?"
 
-= = = 
+ = = = 
+
+Storage location structure:
+
+
+BRICCS Collection Protocol:
+