[ckan-dev] Independent plugins (two or more) which extends dataset metadata fields
Ladislav Nesnera
nesnera at email.cz
Fri Oct 6 03:17:35 UTC 2017
Not yet any suggestion :( OK. I'll try explain it in use case.
1) We have two CKAN instances. Internal for all datasets and external
with open datasets only. I need preserve information about tied dataset
couple. (syndicate extension
<https://github.com/aptivate/ckanext-syndicate>)
2) We use Redmine <http://www.redmine.org/> as a tool for managing tasks
(data preparing, publication process, ..). It requires bidirectional
information task <> dataset. (own extension)
3) Different functionality would be fine hold in different independent
extensions but booth need to write into the same datasets.
Is it possile? How to realize it?
;?
On 3.10.2017 02:28, Ladislav Nesnera wrote:
>
> Hi,
>
> I'd like to have two independent plugins which extends dataset
> metadata fields. I need to allow them separately or together.
> They could be derived from this example
> <https://github.com/ckan/ckan/blob/d73326ad4beb3743cb4a347b15c04dace8c8654b/ckanext/example_idatasetform/plugin.py>.
> I've tried it but I have no idea how to solve collisions is_fallback()
> and package_types() functions. Is it possible? Any suggestions?
>
> LN ;?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20171006/6c9fc261/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20171006/6c9fc261/attachment-0003.sig>
More information about the ckan-dev
mailing list