[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-cvs] ged/doc TODO

From: Pascal Vilarem
Subject: [Phpgroupware-cvs] ged/doc TODO
Date: Sat, 17 Jun 2006 18:22:08 +0000

CVSROOT:        /sources/phpgroupware
Module name:    ged
Changes by:     Pascal Vilarem <maat>   06/06/17 18:22:07

Modified files:
        doc            : TODO 

Log message:
        Added Sigurd ideas in todo


Index: TODO
RCS file: /sources/phpgroupware/ged/doc/TODO,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- TODO        17 Jun 2006 18:19:26 -0000      1.2
+++ TODO        17 Jun 2006 18:22:07 -0000      1.3
@@ -1,3 +1,96 @@
+01/04/2006 from sigurd Ness
+It would be nice if documents are organized into projects - that could
+be linked to both (one or the other) projects in the app 'projects' and
+projects the app 'property'.
+The app property is a facilities management system - and the
+project-submodule would have good use for ged as a tool for coordination
+/ validation and sharing of documents for house-building-projects where
+many actors are involved and there is a complex structure of information
+along different stages.
+It would also be nice feature if involved parties (users and groups)
+would get a reminder (an email and an item on an internal "todo-list" as
+a part of a workflow) when new documents are added or documents are updated.
+As a last feature to take over the marked from proprietary commercial
+system - there would be a need for distributed print-outs - that is - to
+order prints from selected documents (drawings) by listed vendors of
+such services - and delivered to address of choice.
+As acl_location for the documents I would recommend a combination of
+project_ID and folder-name.
+The acl_locations goes into the table phpgw_acl_location.
+There are two different aspects of the acl:
+1) Give groups/users permission per locations within applications.
+2) Grant other users rights related to ones (the grantor) records. These
+rights can be defined with a group as the grantor (only admin-users can
+do this).
+Locations that are to be part of inheritance are named as:
+The locations "run" and 'changepassword' are not listed at locations,
+and are not subject to inheritance - because these locations are handled
+in the user-setup.
+Locations must be allowed to give grant - this is set in the
+allow_grant-column in the phpgw_acl_location-table.
+As an example - only the location '.user' is allowed to give grant in
+the app 'hrm'.
+Global categories for the application will be listed for both permission
+and granting as:
+$locations[$i]['id']    = 'C' . $cat['id'];
+$locations[$i]['descr']    = $cat['name'];
+The acl-class checks the groups-rights first - and then re-check for
+One can give a group some rights - and then mask - or give additional
+rights for specified users.
+In order to check if a user is allowed to add a record in
+'.location1.sublocation1' at 'some_application' - one has to check for:
+if the applicationname is not given - currentapp will be assumed.
+check for grants:
+in so-class:
+    .
+    .
+    .
+while ($this->db->next_record())
+    $ngrants = $this->grants[$this->db->f('account_id')];
+    $account_info[] = array
+    (
+        'value'        => $this->db->f('value'),
+        'grants'    => $ngrants
+    );
 30/03/2006 From Dave Hall

reply via email to

[Prev in Thread] Current Thread [Next in Thread]