Bug #1073


Allow Users to edit Entities that they own

Added by Michael Lee over 19 years ago. Updated over 16 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Allow users to edit party records that they are the owner of, i.e. they (the
user) are the same as the party (link via user database that identifies which
party.party_ID they are) that owns this record (party.owner).

all changes should be added to the revisions table.

Furthermore, split from bug 852:
------------------(bug 852, comment 4)---------
from Bob:

1. There is the problem that there are party attributes that a user needs
to be able to update and which are not on the profile page that the user
edits. This should be added.

That is, the party table has attributes not on the "edit profile" form. We need
to either add these fields to that form, or we need to make a new form for
people to edit any party that they are the owner of.

------------------(bug 852, comment 6)---------
We need some business rules here. Ownership is by a registered user. We
currently track registered users as unique by email address. We do not
require email for a party (we do not always know an email). How do we link
registered users with parties? And, how do we affect the transfer of
ownership from a second-party creator to a registered user who wants to take
over his own party?

I suggest:

1. We move to primary key as the unique identifier for a registered user so
that email is no longer the unique identifier. Upon logging in the registered
user should be able to edit his/her email address, just like other user

[MTL - I like the idea of allowing users to change their email, provided the
email address they specify is not already on the system. Email would still be
the logon]

2. A new user when registering will create a new party by default. That user
can then send an email to the system manager requesting that one or more
extant parties be synonymized with the new party just created. This would
require that the manager reset part[y]:currentName_ID to point at the user’s
party record. This also suggests a new function needed in the management

3. We remove or minimize the redundancy between the user registration table
and the party table. We don’t want name, organization, address, etc stored in
both places.

Related issues

Blocks VegBank - Bug #852: When register, link to party & then updateResolvedGabriel Farrell11/13/2002

Actions #1

Updated by Michael Lee over 16 years ago

users can edit their own party, currently, but not parties they have added. Nor can they submit revisions or updates to plots and other data. Such functionality is desired, though may be difficult to put together in a way that they can use (some kind of batch of updated, likely).

Actions #2

Updated by Redmine Admin almost 10 years ago

Original Bugzilla ID was 1073


Also available in: Atom PDF