Why do activity UUIDs differ after importing the same ecoinvent version and system model into openLCA?

Question

Hi,

our team is building an automated matching pipeline between our BOM data and ecoinvent datasets.
For this purpose, we use the Activity UUID from ecoinvent Database as the unique identifier.
However, we noticed that the UUID in openLCA is different, although the ecoinvent version, system model, activity name, and geography appear to be the same.

My questions are

1. Why does the UUID change when the ecoinvent dataset is imported into openLCA?

2. Does openLCA generate its own UUID during the ecoinvent conversion/import?

3. Is there another original ecoinvent identifier preserved somewhere in the openLCA dataset?

Answer 1

interesting ->

1 ecoinvent's UUIDs are not consistent, e.g. for allocated datasets they may refer to the version prior to the allocation, etc.

2 because of 1

3 yes, in flows as a comment, and in the process if you follow the link to the ecoquery.

However, because of 1,  the original ecoinvent UUIDs we find are not too practical, but certainly useful as a reference. Good luck!