DCAT feed URLs return 404

[Anonymous User]

The DCAT feed for our Open Data site returns urls which currently throw a 404 error. I've looked at a few sites' DCAT data links and they're also throwing a 404 error. Our site is https://data-transpower.opendata.arcgis.com/ and the DCAT feed lists license urls like http://data-transpower.opendata.arcgis.com/datasets/0e8f361371914a6f95133f58d34ffcb9_0/license.json which are throwing a 404 error. On the DCAT Feed preview page (see attachment) the links point to http://opendata.arcgis.com/... which works e.g. https://opendata.arcgis.com/datasets/0e8f361371914a6f95133f58d34ffcb9_0/license.json 

[Department_of_Communications__]

Hi Mark, Thanks for the reply, your post prompted me to take a closer look and basically mine was exactly like yours.

Here is the before and after version (post a bit of fiddling)

• Before

"@type": "dcat:Catalog",
"conformsTo": "https://project-open-data.cio.gov/v1.1/schema",
"describedBy": "https://project-open-data.cio.gov/v1.1/schema/catalog.json",
"dataset": [
{
"@type": "dcat:Dataset",
"identifier": "http://opendata.arcgis.com/datasets/7e95eba45eb24855aa320c10e5c4b349_0",
"license": "http://opendata.arcgis.com/datasets/7e95eba45eb24855aa320c10e5c4b349_0/license.json",
"landingPage": "http://opendata.arcgis.com/datasets/7e95eba45eb24855aa320c10e5c4b349_0",
"title": "LOADME",
"description": "{{default.description}}",
"keyword": [
"DCAT_TEST"

• After

{
"@context": "https://project-open-data.cio.gov/v1.1/schema/catalog.jsonld",
"@type": "dcat:Catalog",
"conformsTo": "https://project-open-data.cio.gov/v1.1/schema",
"describedBy": "https://project-open-data.cio.gov/v1.1/schema/catalog.json",
"dataset": [
{
"@type": "dcat:Dataset",
"identifier": "http://opendata.arcgis.com/datasets/7e95eba45eb24855aa320c10e5c4b349_0",
"license": "https://creativecommons.org/licenses/by/4.0/",
"landingPage": "http://opendata.arcgis.com/datasets/7e95eba45eb24855aa320c10e5c4b349_0",
"title": "LOADME",
"description": "{{default.description}}",
"keyword": [
"DCAT_TEST"
],
"issued": "2020-05-29T10:25:21.000Z",

So I now know I can change the content of the DCAT and for this particular example I just hard coded it with a url as for the moment but I also got it working with the dcat elements that popup on the righthand side when your editing (excuse the terminology I couldn't find and help or direction on this)

I just added one line into the DCAT configuration (bold below) but it can be dynamic using the metadata item 

{
"title": "{{default.name}}",
"description": "{{default.description}}",
"keyword": "{{item.tags}}",
"issued": "{{item.created:toISO}}",
"modified": "{{item.modified:toISO}}",
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"source": "{{default.source.source}}"
},
"contactPoint": {
"hasEmail": "{{metadata.metadata.mdContact.rpCntInfo.cntAddress.eMailAdd}}",
"mbox": "info@gsi.ie"
}
}

So for the moment it works ... I just have to better understand the whole configuration aspect.  Thanks for the post  

Paulg

[Anonymous User]

Hi Paulg,

Yes, you can manually configure the DCAT based on DCAT attributes or just hard code it. It's just not so useful when you have mixed license content.

You could try "license": "{{item.licenseInfo}}" instead of hardcoding it. I would change our one to that setting, but the agency that reads our DCAT expects it as a url, pointing to a json file, so it doesn't work for them.

[jonathanharte]

Hi Mark,

Yes your correct … I need the license.json response also,  my excitement cloudy my judgement 🙂 

I feel its time to log a support call.

Thanks for taking the time to respond

Paulg

[ThomasHervey1]

Hi jonathan harte‌ we have work schedule to fix the license.json endpoint. The DCAT editor is about to get an update and so this bug will be investigated during the process.

[Anonymous User]

Thomas Hervey any update on this? The Hub change log mentions the DCAT editor has been updated (which I've seen in the product) but the license.json endpoint hasn't changed.

[ThomasHervey1]

Thanks for checking back. This was not fixed during the UI updates that went out. There is work scheduled for this week fix several DCAT issues including correcting 404s for license endpoints and update the links to HTTPS.

[ThomasHervey1]

The 404 on license endpoints has not yet been corrected. I apologize for the delay and inconvenience. We currently do not generate licenses to populate this endpoint, but we're looking forward to work within the next few months to build a license picker, allowing users to set reuse licenses on content. This 404 issue will be corrected then.

For additional context, Hub is also looking to expand and support other catalogs like DCAT-AP. The initial work for during expansion involves a critical look at Hub's DCAT template and will attempt to resolve any other outstanding issues.