When I add a resource with the "Upload Document" feature, it maps to DataLink on the JSON. "Link Dataset" should be the only function to populate the "DataLink"
It would be useful to discuss this issue before you start work on it because this appears to be related to an old issue that hasn't properly been resolved (https://github.com/OpenWork-NZ/core-geonetwork/issues/76). Before everything mapped to DataDownload, and now everything is mapping to DataLink. Something to consider, what will happen when I link a publication URL? This is going to map to DataDownload, but it isn't data. As described in #76, the XML carries the identity of these different document/data types, but the JSON just carries them all as DataDownload. To me, it doesn't make sense to have a written publication mapping to DataDownload.
When I add a resource with the "Upload Document" feature, it maps to DataLink on the JSON. "Link Dataset" should be the only function to populate the "DataLink"
It would be useful to discuss this issue before you start work on it because this appears to be related to an old issue that hasn't properly been resolved (https://github.com/OpenWork-NZ/core-geonetwork/issues/76). Before everything mapped to DataDownload, and now everything is mapping to DataLink. Something to consider, what will happen when I link a publication URL? This is going to map to DataDownload, but it isn't data. As described in #76, the XML carries the identity of these different document/data types, but the JSON just carries them all as DataDownload. To me, it doesn't make sense to have a written publication mapping to DataDownload.
See: https://antcat.antarcticanz.govt.nz/geonetwork/srv/eng/catalog.search#/metadata/dc61cadc-9553-4e9c-83dc-bf65fabed1c9
Which ends up on the JSON's "DataLink" in this on the JSON, but should be going to DataDownload for this type of resource: https://antcat.antarcticanz.govt.nz/geonetwork/srv/api/records/dc61cadc-9553-4e9c-83dc-bf65fabed1c9/formatters/jsonld?approved=true