Stefan Korn

Please see PR #4055 for an idea how to handle this differently without creating a new distribution (or other embedded elements) every tme.

@dafeder : Thanks for the explanation. What do you mean by > One question is, should distributions be referenced at all? Maybe they don't need to be, and we could...

@dafeder : Coming back to your explanations on distribution I would like to know if you prefer (in the long term) to get rid of any "Dataset properties to be...

@dafeder : Thanks for your reply. We are now relying in some cases on "Dataset properties to be stored as separate entities", so hopefully you will not remove this feature...

@dafeder : I am coming back to this regarding publisher once again (sorry did not manage to get around this earlier) We are using a publisher as a reference in...

> @stefan-korn can you clarify the workflow here? I would think that you could > > 1. Create a dataset and indirectly create a publisher node by using the autocomplete...

@dafeder : I used the default schema coming with https://github.com/GetDKAN/dkan/tree/2.x/schema/collections now. Is the problem maybe that the Referencer is checking for the node by the title property of the reference,...

@dafeder : Not so easy it seems. When directly editing a publisher node it seems we do not get to updateExistingEntity. Currently I am asking myself in what case we...

@dafeder I use this code in custom module now: ``` function custom_module_node_presave(\Drupal\node\NodeInterface $entity) { if ($entity->bundle() === 'data' && $entity->hasField('field_data_type') && !$entity->get('field_data_type')->isEmpty() && $entity->get('field_data_type')->value !== 'dataset' ) { if ($entity->hasField('field_json_metadata')...

@janette : Thanks, change makes sense.