Konstantin Sivakov

https://github.com/ckan/ckan/pull/5088

@wardi i was checking an option to use [`signals`](https://github.com/ckan/ckan/blob/master/ckan/lib/signals.py#L49) and having something like `resource_reorder` signal that would be used as check if we need to update the `metadata_modified` when `package_update`...

@TkTech @smotornyuk Hey guys, whats the status of this PR, it would be great if this get merged soon

Thanks @smotornyuk Maybe @TomeCirun or me could try to do that in separate PR

@TkTech what about transfering the extension under CKAN org ? cc @amercader @wardi

@wardi thanks for the ValidatorFactory tip, now we can get the plugins name.

So i will need some suggestion about the naming of the `plugin_data` I considered few options as `plugin_fields`, `extra fileds`, `custom_data` but im not sure if those can be explainatory...

For the option to keep the data in one column, when we will have multiple extensions implementing this interface, we would endup having following structure ```json "plugin_data": { "example_plugin1": {...

@wardi ive followed the other `extras` implementations.

Some time ago i tried Adapter approach, with initial idea of having CkanSearch interface but in that case any other engine support should be added as extension and all the...