Closed adborden closed 3 years ago
Also maybe worth noting this feature is included in the plugin spatial_harvest_metadata_api
which we are including
For testing locally I was using the harvest source 2016-kml-cd114-20
and dataset /dataset/2015-cartographic-boundary-file-state-congressional-district-for-united-states-1-20000000
because the example used in the issue is from the DOI source which is too large to harvest locally
Also maybe worth noting that the dataset in question on old catalog when you load the url without the /html
it is in xml format while the same dataset in catalog-next without the `/html' is loading in json format
@thejuliekramer you're seeing a bug (missing feature) https://github.com/GSA/datagov-deploy/issues/2462. It should be XML in this case, but don't worry too much about that for this bug.
Possible fix is to fix and push code upstream that was originally fixed in our old fork of ckanext-harvest here https://github.com/GSA/ckanext-harvest/commit/84ae3f9f8959eee31394367581653fb9aee26c8b#.
Closing as duplicate of #2462
How to reproduce
Expected behavior
The HTML view of the source metadata is rendered.
See catalog-classic for similar behavior.
Actual behavior
500, server error.