tmheunis
commented
8 months ago Another data point: when I try to get the config of the created catalog after my edits to the config file, it gives the wrong result.
This is the config file that I edited and that I passed to the catalog-add command above:
cat data-cat/config.json | jq .
{
"catalog_name": "DataCat",
"logo_path": "",
"link_color": "#fba304",
"link_hover_color": "#af7714",
"social_links": {
"about": null,
"documentation": "https://docs.datalad.org/projects/catalog/en/latest/",
"github": "https://github.com/datalad/datalad-catalog",
"mastodon": "https://fosstodon.org/@datalad",
"x": "https://x.com/datalad"
},
"dataset_options": {
"include_metadata_export": true
},
"property_sources": {
"dataset": {
"dataset_id": {
"rule": "single",
"source": "stephan_manual"
},
"dataset_version": {
"rule": "single",
"source": "stephan_manual"
},
"type": {
"rule": "single",
"source": "stephan_manual"
},
"children": {
"rule": "merge",
"source": "any"
},
"name": {
"rule": "single",
"source": "stephan_manual"
},
"short_name": {},
"description": {
"rule": "priority",
"source": [
"stephan_manual",
"datacite_gin",
"bids_dataset"
]
},
"doi": {},
"url": {
"rule": "merge",
"source": "any"
},
"authors": {
"rule": "merge",
"source": "any"
},
"keywords": {
"rule": "merge",
"source": "any"
},
"license": {},
"funding": {
"rule": "merge",
"source": "any"
},
"publications": {
"rule": "merge",
"source": "any"
},
"subdatasets": {
"rule": "merge",
"source": "any"
},
"additional_display": {
"rule": "merge",
"source": "any"
},
"top_display": {
"rule": "merge",
"source": "any"
}
}
}
}and this is the result of a catalog-get:
datalad catalog-get -c data-cat config | jq .
/Users/theunis/virtualenvs/catalog/lib/python3.9/site-packages/urllib3/__init__.py:34: NotOpenSSLWarning: urllib3 v2 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with 'LibreSSL 2.8.3'. See: https://github.com/urllib3/urllib3/issues/3020
warnings.warn(
{
"catalog_name": "DataCat",
"logo_path": "",
"link_color": "#fba304",
"link_hover_color": "#af7714",
"social_links": {
"about": null,
"documentation": "https://docs.datalad.org/projects/catalog/en/latest/",
"github": "https://github.com/datalad/datalad-catalog",
"mastodon": "https://fosstodon.org/@datalad",
"x": "https://x.com/datalad"
},
"dataset_options": {
"include_metadata_export": true
},
"property_sources": {
"dataset": {
"dataset_id": {
"rule": "single",
"source": "metalad_core"
},
"dataset_version": {
"rule": "single",
"source": "metalad_core"
},
"type": {
"rule": "single",
"source": "metalad_core"
},
"children": {
"rule": "merge",
"source": "any"
},
"name": {
"rule": "single",
"source": "metalad_studyminimeta"
},
"short_name": {},
"description": {
"rule": "priority",
"source": [
"catalog_readme",
"metalad_studyminimeta",
"datacite_gin",
"bids_dataset"
]
},
"doi": {},
"url": {
"rule": "merge",
"source": "any"
},
"authors": {
"rule": "merge",
"source": "any"
},
"keywords": {
"rule": "merge",
"source": "any"
},
"license": {},
"funding": {
"rule": "merge",
"source": "any"
},
"publications": {
"rule": "merge",
"source": "any"
},
"subdatasets": {
"rule": "merge",
"source": "any"
},
"additional_display": {
"rule": "merge",
"source": "any"
},
"top_display": {
"rule": "merge",
"source": "any"
}
}
}
}It looks like catalog-get still retrieves the original default config from the package, and not the one that I expect it to, which is the one I edited.
jsheunis
I'm following the datacat tutorial and noticed that my locally generated catalog does not look the same as the one in the tutorial screenshots after adding metadata, see screenshot:
I looked at the config of the created catalog and it includes rules for metadata sources that seem like they are not applicable for the tutorial. E.g. the sources in the tutorial are:
but the config includes metadata source rules for
metalad_studyminimetaand other sources. It seems like the config might not be a good match for the toy dataset of the tutorial, and might be preventing the correct fields from rendering?I tried editing the config to include
stephan_manualas a source (priority or single) and then re-added the metadata, but this didn't change anything. Not in the catalog rendering nor in the catalog metadata itself. This is an example from the catalog metadata after adding it:So somehow the
nameand description fields are not set?Then I called catalog-add while explicitly passing the updated config file. This seems to work and the catalog renders correctly.
Also, the catalog metadata fields that were previously
nullnow have the actual correct value. I also noticed that there is a new (duplicate) config file inside themetadata/<added-dataset>folder in the catalog.