Index: openacs-4/packages/categories/www/doc/design.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/categories/www/doc/design.adp,v diff -u -r1.1.2.3 -r1.1.2.4 --- openacs-4/packages/categories/www/doc/design.adp 9 Jun 2016 13:03:12 -0000 1.1.2.3 +++ openacs-4/packages/categories/www/doc/design.adp 3 Jul 2016 17:14:00 -0000 1.1.2.4 @@ -11,51 +11,53 @@ When a package admin clicks on an Administer Categories link, they are presented with a page that shows the following items:
In addition to mapping an entire tree to an object, admins have
the option of mapping only a subtree of an existing tree. To do
-that, they have to click on a "Map subtree" link, after which they
-will see a list of tree nodes.
+that, they have to click on a "Map subtree" link, after
+which they will see a list of tree nodes.
The mapped subtree will consist of all subcategories of the
category the user selected - the category itself will not be
included. Note that the mapped subtree will not be a new tree.
Therefore this option should be used only if an admin plans to use
-the subtree 'as is' and has no intention of making changes to
-it.
An alternative solution is available for admins who want to
create a tree by copying one of the existing trees and subsequently
playing around with it (moving/adding/deleting categories). To
accomplish that, they would have to create a new tree, go to the
-admin page for this tree and click on a "Copy existing tree" link.
-They will see a list of available trees to copy. Clicking on the
-"Copy this one" link will result in creating copies of the
-categories from the source trees and placing them in the new
-tree.
+admin page for this tree and click on a "Copy existing
+tree" link. They will see a list of available trees to copy.
+Clicking on the "Copy this one" link will result in
+creating copies of the categories from the source trees and placing
+them in the new tree.
This operation can be performed several times, each time the copied
categories will be placed as toplevel categories of the tree.
As far as unmapping is concerned, this operation doesn't delete -the mapping between categories and objects.
+As far as unmapping is concerned, this operation doesn't +delete the mapping between categories and objects.
Permissions
The creator of the category tree is granted the
category_tree_read, category_tree_write and
category_tree_grant_permissions privileges.
The operations one can perform on categories are:
+The operations one can perform on categories +are:
Here the tree's name and description is stored in different +
Here the tree's name and description is stored in different translations.
create table category_tree_translations ( @@ -103,8 +105,9 @@ about the parent category. The tree is ordered by a nested index (left_ind, right_ind). Sorting is thus accomplished by means of a nested set. You can read a -description of how nested sets work. This also describes how -to write queries that sort correctly when using categories. +description of how nested sets work. This also describes +how to write queries that sort correctly when using +categories.create table categories ( category_id integer primary key Index: openacs-4/packages/categories/www/doc/design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/categories/www/doc/design.html,v diff -u -r1.2 -r1.2.14.1 --- openacs-4/packages/categories/www/doc/design.html 12 Jul 2004 14:49:55 -0000 1.2 +++ openacs-4/packages/categories/www/doc/design.html 3 Jul 2016 17:14:00 -0000 1.2.14.1 @@ -17,7 +17,7 @@