[ckan-dev] Problem with custom fields only new datasets

Mon Jul 7 07:55:10 UTC 2014

Hi,

I can confirm that the problem lies in the names of the fields. If I change
my field names from for example "attribute_description" to
"zattribute_description" they are saved correctly. Unfortunately, thats no
ultimate workaround for the problem in my case, because I have to use
certain field names to fulfill our local "OGD Austria Metadatastandard".

I have opened a new issue at github:
https://github.com/ckan/ckan/issues/1833

Thanks for the help!

Michael

2014-07-04 14:37 GMT+02:00 Ian Ward <ian at excess.org>:

> This does seem similar to the issue I ran into some time ago. All of
> your fields names that sort before 'maintainer_email' don't work on
> the third stage of dataset creation.
>
> I remember stepping around in
> ckan.lib.navl.dictization_function._validate to figure out what was
> going on with the problem I ran into. My old issue was
> https://github.com/ckan/ckan/issues/621
>
> Why don't you create a new issue on github so we can track this?
>
> On Fri, Jul 4, 2014 at 8:06 AM, Michael Reichart
> <michael.reichart at gmail.com> wrote:
> > I'm listing all the fields in the order of package_metadata_fields.html:
> >
> > schema_name   -> works
> > schema_language   -> works
> > schema_characterset   -> works
> > metadata_linkage   -> works
> > attribute_description   -> doesn't work
> > geographic_toponym   -> doesn't work
> > geographic_bbox   -> doesn't work
> > update_frequency   -> works
> > lineage_quality   -> doesn't work
> > en_title_and_desc   -> doesn't work
> > license_citation   -> doesn't work
> > metadata_original_portal   -> works
> > maintainer_email   -> works
> >
> > Thanks
> >
> > Michael
> >
> >
> > 2014-07-04 12:53 GMT+02:00 Ian Ward <ian at excess.org>:
> >>
> >>
> >> On 4 Jul 2014 01:52, "Michael Reichart" <michael.reichart at gmail.com>
> >> wrote:
> >> >
> >> > No I'm not using the standard "extra fields" only the custom fields
> ...
> >> >
> >> >
> >> > You can see the form here:
> >> >
> >> >
> https://github.com/OpenDataPortal-AT/ckanext-odpat-form/blob/master/ckanext/odpat_form/templates/package/snippets/package_metadata_fields.html#L25
> >> >
> >> > The field "attribute_description" is one of the fields that doesn't
> >> > work, the field "metadata_linkage" right above works ...
> >>
> >> Which fields work and which fields don't on that page? We did have a bug
> >> where field names that sorted before a certain string weren't being
> saved,
> >> but that should have been fixed in 2.1.
> >>
> >>
> >> _______________________________________________
> >> 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
> >>
> >
> >
> > _______________________________________________
> > 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
> >
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140707/c7e63591/attachment-0003.html>