You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clone the url field to the field includedInDataCatalog.dataset
Issue Description
Upon merging identical records from two different repositories, the url field is merged. This results in the front-end being unable to send the user to the appropriate record in each repository. In other words, one of the two unique url fields is lost.
This will be increasingly problematic as more repositories look for their data. In a merged case, one of the two repos may be offput by the loss of the link to their site.
To address this, the parsers/crawlers should copy/save the url field value to the includedInDataCatalog object. This object has a field (dataset) in the schema specifically for this purpose. The dataset property is inherited from schema.org, thus it will be dataset regardless of the actual record type (i.e. ComputationalTool, ResourceCatalog will still use includedInDataCatalog.dataset). We'll just have to be more accurate about its display on the front end.
Note, if this can be done post-build, that's fine too.
Issue Name
Clone the
url
field to the fieldincludedInDataCatalog.dataset
Issue Description
Upon merging identical records from two different repositories, the
url
field is merged. This results in the front-end being unable to send the user to the appropriate record in each repository. In other words, one of the two unique url fields is lost.This will be increasingly problematic as more repositories look for their data. In a merged case, one of the two repos may be offput by the loss of the link to their site.
To address this, the parsers/crawlers should copy/save the
url
field value to theincludedInDataCatalog
object. This object has a field (dataset
) in the schema specifically for this purpose. Thedataset
property is inherited from schema.org, thus it will bedataset
regardless of the actual record type (i.e. ComputationalTool, ResourceCatalog will still useincludedInDataCatalog.dataset
). We'll just have to be more accurate about its display on the front end.Note, if this can be done post-build, that's fine too.
Issue Example
https://data.niaid.nih.gov/resources?id=gse143393
![Image](https://private-user-images.githubusercontent.com/9200138/406536419-bc108bd3-e4a0-44f7-b91c-00b0fc4c2e01.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1NDg2NjcsIm5iZiI6MTczOTU0ODM2NywicGF0aCI6Ii85MjAwMTM4LzQwNjUzNjQxOS1iYzEwOGJkMy1lNGEwLTQ0ZjctYjkxYy0wMGIwZmM0YzJlMDEucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTRUMTU1MjQ3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDM3ZGM5NDI3NTY1MWQzZDMxNzJiOWE4MTRkOGM2MGRkYmVhMGFkMzNjZWIzYjk0MGQxMTZlYjU4N2JhYzkwZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.hNNLq0RnQj7ftHWnRGpAzxxHspjM4CTJF478G-n8vuo)
Related WBS task
https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/14
For internal use only. Assignee, please select the status of this issue
Status Description
No response
The text was updated successfully, but these errors were encountered: