VegBank

This was done fall 2002.

• Bug 825 has been marked as a duplicate of this bug. ***

Need to make sure that certification documents are emailed to the appropriate
parties when someone requests certification. This list of parties probably
should be an XML doc somewhere so that we could change easily who will get the
emails.

additionally, all fields that are public in the certification form need to be
editable from the "edit profile" page :
framework/servlet/usermanagement?action=changeusersettings

profile database (framework) does not need revision for the Nov1 milestone.
Certification just needs to work. AFter ceritifcation fucntionality works, put
this bug in the 2.0 bucket.

If a user is not logged in, fills out entire form, submits, message says, "log
in" and the form data is lost. Bad news for user.

Also, "What do the levels mean?" link is broken.

Also, since only logged in users can apply for cert, we don't need the email
address to be entered, or at least we can auto populate it.

Mark, your comments above I agree with. The "what do these levels mean" link is
perhaps being screwed up my renegade javascripts elsewhere in the page, ie
footer and header. This wasn't a good idea on my part and I will be removing
them. We can find another way of linking someone to context sensitive help.

• Bug 836 has been marked as a duplicate of this bug. ***

Mark, I'll take this bug for now, with focus on model change implications.
Sounds like the certification email is working better now- just need to get the
from: address sorted out.

more info, akin to data-dictionary on its way

I see no problems with the ERD id=89 particularily in relation to user,
certification, userPermissions and embargo, userDataset and datasetObs tables.

Supporting the userQuery, recordOwnership, partyMember and userNotify are over
my horizon for now but the model looks good.

I am concerned about the SQL queries stored in the userNotity and userQuery as
there may be a more abstract way to do this that would be more robust to model
and system changes, what that way might be is unclear to me so its a moot point
for now.

Also we currently have no way to persist user preferences we may want to add
another table(s) later to support this. This can be ignored for now in the
interest of finalizing this good work and getting it in place.

Once again changing the nature and summary of this bug. Here is the task of
making the website work with the correct, new tables inside vegbank, not in
framework. Certification, authentication, log-in, etc. all need to now read
through the new tables, which are presumably populated and happy in vegbank.

New user system works great now!

changed from components that are to be deleted to "misc" so that bugs don't get
deleted with component. Sorry for all the email.

Original Bugzilla ID was 824