An interesting conversation about contacts in #geonode is summarized below:
Problems -------------- 1. Any user could edit other user's contact information in the metadata form. 2. There were two buttons to update or save a new object that needed an implementation/rethinking [0] Terms --------- Bound and Unbound contact fields: A contact field is bound when it has a User object attached (i.e. it corresponds to a real geonode user). A contact field is unbound when it does not correspond to a Geonode user. Decisions --------------- 1. A unbound user can be associated with one and only one Layer. A bound user can be associated to one or many layers. 2. There would be a drop down list to select between the bound contacts [1] and a final option to use an unbound contact that reads something like: "this person isn't on geonode yet" and a form to fill all the details is displayed. 3. If someone wants to edit the profile information (contact info) of a bound user, he has to either be the user or be an admin and use the profile edit view or the admin to do that. 4. By default when doing a batch upload (relying on the slurp method in the layer manager), the geonode default admin user is used (this is the superuser with the lowest id value). Ariel [0] http://cl.ly/683a8f2b69d567c04c2c [1] http://img.skitch.com/20100713-mue2ibwsctcrbefju6a32sna13.png
