Party entry and edit -- design / evaluate /connect and implement form
#3 Updated by Michael Lee over 19 years ago
This is a more commonly used bit of data that users will want to add outside of
a plot. Also somewhat simple in implementation -- simple form linked to one or
two tables. (A bit more for community -- but this functionality is quite
central to what we're working on.)
#6 Updated by Robert Peet over 19 years ago
Comments on the draft new “Party Form”
Make field names closer to real English rather than being exactly equal to the
field names. Capitalize each.
salutation --> Salutation
givenName --> First name
middleName --> Middle name/initial
surname --> Last name
organizationName --> Organization
contactInstructions --> Contact Instructions
Make similar changes for the other fields.
Remove the option for owner. The owner is the registered user who creates the
party until the system administrator changes this.
Of course, Gabe will need to implement the permissions function that restricts
editing to the owner.
Let’s not require phone number
The line immediately after the add button needs some rewriting.
The click here for data dictionary is confusing because the user is not
directed to a specific table, and it is less than intuitive that three tables
must be examined. I suppose we should list all three and provide hotlinks to
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?
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
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: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
#8 Updated by Michael Lee over 19 years ago
Is now the new form that has renamed field labels, more explanations, hot-links
to datadictionary fields.
The other comments from Bob deal with a different bug, so I will copy them and
add them to bug 852. Starting with "We need some business rules here:"
If the form is good as is, then this bug should be passed to gabe for
#10 Updated by Michael Lee over 19 years ago
Alternate identifier type ? Is this the system? This is not a closed list, but
rather a system URL that the user owns that can uniquely identify the system
(always). See the data dictionary:
Identifier is also not a closed list, as the user will select any name they want
Am I missing something? If it's good as is, then it should be passed to gabe
#11 Updated by Robert Peet over 19 years ago
Not sure what notes 8 & 9 refer to. ALternative identifier comments probably
pertain to the reference form rather than the party form, and in that case I
agree with Mike's assessment as to how they work, but there is still a
compelling need for the user of the reference form to be able to select from
alternatiav identifier types already in the system (or to add a new one).
Mike, perhaps you can shift this note over to the reference form bug, and then
forward the party form to Gabe for implementation.