Index: openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.html,v diff -u -N -r1.3 -r1.3.24.1 --- openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.html 30 Sep 2003 12:10:03 -0000 1.3 +++ openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.html 18 Jul 2016 11:40:32 -0000 1.3.24.1 @@ -1,418 +1,418 @@ - - - -Group Admin Pages - Acceptance test - - - - -

Group Admin Pages - Acceptance test

 -ACS subsite docs : Group Admin Pages - Acceptance test -
- -

DEVELOPER DEFINED GROUP TYPES TEST

- -The first thing we have to test is developer defined group types -working in conjunction with the user defined ones. -

-Create the following object type in SQL*Plus. - -

-begin
- acs_object_type.create_type (
-   supertype => 'group',
-   object_type => 'developer_defined_test_type',
-   pretty_name => 'Developer defined test type',
-   pretty_plural => 'Developer defined test types',
-   table_name => 'developer_defined_test_types',
-   id_column => 'test_group_id',
-   package_name => 'developer_defined_test_type',
-   name_method => 'acs_group.name'
- );
-end;
-/
-show errors;   
-
-
-create table developer_defined_test_types (
-       test_group_id   integer primary key references groups(group_id)
-);
-
-
-create or replace package developer_defined_test_type
-as
-
-  function new (
-         TEST_GROUP_ID   IN DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE DEFAULT NULL,
-         GROUP_NAME      IN GROUPS.GROUP_NAME%TYPE,
-         OBJECT_TYPE     IN ACS_OBJECTS.OBJECT_TYPE%TYPE DEFAULT 'developer_defined_test_type'
-  ) return DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE;
-
-  procedure delete (
-    TEST_GROUP_ID      in DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE
-  );
-
-end developer_defined_test_type;
-/
-show errors
-
-create or replace package body developer_defined_test_type
-as
-
-  function new (
-         TEST_GROUP_ID   IN DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE DEFAULT NULL,
-         GROUP_NAME      IN GROUPS.GROUP_NAME%TYPE,
-         OBJECT_TYPE     IN ACS_OBJECTS.OBJECT_TYPE%TYPE DEFAULT 'developer_defined_test_type'
-  ) return DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE
-  is
-    v_TEST_GROUP_ID DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE;
-  begin
-
-    v_TEST_GROUP_ID := acs_group.new (
-                     group_id         => new.TEST_GROUP_ID,
-                     GROUP_NAME       => new.GROUP_NAME,
-                     OBJECT_TYPE      => new.OBJECT_TYPE
-                   );
-
-    insert into DEVELOPER_DEFINED_TEST_TYPES
-    (TEST_GROUP_ID)
-    values
-    (v_TEST_GROUP_ID);
-
-    return v_TEST_GROUP_ID;
-
-  end new;
-
-  procedure delete (
-    TEST_GROUP_ID      in DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE
-  )
-  is
-  begin
-
-    acs_group.del( developer_defined_test_type.delete.TEST_GROUP_ID );
-
-  end delete;
-
-end developer_defined_test_type;
-/
-show errors
-
-
- -
    - -
  1. Go to /admin/group-types and select "Developer defined test types" -
  2. Add a permissible rel type of Membership Relation -
  3. Add a group named "Test group" - -
- - - -

GROUP TYPE PAGES BASIC FUNCTIONALITY

- -(Start at /admin) -

- -

    - -
  1. Click on group types - -
  2. Click on Groups - -
  3. Click on "Group name" under "Attributes of this type of group" - -
  4. Ensure that you see the properties of the attribute and that you - are offered no administrative links - -
  5. Make sure you cannot add attributes or do anything under administration - -
  6. Make sure you see Composition and Membership Relation as the - default relationship types - -
  7. Add a new group called "Foobar" - Make sure Foobar appears after - adding the group - -
  8. Click on Foobar - -
  9. Click on nuke this group then click no. Ensure group is not deleted - -
  10. Click on nuke this group then click yes. Group should no longer show up - -
  11. Recreate the group Foobar - -
  12. Click on foobar, then change the name to "ArsDigita" - -
  13. Change ArsDigita's join policy to closed - -
- -

DYNAMICALLY EXTENDING GROUPS

- -(Start at /admin/group-types/) - -
    - -
  1. Click on "Define a new group type" and create a new group type - called "Project" with type "project". Ensure that all the fields - you see are required (try submitting without entering in - anything). - -
  2. Define another group type, child of group, named "Test" - -
  3. Define another group type, 'subproject', child of project. Ensure - that the index page correctly displays the hierarchy. - -
  4. Define a new group type with group type = group. See error - message saying type already exists. - -
  5. Go back to the index page (/admin/group-types). - -
  6. Click on the Test group type. Make sure that: - -
      -
    • there are no groups -
    • Group name attribute is inherited from groups -
    • you have a link to add an attribute -
    • you see Composition and Membership Relation as the default - relationship types -
    • You have a link to change the default join policy -
    • You have a link to delete the group type -
    - -
  7. Click on "Add a permissible relationship type." Ensure that you - are not given a select bar but are offered a link to "create a new - relationship type" - -
  8. Create a group of type test. - -
  9. Delete the test group type (first verify that the cancel button - works) - -
  10. Go to the "project" group type - -
  11. Add a required attribute called "Project type" of datatype - enumeration. Values are "Client" "Toolkit" - -
  12. Add an optional attribute "Monthly fee" of type integer and - default of "10000" - -
  13. Add a third attribute called test. - -
  14. Make sure you can see all the attributes. Delete the test attribute - -
  15. Go to "/admin/object-types/one?object_type=project" and ensure - that start_date and monthly fees are listed as attributes. Also - make sure: -
      -
    • test attribute is not visible -
    • monthly_fee has a default specified (NULL) in the pl/sql parameter list -
    • start_date has no default specified -
    - -
  16. Go to "/admin/object-types/one?object_type=subproject" and - ensure the new attributes of project are in the pl/sql package - -
  17. Now go back to the group type admin page for the "Projects" - group type. Remove the composition relation. Make sure you get a - link back to add a relationship type. Add back the composition - relation. - -
  18. Add a group of type project named GuideStar.org - -
- -

RELATIONSHIP TYPE PAGES BASIC FUNCTIONALITY

- -
    - -
  1. Create a new relationship type, Employment relation, that is a - subtype of Membership relation, between group and person. Group - has role of employer, person role of employee. - -
  2. Select the employment relation and add an attribute age (integer, - not required) - -
  3. Delete the employment relationship type. - -
  4. Re-add the employment relationship type (we're testing to make - sure the age attribute is correctly removed and flushed from the - cache) - -
  5. Click on membership relation, then click on create subtype - -
  6. Click on membership relation -> Create subtype - type: project_lead_relation - name: Project Lead - between projects (the composite) and persons (the project leader - new role) - -
  7. Create a new, dummy rel type, subtype of Project Lead - Relation. Make sure the only things in object type one are - project and subproject - -
  8. Select the dummy relationship type and then delete it. - -
  9. Select the Employment relation and add a required attribute - "salary" (type integer) - -
- -

SEGMENTS, CONSTRAINTS AND RELATIONS

- -
    - -
  1. Go back to the admin page (/admin) - -
  2. Click on the Groups -> GuideStar.org. Add ArsDigita as a component - -
  3. Remove the composition rel type from this group - -
  4. Readd the composition rel type. Make sure arsdigita doesn't show up - -
  5. remove the composition rel type - -
  6. Add a permissible rel type: project_lead_relation - -
  7. Click yes to create a rel segment named "GuideStar Project Leads" - -
  8. Go back to /admin/groups - -
  9. Click on "relationship to site" - -
  10. Remove yourself from the group. - -
  11. Add yourself again as a member (using the membership - relation). You will have to select an existing party from the - system. - -
  12. Make sure you see the segment "Main Site Members" for parties - with a membership relation to the main site. - -
  13. Go to the ArsDigita group. - -
  14. Add guidestar.org as a component - -
  15. Remove the membership relation type from this group - -
  16. Add the employment relation type - -
  17. Create a segment named "ArsDigita employees" - -
  18. Add a constraint named "ArsDigita employees must be Main Site - Members" for employees and the segment "Main Site Members" - -
  19. Go back to the guidestar.org group - -
  20. Add yourself as a project lead. - -
  21. Click on the project lead segment "GuideStar Project Leads" - -
  22. Click delete this segment. Say no. - -
  23. Click delete this segment. Say Yes. - -
  24. Recreate the "GuideStar Project Leads" segment - -
  25. Add a constraint named "Project leads must be employees" that - says all "project leaders must be employees of ArsDigita" - -
  26. Make sure you see yourself as a violation. Remove the violating - relation and finish adding the constraint - -
  27. Try to add a project leader to guidestar. You should see that - there "There is no other Person that can be added as Project Leader to - GuideStar.Org" - -
  28. Add yourself as an arsdigita employee - -
  29. Make yourself the project lead on guidestar.org - -
  30. Go back to /admin/groups and select "relationship typ site." - Remove your membership relation. You should get prompted to - remove relation to arsdigita, then to guidestar. Remove all of - these relations. - -
  31. Make yourself a project lead of guidestar again. - -
- -

Testing with more Users

- -Now we're going to test that the user interface remains consistent if -there are a few more users. - -
    - -
  1. Go to /acs-admin/users and add 4 users - -
  2. Go to /admin/groups and click on "relationship to site." You - should see all of the people you just entered listed as members of - the subsite. - -
  3. Try to remove your Membership relation. You should see only one - constraint violation. - -
  4. Remove one of the other people from the registered users - group. You should be allowed to do it immediately. - -
  5. Add back the person you removed. - -
  6. Remove yourself from the registered users group. Make yourself - a project lead on guidestar again. - -
  7. Make another user a project lead on guidestar. - -
- - - -

CLEANING UP

- -
    -
  1. Go to /admin/group-types - -
  2. Select the project group type - -
  3. Delete this group type. Should get prompted to delete sub - projects group type. - -
  4. Delete the sub projects group type. - -
  5. Should get prompt to delete the project lead rel type - -
  6. Delete the project lead rel type. Continue until you delete the - project group type. - -
  7. Delete the ArsDigita group. - -
  8. Go to /admin/rel-types/ - -
  9. Click on "View all roles" - -
  10. Click on "Project Leader" - delete this role - -
  11. Click on "Employer" then on Employment Relation - -
  12. Delete the employment relation type. - -
  13. Delete the employee, employer, and project_leader roles - -
  14. Delete any groups you created for the developer defined type - -
  15. Drop the developer defined type (in SQL*Plus): - -
    -exec acs_object_type.drop_type('developer_defined_test_type'); 
-drop table developer_defined_test_types;
-drop package developer_defined_test_type;
-
    - -
- - -
-
Michael Bryzek
-
$Id$ - - + + + +Group Admin Pages - Acceptance test + + + + +

Group Admin Pages - Acceptance test

 +ACS subsite docs : Group Admin Pages - Acceptance test +
+ +

DEVELOPER DEFINED GROUP TYPES TEST

+ +The first thing we have to test is developer defined group types +working in conjunction with the user defined ones. +

+Create the following object type in SQL*Plus. + +

+begin
+ acs_object_type.create_type (
+   supertype => 'group',
+   object_type => 'developer_defined_test_type',
+   pretty_name => 'Developer defined test type',
+   pretty_plural => 'Developer defined test types',
+   table_name => 'developer_defined_test_types',
+   id_column => 'test_group_id',
+   package_name => 'developer_defined_test_type',
+   name_method => 'acs_group.name'
+ );
+end;
+/
+show errors;   
+
+
+create table developer_defined_test_types (
+       test_group_id   integer primary key references groups(group_id)
+);
+
+
+create or replace package developer_defined_test_type
+as
+
+  function new (
+         TEST_GROUP_ID   IN DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE DEFAULT NULL,
+         GROUP_NAME      IN GROUPS.GROUP_NAME%TYPE,
+         OBJECT_TYPE     IN ACS_OBJECTS.OBJECT_TYPE%TYPE DEFAULT 'developer_defined_test_type'
+  ) return DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE;
+
+  procedure delete (
+    TEST_GROUP_ID      in DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE
+  );
+
+end developer_defined_test_type;
+/
+show errors
+
+create or replace package body developer_defined_test_type
+as
+
+  function new (
+         TEST_GROUP_ID   IN DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE DEFAULT NULL,
+         GROUP_NAME      IN GROUPS.GROUP_NAME%TYPE,
+         OBJECT_TYPE     IN ACS_OBJECTS.OBJECT_TYPE%TYPE DEFAULT 'developer_defined_test_type'
+  ) return DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE
+  is
+    v_TEST_GROUP_ID DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE;
+  begin
+
+    v_TEST_GROUP_ID := acs_group.new (
+                     group_id         => new.TEST_GROUP_ID,
+                     GROUP_NAME       => new.GROUP_NAME,
+                     OBJECT_TYPE      => new.OBJECT_TYPE
+                   );
+
+    insert into DEVELOPER_DEFINED_TEST_TYPES
+    (TEST_GROUP_ID)
+    values
+    (v_TEST_GROUP_ID);
+
+    return v_TEST_GROUP_ID;
+
+  end new;
+
+  procedure delete (
+    TEST_GROUP_ID      in DEVELOPER_DEFINED_TEST_TYPES.TEST_GROUP_ID%TYPE
+  )
+  is
+  begin
+
+    acs_group.del( developer_defined_test_type.delete.TEST_GROUP_ID );
+
+  end delete;
+
+end developer_defined_test_type;
+/
+show errors
+
+
+ +
    + +
  1. Go to /admin/group-types and select "Developer defined test types" +
  2. Add a permissible rel type of Membership Relation +
  3. Add a group named "Test group" + +
+ + + +

GROUP TYPE PAGES BASIC FUNCTIONALITY

+ +(Start at /admin) +

+ +

    + +
  1. Click on group types + +
  2. Click on Groups + +
  3. Click on "Group name" under "Attributes of this type of group" + +
  4. Ensure that you see the properties of the attribute and that you + are offered no administrative links + +
  5. Make sure you cannot add attributes or do anything under administration + +
  6. Make sure you see Composition and Membership Relation as the + default relationship types + +
  7. Add a new group called "Foobar" - Make sure Foobar appears after + adding the group + +
  8. Click on Foobar + +
  9. Click on nuke this group then click no. Ensure group is not deleted + +
  10. Click on nuke this group then click yes. Group should no longer show up + +
  11. Recreate the group Foobar + +
  12. Click on foobar, then change the name to "ArsDigita" + +
  13. Change ArsDigita's join policy to closed + +
+ +

DYNAMICALLY EXTENDING GROUPS

+ +(Start at /admin/group-types/) + +
    + +
  1. Click on "Define a new group type" and create a new group type + called "Project" with type "project". Ensure that all the fields + you see are required (try submitting without entering in + anything). + +
  2. Define another group type, child of group, named "Test" + +
  3. Define another group type, 'subproject', child of project. Ensure + that the index page correctly displays the hierarchy. + +
  4. Define a new group type with group type = group. See error + message saying type already exists. + +
  5. Go back to the index page (/admin/group-types). + +
  6. Click on the Test group type. Make sure that: + +
      +
    • there are no groups +
    • Group name attribute is inherited from groups +
    • you have a link to add an attribute +
    • you see Composition and Membership Relation as the default + relationship types +
    • You have a link to change the default join policy +
    • You have a link to delete the group type +
    + +
  7. Click on "Add a permissible relationship type." Ensure that you + are not given a select bar but are offered a link to "create a new + relationship type" + +
  8. Create a group of type test. + +
  9. Delete the test group type (first verify that the cancel button + works) + +
  10. Go to the "project" group type + +
  11. Add a required attribute called "Project type" of datatype + enumeration. Values are "Client" "Toolkit" + +
  12. Add an optional attribute "Monthly fee" of type integer and + default of "10000" + +
  13. Add a third attribute called test. + +
  14. Make sure you can see all the attributes. Delete the test attribute + +
  15. Go to "/admin/object-types/one?object_type=project" and ensure + that start_date and monthly fees are listed as attributes. Also + make sure: +
      +
    • test attribute is not visible +
    • monthly_fee has a default specified (NULL) in the pl/sql parameter list +
    • start_date has no default specified +
    + +
  16. Go to "/admin/object-types/one?object_type=subproject" and + ensure the new attributes of project are in the pl/sql package + +
  17. Now go back to the group type admin page for the "Projects" + group type. Remove the composition relation. Make sure you get a + link back to add a relationship type. Add back the composition + relation. + +
  18. Add a group of type project named GuideStar.org + +
+ +

RELATIONSHIP TYPE PAGES BASIC FUNCTIONALITY

+ +
    + +
  1. Create a new relationship type, Employment relation, that is a + subtype of Membership relation, between group and person. Group + has role of employer, person role of employee. + +
  2. Select the employment relation and add an attribute age (integer, + not required) + +
  3. Delete the employment relationship type. + +
  4. Re-add the employment relationship type (we're testing to make + sure the age attribute is correctly removed and flushed from the + cache) + +
  5. Click on membership relation, then click on create subtype + +
  6. Click on membership relation -> Create subtype + type: project_lead_relation + name: Project Lead + between projects (the composite) and persons (the project leader + new role) + +
  7. Create a new, dummy rel type, subtype of Project Lead + Relation. Make sure the only things in object type one are + project and subproject + +
  8. Select the dummy relationship type and then delete it. + +
  9. Select the Employment relation and add a required attribute + "salary" (type integer) + +
+ +

SEGMENTS, CONSTRAINTS AND RELATIONS

+ +
    + +
  1. Go back to the admin page (/admin) + +
  2. Click on the Groups -> GuideStar.org. Add ArsDigita as a component + +
  3. Remove the composition rel type from this group + +
  4. Readd the composition rel type. Make sure arsdigita doesn't show up + +
  5. remove the composition rel type + +
  6. Add a permissible rel type: project_lead_relation + +
  7. Click yes to create a rel segment named "GuideStar Project Leads" + +
  8. Go back to /admin/groups + +
  9. Click on "relationship to site" + +
  10. Remove yourself from the group. + +
  11. Add yourself again as a member (using the membership + relation). You will have to select an existing party from the + system. + +
  12. Make sure you see the segment "Main Site Members" for parties + with a membership relation to the main site. + +
  13. Go to the ArsDigita group. + +
  14. Add guidestar.org as a component + +
  15. Remove the membership relation type from this group + +
  16. Add the employment relation type + +
  17. Create a segment named "ArsDigita employees" + +
  18. Add a constraint named "ArsDigita employees must be Main Site + Members" for employees and the segment "Main Site Members" + +
  19. Go back to the guidestar.org group + +
  20. Add yourself as a project lead. + +
  21. Click on the project lead segment "GuideStar Project Leads" + +
  22. Click delete this segment. Say no. + +
  23. Click delete this segment. Say Yes. + +
  24. Recreate the "GuideStar Project Leads" segment + +
  25. Add a constraint named "Project leads must be employees" that + says all "project leaders must be employees of ArsDigita" + +
  26. Make sure you see yourself as a violation. Remove the violating + relation and finish adding the constraint + +
  27. Try to add a project leader to guidestar. You should see that + there "There is no other Person that can be added as Project Leader to + GuideStar.Org" + +
  28. Add yourself as an arsdigita employee + +
  29. Make yourself the project lead on guidestar.org + +
  30. Go back to /admin/groups and select "relationship typ site." + Remove your membership relation. You should get prompted to + remove relation to arsdigita, then to guidestar. Remove all of + these relations. + +
  31. Make yourself a project lead of guidestar again. + +
+ +

Testing with more Users

+ +Now we're going to test that the user interface remains consistent if +there are a few more users. + +
    + +
  1. Go to /acs-admin/users and add 4 users + +
  2. Go to /admin/groups and click on "relationship to site." You + should see all of the people you just entered listed as members of + the subsite. + +
  3. Try to remove your Membership relation. You should see only one + constraint violation. + +
  4. Remove one of the other people from the registered users + group. You should be allowed to do it immediately. + +
  5. Add back the person you removed. + +
  6. Remove yourself from the registered users group. Make yourself + a project lead on guidestar again. + +
  7. Make another user a project lead on guidestar. + +
+ + + +

CLEANING UP

+ +
    +
  1. Go to /admin/group-types + +
  2. Select the project group type + +
  3. Delete this group type. Should get prompted to delete sub + projects group type. + +
  4. Delete the sub projects group type. + +
  5. Should get prompt to delete the project lead rel type + +
  6. Delete the project lead rel type. Continue until you delete the + project group type. + +
  7. Delete the ArsDigita group. + +
  8. Go to /admin/rel-types/ + +
  9. Click on "View all roles" + +
  10. Click on "Project Leader" - delete this role + +
  11. Click on "Employer" then on Employment Relation + +
  12. Delete the employment relation type. + +
  13. Delete the employee, employer, and project_leader roles + +
  14. Delete any groups you created for the developer defined type + +
  15. Drop the developer defined type (in SQL*Plus): + +
    +exec acs_object_type.drop_type('developer_defined_test_type'); 
+drop table developer_defined_test_types;
+drop package developer_defined_test_type;
+
    + +
+ + +
+
Michael Bryzek
+
$Id$ + + Index: openacs-4/packages/acs-subsite/www/doc/group-admin-pages-design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-subsite/www/doc/group-admin-pages-design.html,v diff -u -N -r1.3.2.1 -r1.3.2.2 --- openacs-4/packages/acs-subsite/www/doc/group-admin-pages-design.html 9 Jun 2016 08:12:14 -0000 1.3.2.1 +++ openacs-4/packages/acs-subsite/www/doc/group-admin-pages-design.html 18 Jul 2016 11:40:32 -0000 1.3.2.2 @@ -11,10 +11,10 @@

II. Introduction

@@ -138,8 +138,8 @@

-Note that the dynamic_p is still experimental and may -be removed in a future version of ACS +Note that the dynamic_p is still experimental and may +be removed in a future version of ACS

VII. Data Model Discussion

@@ -188,9 +188,9 @@ key insights early in the development process.

XII. Revision History

Index: openacs-4/packages/acs-subsite/www/doc/group-admin-pages-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-subsite/www/doc/group-admin-pages-requirements.html,v diff -u -N -r1.2 -r1.2.30.1 --- openacs-4/packages/acs-subsite/www/doc/group-admin-pages-requirements.html 11 Aug 2001 21:31:03 -0000 1.2 +++ openacs-4/packages/acs-subsite/www/doc/group-admin-pages-requirements.html 18 Jul 2016 11:40:32 -0000 1.2.30.1 @@ -56,7 +56,7 @@

IV. Use case and User Scenarios

-The Intranet Application +The Intranet Application

The Intranet application may model employees in many ways. Without @@ -66,11 +66,11 @@ company represents one instance of the intranet application.

- +
-
+ -
Figure 1: Structure of Multiple Intranets +
Figure 1: Structure of Multiple Intranets
@@ -105,14 +105,14 @@
-
10.10 Default relationship types for group types
+
10.10 Default relationship types for group types

Each group type should specify a set of permissible relationship types to use for groups of that type.

-

10.20 Default relationship types for groups
+

10.20 Default relationship types for groups

@@ -129,15 +129,15 @@

-
20.10 Define a new group type
+
20.10 Define a new group type

Users should be able to create a new type of group.

-
30.10 Specify attributes
+
30.10 Specify attributes

@@ -146,7 +146,7 @@

-
35.10 Remove attributes
+
35.10 Remove attributes

@@ -156,7 +156,7 @@

-
40.10 Relationship Constraints
+
40.10 Relationship Constraints

@@ -166,7 +166,7 @@

-

40.10.10 Permissible relationships
+
40.10.10 Permissible relationships

@@ -175,7 +175,7 @@

-
40.10.20 Constraints on relationships
+
40.10.20 Constraints on relationships

@@ -186,7 +186,7 @@

-
40.10.30 Constrain membership to a given group
+
40.10.30 Constrain membership to a given group

@@ -207,7 +207,7 @@

-
100.10 Create a group type with attributes
+
100.10 Create a group type with attributes

@@ -216,11 +216,11 @@

-
130.10 Group type summary page
+
130.10 Group type summary page
-
130.10.10 Display allowable relationship types
+
130.10.10 Display allowable relationship types

@@ -231,7 +231,7 @@

-
130.10.20 Display groups
+
130.10.20 Display groups

@@ -240,7 +240,7 @@

-
110.10 Create an instance of a particular group type
+
110.10 Create an instance of a particular group type

@@ -251,15 +251,15 @@

-
130.10.20 Display type attributes
+
130.10.20 Display type attributes

Display all attributes for this group type, including supertypes.

-
130.10.20 Delete group type
+
130.10.20 Delete group type

@@ -272,11 +272,11 @@

-
150.10 Group instance summary page
+
150.10 Group instance summary page
-
150.10.10 Display relations
+
150.10.10 Display relations

@@ -287,15 +287,15 @@

-
150.10.20 Display attributes
+
150.10.20 Display attributes

Display all attributes of the group with links to edit each.

-
150.10.20 Delete group
+
150.10.20 Delete group

@@ -304,7 +304,7 @@

-
150.20 Integration with relational Segments and Constraints
+
150.20 Integration with relational Segments and Constraints

@@ -323,11 +323,11 @@

Revision History

- +
- - - + + + Index: openacs-4/packages/acs-datetime/www/doc/coversheet.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-datetime/www/doc/coversheet.html,v diff -u -N -r1.1.1.1 -r1.1.1.1.28.1 --- openacs-4/packages/acs-datetime/www/doc/coversheet.html 20 Apr 2001 20:51:09 -0000 1.1.1.1 +++ openacs-4/packages/acs-datetime/www/doc/coversheet.html 18 Jul 2016 11:46:38 -0000 1.1.1.1.28.1 @@ -9,7 +9,7 @@

ACS DateTime

-by ron@arsdigita.com +by ron@arsdigita.com
Index: openacs-4/packages/acs-datetime/www/doc/design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-datetime/www/doc/design.html,v diff -u -N -r1.1.1.1 -r1.1.1.1.28.1 --- openacs-4/packages/acs-datetime/www/doc/design.html 20 Apr 2001 20:51:09 -0000 1.1.1.1 +++ openacs-4/packages/acs-datetime/www/doc/design.html 18 Jul 2016 11:46:38 -0000 1.1.1.1.28.1 @@ -59,7 +59,7 @@

Date and Time functions

-

See examples. +

See examples.

  1. dt_systime generates current system time (local or GMT) @@ -82,7 +82,7 @@

    Date and Time widgets

    -

    See examples. +

    See examples.

    1. dt_widget_datetime generate HTML select widgets of varying granularity for @@ -96,7 +96,7 @@

      Calendar widgets

      -

      See examples.

      +

      See examples.

      Each of the following allow the programmer to supply calendar details in an ns_set keyed on Julian date and returns an @@ -125,14 +125,14 @@

      XIII. Authors

      Implemented by Ron Henderson (ron@arsdigita.com), based on the +href="mailto:ron@arsdigita.com">ron@arsdigita.com), based on the previous work of gregh@arsdigita.com and smeeks@arsdigita.com.

      +href="mailto:gregh@arsdigita.com">gregh@arsdigita.com and smeeks@arsdigita.com.

      -ron@arsdigita.com +ron@arsdigita.com Index: openacs-4/packages/acs-datetime/www/doc/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-datetime/www/doc/index.html,v diff -u -N -r1.1.1.1.28.2 -r1.1.1.1.28.3 --- openacs-4/packages/acs-datetime/www/doc/index.html 21 Aug 2015 10:49:20 -0000 1.1.1.1.28.2 +++ openacs-4/packages/acs-datetime/www/doc/index.html 18 Jul 2016 11:46:38 -0000 1.1.1.1.28.3 @@ -5,11 +5,11 @@ ACS DateTime Documentation - +

      ACS DateTime Documentation

      -ron@arsdigita.com +ron@arsdigita.com

      Index: openacs-4/packages/acs-datetime/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-datetime/www/doc/requirements.html,v diff -u -N -r1.2.26.1 -r1.2.26.2 --- openacs-4/packages/acs-datetime/www/doc/requirements.html 21 Aug 2015 10:49:20 -0000 1.2.26.1 +++ openacs-4/packages/acs-datetime/www/doc/requirements.html 18 Jul 2016 11:46:38 -0000 1.2.26.2 @@ -4,7 +4,7 @@ ACS DateTime - +

      ACS DateTime Requirements

      Index: openacs-4/packages/acs-datetime/www/doc/examples/calendar-navigation.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-datetime/www/doc/examples/calendar-navigation.adp,v diff -u -N -r1.5 -r1.5.2.1 --- openacs-4/packages/acs-datetime/www/doc/examples/calendar-navigation.adp 3 Jul 2015 10:25:41 -0000 1.5 +++ openacs-4/packages/acs-datetime/www/doc/examples/calendar-navigation.adp 18 Jul 2016 11:46:38 -0000 1.5.2.1 @@ -5,15 +5,15 @@ @title;literal@ @context;literal@ -
      dt_widget_calendar_navigation base_url view date pass_in_vars
      +
      dt_widget_calendar_navigation base_url view date pass_in_vars

      -

      Parameters:
      -base_url (optional)
      -view (defaults to week)
      -date (optional)
      -pass_in_vars (optional)
      +

      Parameters:
      +base_url (optional)
      +view (defaults to week)
      +date (optional)
      +pass_in_vars (optional)
      Index: openacs-4/packages/general-comments/www/doc/design.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/general-comments/www/doc/design.adp,v diff -u -N -r1.1.2.5 -r1.1.2.6 --- openacs-4/packages/general-comments/www/doc/design.adp 5 Jul 2016 16:52:02 -0000 1.1.2.5 +++ openacs-4/packages/general-comments/www/doc/design.adp 18 Jul 2016 11:45:37 -0000 1.1.2.6 @@ -62,16 +62,16 @@

      1.2.6. API

      Tcl API

      There is one core procedure, general_comments_get_comments, that will show comments on an object and make appropriate links to files from the -general-comments package for -recording and editing user comments. An optional return_url can be specified which will be -provided as a link to the user within the general-comments pages. This is useful for +general-comments package for +recording and editing user comments. An optional return_url can be specified which will be +provided as a link to the user within the general-comments pages. This is useful for the user to return to the original page after making a comment.

      The other procedure, general_comments_create_link, is a wrapper procedure that returns an html fragment for a link which points to the -location of the mounted general_comments package. There are various +location of the mounted general_comments package. There are various switches that will be useful to package developers:

      • object_name: A name for the object -being commented on is displayed throughout the general-comments pages. Defaults to +being commented on is displayed throughout the general-comments pages. Defaults to [acs_object_name].

      • link_text: The text of the link returned. Defaults to "Add a comment".

      • @@ -82,14 +82,14 @@ complete. The purpose is to allow separation of comments on the same object into categories.

      A problem that may occur is when any of the two tcl procedures -are called when the general-comments package is not mounted. Both -general_comments_get_comments and -general_comments_create_link needs -to find out the location of the mounted general-comments instance to generate correct +are called when the general-comments package is not mounted. Both +general_comments_get_comments and +general_comments_create_link needs +to find out the location of the mounted general-comments instance to generate correct links. In this case, both procedures will return nothing and log a notice.

      Note: In the alpha release of -general-comments, the tcl +general-comments, the tcl procedures were defined within a namespace and encountered problems with the api browser not being able to display them properly. These procedures have now been moved out of the namespace and the old @@ -98,31 +98,31 @@

      1.2.7. Data Model Discussion

      The majority of the functionality of general comments has been -merged with acs-messaging. Comments are stored as acs-messages.

      The general_comments table -extends acs_messages to provide -categorization of comments on a particular object. general_comments also stores the object_id of +merged with acs-messaging. Comments are stored as acs-messages.

      The general_comments table +extends acs_messages to provide +categorization of comments on a particular object. general_comments also stores the object_id of the object the comment refers to. Relationships from attachments to -acs-message is done by using the cr_items.parent_id column.

      A general-comment can be -associated with any object in the system by using the general_comments.object_id column. Because +acs-message is done by using the cr_items.parent_id column.

      A general-comment can be +associated with any object in the system by using the general_comments.object_id column. Because each comment is itself an object, we could implement comments on comments. However, this functionality is not needed in the -general-comments model and the UI +general-comments model and the UI does not support comments on comments.

      There are three types of attachments a user can create: file, image, and url. The underlying data representation of an attachment is a content item with different content_types. File attachments are stored with a content_revision type. Image attachments are stored with a image type. Url attachments are stored with a content_extlink type.

      One problem we face is how to allow designers to modify the presentation of the comments on an object without modifying tcl -code. The proc general_comments_get_comments has html code +code. The proc general_comments_get_comments has html code which should really be placed into a template. Karl Goldstein code reviewed general comments and has an interesting solution:

        -

      • Add an -uplevel parameter to -db_multirow.

      • In the general_comments_get_comments proc, create an -upleveled datasource.

      • From the .tcl page, make a call -to general_comments_get_comments, +

      • Add an -uplevel parameter to +db_multirow.

      • In the general_comments_get_comments proc, create an +upleveled datasource.

      • From the .tcl page, make a call +to general_comments_get_comments, which would set up the multirow datasource in the current -environment.

      • From the .adp page, loop through +environment.

      • From the .adp page, loop through the multirow datasource.

      @@ -135,13 +135,13 @@

      1.2.9. Configuration/Parameters

      • -AutoApproveCommentsP: Sets +AutoApproveCommentsP: Sets whether comments go live immediately.

      • -AllowFileAttachmentsP: Sets +AllowFileAttachmentsP: Sets whether files can be attached to comments.

      • -AllowLinkAttachmentsP: Sets +AllowLinkAttachmentsP: Sets whether links can be attached to comments.

      • -MaxFileSize: Maximum file size +MaxFileSize: Maximum file size that can be uploaded in bytes.

      Index: openacs-4/packages/general-comments/www/doc/design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/general-comments/www/doc/design.html,v diff -u -N -r1.2 -r1.2.2.1 --- openacs-4/packages/general-comments/www/doc/design.html 27 Oct 2014 16:41:44 -0000 1.2 +++ openacs-4/packages/general-comments/www/doc/design.html 18 Jul 2016 11:45:37 -0000 1.2.2.1 @@ -136,15 +136,15 @@ >

    2. general-comments-create.sql

    3. general-comments-drop.sql

Document Revision #Action Taken, Notes
Document Revision #Action Taken, Notes When? By Whom?