Difference between revisions of "Registry Software:User Groups"

(New page: [21 Dec 2008 - Randy] It is obvious that a user is a member of a group. In fact, they must be approved by a group leader in order to activate their account. A field in the 'user' and 'pa...)
 
 
Line 8: Line 8:
 
However, a user may be a member of more than one group. The list of groups a user belongs to is derived from
 
However, a user may be a member of more than one group. The list of groups a user belongs to is derived from
 
the table ung_db.membership limited by user_id. This is represented a the group_u_list entry in the bbdb.parts table.
 
the table ung_db.membership limited by user_id. This is represented a the group_u_list entry in the bbdb.parts table.
 +
 +
Some sections of the register allow the user to specify which of its groups should apply to the action.
 +
 +
If User->group is to be used, then the default should be the most recent group the user has joined, or the group
 +
selected as the default by the user.
  
 
Usage:
 
Usage:
  
−
* ->group and group_id are used widely throughout the Registry software.
+
* Part.pm - It does not seem that owning_group_id or Part->group are used by anyone except the DAS system
 +
 
 +
 
 +
* DNA Submission System (cgi/dna_transfer and cgi/lib/DNASubmissionBatch.pm)
 +
 
 +
 
  
−
* The DNA submission system and the measurement systems allow the user to specify the group name they
 
−
wish to associate with the submission from a pull-down list of their groups. (It uses the user->group as the default)
 
  
 
* When basic or composite parts are created, the user is given a list of groups that should be given editing permission
 
* When basic or composite parts are created, the user is given a list of groups that should be given editing permission
 
this list fills group_u_list. User->group is not used by other part creation.
 
this list fills group_u_list. User->group is not used by other part creation.
−
 
−
*
 

Latest revision as of 20:30, 21 December 2008

[21 Dec 2008 - Randy]

It is obvious that a user is a member of a group. In fact, they must be approved by a group leader in order to activate their account.

A field in the 'user' and 'part' tables is intended to hold this group_id.

However, a user may be a member of more than one group. The list of groups a user belongs to is derived from the table ung_db.membership limited by user_id. This is represented a the group_u_list entry in the bbdb.parts table.

Some sections of the register allow the user to specify which of its groups should apply to the action.

If User->group is to be used, then the default should be the most recent group the user has joined, or the group selected as the default by the user.

Usage:

  • Part.pm - It does not seem that owning_group_id or Part->group are used by anyone except the DAS system


  • DNA Submission System (cgi/dna_transfer and cgi/lib/DNASubmissionBatch.pm)



  • When basic or composite parts are created, the user is given a list of groups that should be given editing permission

this list fills group_u_list. User->group is not used by other part creation.