Opened 13 years ago

Last modified 13 years ago

#154 new enhancement

Use membership confirmation process to correct values in the DB

Reported by: adehnert Owned by:
Priority: normal Milestone: Fall 2013
Component: Membership confirmation Version:
Keywords: Cc:
Size: medium

Description

We know that our values for a number of fields are not what we wish they were --- for example, many officers' lists are the president's email address, rather than something that will remain constant from year to year and avoids a SPOF. Similarly, we expect the membership numbers in a group's DB entry to tend to get out of date. The group registration form asks for both these kinds of data, so it could either automatically save answers into the group entry, or warn you when the answers are inconsistent and give you a chance to decide to change one or the other.

Change History (3)

comment:1 Changed 13 years ago by adehnert

  • Milestone changed from Sometime to Fall 2012

comment:2 Changed 13 years ago by adehnert

Conclusion: this isn't happening this year. It's probably still useful in the future, since groups do change size or (less often) mailing lists and fail to inform us.

I suspect we want to show the mismatch warning and "copy from DB entry"/"copy to DB entry"/"ignore" only if a mismatch occurs. It's not clear how to cleanly add a field to the form / otherwise handle this that late in the form processing, though.

ValidationWarning (​https://code.djangoproject.com/ticket/23) could be useful if it ever happens, though it isn't looking stunningly likely... :(

comment:3 Changed 13 years ago by adehnert

  • Milestone changed from Fall 2012 to Fall 2013
Note: See TracTickets for help on using tickets.