Membership Application - Revision history

Arnulf: /* Information Fields To Capture */ added current position, thoughts about checkboxes for committtees

2007-03-30T15:23:08Z

Information Fields To Capture: added current position, thoughts about checkboxes for committtees

Arnulf: /* Architecture */ Security and privacy issues.

2007-03-30T15:18:07Z

Architecture: Security and privacy issues.

Warmerdam: update status, note trac ticket.

2007-03-26T18:01:33Z

update status, note trac ticket.

Neteler: +cat Membership

2006-09-08T13:03:15Z

+cat Membership

Tmitchell: /* Information Fields To Capture */

2006-09-05T04:16:55Z

Information Fields To Capture

Tmitchell: /* Information Fields To Capture */

2006-09-04T17:12:41Z

Information Fields To Capture

Tmitchell: Added information fields to capture

2006-09-04T17:09:05Z

Added information fields to capture

Tmitchell: /* Possible drupal implementation of this */ added notes on my custom field work

2006-08-15T17:48:38Z

Possible drupal implementation of this: added notes on my custom field work

Wiki-JoWalsh: drupal notes mostly so i remember this page exists and i'm meant to be thinking about it

2006-08-09T22:16:31Z

drupal notes mostly so i remember this page exists and i'm meant to be thinking about it

Warmerdam: /* Architecture */

2006-07-13T17:05:43Z

Architecture

@@ Line 24: / Line 24: @@
 ** Link to personal blog RSS - Text URL
 * Location - general information about where a user lives
 ** Address - Text (Private)
 ** City/town - Text
@@ Line 31: / Line 37: @@
 * Community Signup - a way of showing which areas of the community they are interested in following.  Could be tied to CMS to help focus content on their personal start page or to sign them up to certain services/mailing lists.
 ** Choose mailing lists - Checkboxes
-** Choose committees of interest - Checkboxes
+** Choose committees of interest - Checkboxes (''What is this good for? People 'joining' committees shoudl go through a more thorough process making sure we don't end up with committees everybody is interested in any nobody does anything. Additionally at the point of first contact it will not be clear what a committee does by just knowing the name - imagine what would happen to FunCom'')
 ** Sponsorship interest - Checkbox
 ** Send me info - Checkbox
-* must be more...
+* must be more... (''really? All the rest should just go to the Wiki user page, there people can do whatever they want'')
 = Who to Build =

@@ Line 49: / Line 49: @@
 * It seems reasonable to keep the bulk of the information in a PostGIS database.  Easy to map from, easy to update, well supported by lots of stuff.
 * It has been suggested that WFS access be provided to this data; however, I am nervous about this due to privacy concerns.  At the very least I think this should be restricted to location, name and OSGeo userid.
+** [[User:Arnulf Christl | I]] am interested in providing security mechanisms that allow people to specify who may see what of their perosnal information (privacy) via WFS and a ticket system and to allow accessing their own data and only their own data via WFS-T.
 == Possible drupal implementation of this ==

@@ Line 38: / Line 38: @@
 = Who to Build =
-The application would be a service under the responsibility of [[SAC]].  It has been proposed that it might be built to use Mapbender for the mapping component, and that Benjamin Thelen and Astrid from CCGIS would be willing to assist in building it.   Frank Warmerdam is also willing to do some work on this.
+The application may be built by Amr Mostafa in PHP on Drupal.  The application is being treated as a responsiblility of WebCom (though it is sort of on the boundary between webcom and SAC).
 = Architecture =

← Older revision		Revision as of 13:03, 8 September 2006
Line 51:		Line 51:
	* our test drupal install already is reading / authing against LDAP. writeback may involve a shift to OpenLDAP away from Fedora directory server? drupal is mysql oriented though there is postgres support in contribs for it - but do we need that - or can we just store WKT in a text field? ;)		* our test drupal install already is reading / authing against LDAP. writeback may involve a shift to OpenLDAP away from Fedora directory server? drupal is mysql oriented though there is postgres support in contribs for it - but do we need that - or can we just store WKT in a text field? ;)
	* The drupal portal includes customisable fields in the user registration process. I've added lat/lon, country and a blog url as examples and know how to hit them from PHP queries. These should be elementary to grab direct from mysql and other scripting languages. So I think the user profiles and registration process is going to be robust enough to capture information and allow users to choose items, e.g. having a checkbox for committees they are helping with, etc.		* The drupal portal includes customisable fields in the user registration process. I've added lat/lon, country and a blog url as examples and know how to hit them from PHP queries. These should be elementary to grab direct from mysql and other scripting languages. So I think the user profiles and registration process is going to be robust enough to capture information and allow users to choose items, e.g. having a checkbox for committees they are helping with, etc.
		+
		+	[[Category:Membership]]

@@ Line 19: / Line 19: @@
 Setting up user profile fields allows users to enter information in a private or public way and then having the CMS access this information for services or views of lists of members, etc.  When information is displayed, i.e. via a query that an administrator sets up, various fields can be used to filter and sort information.
 * Biographical - information about the users interests, company, organisation affiliation, etc.
 ** Areas of interest - Text
 ** Link to personal web site - Text URL
 * Location - general information about where a user lives
 ** Address - Text (Private)
@@ Line 27: / Line 29: @@
 ** Latitude - Decimal
 ** Longitude - Decimal
 * Community Signup - a way of showing which areas of the community they are interested in following.  Could be tied to CMS to help focus content on their personal start page or to sign them up to certain services/mailing lists.
 ** Choose mailing lists - Checkboxes
 ** Choose committees of interest - Checkboxes
 * must be more...

@@ Line 12: / Line 12: @@
 The application also needs to have a mechanism for a member who joins to make a payment to be a "Supporting" member.
 We might also want an easy mechanism for new members to subscribe to the announce and discuss lists.
 = Who to Build =

← Older revision		Revision as of 17:48, 15 August 2006
Line 27:		Line 27:
	== Possible drupal implementation of this ==		== Possible drupal implementation of this ==

−	our test drupal install already is reading / authing against LDAP. writeback may involve a shift to OpenLDAP away from Fedora directory server? drupal is mysql oriented though there is postgres support in contribs for it - but do we need that - or can we just store WKT in a text field? ;)	+	* our test drupal install already is reading / authing against LDAP. writeback may involve a shift to OpenLDAP away from Fedora directory server? drupal is mysql oriented though there is postgres support in contribs for it - but do we need that - or can we just store WKT in a text field? ;)
		+	* The drupal portal includes customisable fields in the user registration process. I've added lat/lon, country and a blog url as examples and know how to hit them from PHP queries. These should be elementary to grab direct from mysql and other scripting languages. So I think the user profiles and registration process is going to be robust enough to capture information and allow users to choose items, e.g. having a checkbox for committees they are helping with, etc.

@@ Line 1: / Line 1: @@
 = Requirements =
@@ Line 24: / Line 23: @@
 * It seems reasonable to keep the bulk of the information in a PostGIS database.  Easy to map from, easy to update, well supported by lots of stuff.
 * It has been suggested that WFS access be provided to this data; however, I am nervous about this due to privacy concerns.  At the very least I think this should be restricted to location, name and OSGeo userid.