Unable to set the cod_level key

[cjhendrix]

******************************************
* HDX CLI toolkit - Update               *
* Invoked at: 2024-12-17T08:04:37.757588 *
******************************************
hdx_stage_site
Found 1 datasets for organization 'OCHA Field Information Services Section (FISS) (ocha-fiss)' matching filter conditions:
Updating key 'cod_level' with value 'cod-standard'
Type name '' is not recognised, aborting

From IH: "It looks like the issue is in the understanding the data type of the cod_level value. I notice that the cod_level key is not in the JSON which you can download from the dataset page but is in the package_show response. My suspicion is that this is a "special" key."

Also please consider if it is possible to unset the key.

[IanHopkinson]

The issue here is that because the cod_level does not exist on the dataset we are unable to infer the correct type for it which is the what the error message on the final line is telling us.

There are two workarounds for this:

1. We could maintain a list of types for dataset attributes
2. We could allow users to supply the type for the attributes

I don't think we can provide all attributes as strings and let HDX/CKAN do any required type conversion

Providing the output from the toolkit for an issue is really useful, it would be handy to also provide the command which generated the output for testing purposes.

[cjhendrix]

I wonder how many other properties like that we have on a dataset? If there are others, then option 1 might make sense. However if this is the only one, and we already have code for modifying those values when we need to, then it's probably not worth the effort. Maybe @dan Gheorghe ***@***.***> or @alexandru ***@***.***> would have some opinions?

…

________________________________ From: Ian Hopkinson ***@***.***> Sent: Saturday, January 25, 2025 12:02 To: OCHA-DAP/hdx-cli-toolkit ***@***.***> Cc: Chad Hendrix ***@***.***>; Author ***@***.***> Subject: Re: [OCHA-DAP/hdx-cli-toolkit] Unable to set the cod_level key (Issue #47) The issue here is that because the cod_level does not exist on the dataset we are unable to infer the correct type for it which is the what the error message on the final line is telling us. There are two workarounds for this: 1. We could maintain a list of types for dataset attributes 2. We could allow users to supply the type for the attributes — Reply to this email directly, view it on GitHub<#47 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAMT5VKITHA2HVJSRMQFDP32MNVLJAVCNFSM6AAAAABTXYM4UCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTHEZDQMRWGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>