Project

General

Profile

Actions

Bug #720

open

Party Perspective Managment (plant/comm):General interface to allow

Added by Michael Lee about 20 years ago. Updated over 16 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
userAlter
Target version:
Start date:
11/13/2002
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
720

Description

Implement new correlation form


Related issues

Is duplicate of VegBank - Bug #716: Mechanism to add new plants:Insert business rulesResolvedMichael Lee11/13/2002

Actions
Is duplicate of VegBank - Bug #719: manage plants you ownResolvedMichael Lee11/13/2002

Actions
Is duplicate of VegBank - Bug #721: [360] Mechanism to add new plants:correlations-aResolvedMichael Lee11/13/2002

Actions
Is duplicate of VegBank - Bug #733: Mechanism to add new communities:Bulk input of communities & taxaResolvedMichael Lee11/13/2002

Actions
Actions #1

Updated by John Harris about 20 years ago

Currently a user can, via the website, correlate their communities with an NVC,
this same sort of action should be carried out in the plant taxonomy module.

Actions #2

Updated by Michael Lee about 19 years ago

  • Bug 721 has been marked as a duplicate of this bug. ***
Actions #3

Updated by Michael Lee almost 18 years ago

correlate, etc.

Actions #4

Updated by Michael Lee almost 18 years ago

  • Bug 719 has been marked as a duplicate of this bug. ***
Actions #5

Updated by Michael Lee almost 18 years ago

  • Bug 716 has been marked as a duplicate of this bug. ***
Actions #6

Updated by Michael Lee almost 18 years ago

  • Bug 733 has been marked as a duplicate of this bug. ***
Actions #7

Updated by Michael Lee almost 18 years ago

allow bulk imports

Actions #8

Updated by Michael Lee over 16 years ago

This deals with plantStatus and commStatus records primarily, and the related plantCorrelation, plantUsage, commCorrelation, commUsage tables.

users may change their mind about the status of elements and we should provide tools for them to explain that in our system and update their opinion. The XML loader is now smart enough to add new statuses if a user puts them into an XML stream, but it isn't smart enough to end old statuses yet, that the user would either put into the stream or say that the old ones should automatically be ended when the new ones start (could be denorm sql).

Actions #9

Updated by Redmine Admin almost 10 years ago

Original Bugzilla ID was 720

Actions

Also available in: Atom PDF