Overwriting activities when duplicating to database where activity already exists.

[marc-vdm]

New feature suggestion:

When duplicating an activity to a database, AB should check whether an activity with that product, activity, location and unit field already exists, if that is the case, AB should offer two options 1) 'overwrite' the activity (replacing the old activity, and re-linking any exchanges, if required) 2) the standard, just adding the activity to the database, which happens currently.

This way, certain processes could be exchanged from a database where perhaps sharing the entire database could violate licensing or confidentiality agreements would not be allowed. Then others could import the process and duplicate it into the relevant database.

A usecase could be where someone would share altered processes for an ecoinvent database (for background scenarios), and would just send the altered processes, which could then be put into the ecoinvent database for the other user.