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
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.
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
Unfortunately not, it's still to be fixed.
If you go to Configure DCAT and click the Preview tab, what's the license link it shows there?
John Plunkett
Hi … has this been resolved now?
I have a similar issue with HUB
https://www.arcgis.com/home/item.html?id=e8505fbd61e642a088df2eb58deccd7d - My AGOL item
my test HUB item
Bedrock Geology 1:100,000 Ireland ITM Feature Service and this returns a 404 for the license.json. Without this I cannot get CKAN (externally) to harvest with a star rating since it cannot find the licencing reference.
https://gsidcat-dcenr.hub.arcgis.com/datasets/e8505fbd61e642a088df2eb58deccd7d_0/license.json
Any ideas please .. I'm losing direction with this now I have tried so many things.
Regards
Hi Nick,
Not sure where the wires got crossed, but the bug you link has to do with formatting changes in the data.json site when shared publicly and I'm not seeing anything about license.json in the ticket. That said, we're seeing that license.json endpoints are 404ing for all sites and are currently working on a fix. Sorry for the confusion on this one.
Best,
Patrick
we'll take a look!
Esri has responded to the bug report:
BUG-000124770: The DCAT attributes for a ArcGIS Hub site's data.jso..
ArcGIS Hub does not support DCAT for private sites. As user report that this is new behavior, perhaps a bug was recently fixed in which, Hub previously exposed the …/data.json endpoint for private sites when it should not have been doing that in the first place. Also, looking at the DCAT configuration for the public site referred to in the bug report, the email address points to a field that does not exist (in the metadata for the item). If the user wants that to be valid, ensure the metadata for the item actually contains that field. We would be willing to work with user to see what is exactly going on in their particular configuration or scenario.
Private sites?
I have no idea what the technician is talking about. Any ideas?
Thanks Nick. I've logged it with our local Esri vendor, who have raised it with Esri. Hopefully it gets some traction!
This is a known bug. I submitted the bug report back in August!
Perhaps you could escalate this bug with Esri Support to help with expediting a fix.
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
