Taggi2 is in beta. Content is being migrated from the legacy Taggi site and may be incomplete or incorrect.
UNSW Sydney
Accounts

User managed groups

Some groups, although ongoing, have frequent changes to their membership; for example students joining and leaving a project every semester. In order to save…

Work in progress

This page was automatically migrated from the legacy Taggi site ( https://taggi.cse.unsw.edu.au/FAQ/User_managed_groups/) and is pending review. Content, links and screenshots may be incomplete or incorrect.

Using UMGs

UMGs, the UDB, and expiry dates

UMGs are implimented by creating a user and group in the UDB that has the name of the UMG. The priv umg command simply ensures that for most of its operations, the user running it matches the owner part of the UMG name (ie: the string before the '+'). The UMG user and group can be viewed using acc just like any other User Database entry, you just have to prepend 'user.' to the UMG username. ie: % acc user.fbloggs+thesis Group Name : fbloggs+thesis Id : 99999 Expires : 31 Mar 2008 User classes : UserManagedGroupAccount Waste Basket UID : 65619 Printer Usage Status : Run "priv pquota" to initialise this information % acc group.fbloggs+thesis Group Name : fbloggs+thesis Id : 99999 Gid : 88888 Groups : fbloggs+thesis Expires : NEVER (structural) Group classes : UserManagedGroup Members : user.fbloggs|user.s1234567, user.jdoe|user.s7654321 % priv umg list fbloggs+thesis fbloggs 31mar2008 jdoe 20dec2007 Note that in the example above:

  • The UMG: fbloggs+thesis has the expiry date of 31mar2008 (matching the expiry date of its UDB entity: user.fbloggs+thesis);
  • The UDB group: group.fbloggs+thesis, is a structural entity that will usually never expire;
  • The two users that are members of the UMG (fbloggs and jdoe), have membership expiry dates that either preceed or equal the UMG's expiry date;

In general:

  • No UMG member can have a membership expiry date that is later than the expiry date of the UMG itself.
  • No UMG can have an expiry date that is later than the expiry date of the UMG's owner.

Thus:

  • If a UMG is about to expire (ie: the UMG user is about to expire), then as long as the UMG owner has an expiry date that is later than the UMG user, then the UMG owner may extend the expiry of the UMG to the same date as the UMG owner's expiry date by using the command: % priv umg renew UMGNAME
  • If a user's UMG membership is about to expire, then as long as the UMG itself has an expiry date that is later than the UMG membership expiry date, the UMG owner may extend the membership of that user in the UMG to any DATE up to and including the UMG's expiry date by using the command: % priv umg extend UMGNAME USER DATE

Group-owned UMGs

On this page