For the EF database, you should not link anything automatically since they are agrgegated system processes so far (in the released version), which however have some input products sometimes. Linking these automatically does not make sense. For transport, there are unit processes, but they also should be linked manually.
We will release an EF3 version soon also because others have done it now too, we were waiting for a consistent set of EF3 LCI datasets.
Why if I look for some process in the LCDN nodes I frequently observe differences in respect to what is implemented in your DB?
Of course, if the process was created in a different software, our implementation could look differently. Do you have an example maybe?
Is there a way to adapt the EF3 method from JRC into your dataset? To avoid the use of the peflocus, EF converter and Look@LCI
Yes I agree this is a bit a hard pathway. You can do this also by other ways but as said we will also provide EF3 (data as far as available, and LCIA method) soon.
All the best,