[ckan-dev] bug on metadata-created and metadata-modified fields

David Read david.read at hackneyworkshop.com
Wed Aug 16 09:30:41 UTC 2017


I think you're right - it would make sense for a harvest to take the
source metadata_modified/created values by default.

To code this I guess you'd get the ckan harvester to add an option to
the context (maybe 'override_metadata_created_and_modified'=True) so
that package_dict_save() knows not to delete these values. And yes
some playing about with the schemas. Perhaps you can work out a Pull


On 4 August 2017 at 09:29,  <aurelie.gole at orange.com> wrote:
> Hello
> We had noticed that the datasets harvested were not filled with the origin
> metadata-modified and metadata-created dates. (the ones which are in the
> sources before harvesting)
> We had found 2 python files at fault in ckan (shema.py and model_save.py)
> So we would like to know why it is the default behaviour of ckan.
> Thanks
> Regards
> Aurélie Golé
> _________________________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

More information about the ckan-dev mailing list