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
From Ben: "The main issue now and what stopped further progress on the website is the source data. I'm documenting a list of issues that we need to address. Here's an example: The Object ID column in the SSSOM mappings needs to be a URI to the term. Currently, the mappings files dont include the URIs. I can see why, given the SOM specification, but if we want to list them on the information elements page, then we need to add them. We need to standardize the mappings files as well."
The text was updated successfully, but these errors were encountered:
The mappings do include URIs for Object ID, but they're compact URIs (CURIEs). The namespaces are defined in the yml file. The MIDS namespace used for Subject ID obviously does not resolve at the moment and Subject Category needs to have a namespace as well. To integrate this into the website, either you'd need to hardcode support for the yml+csv SSSOM structure, or add a preprocessing script that replaces the namespaces in the csv files with the full paths from the yml. We need the CURIE terms and their full URLs, the former to show on the page and the latter to set as hyperlink.
From Ben: "The main issue now and what stopped further progress on the website is the source data. I'm documenting a list of issues that we need to address. Here's an example: The Object ID column in the SSSOM mappings needs to be a URI to the term. Currently, the mappings files dont include the URIs. I can see why, given the SOM specification, but if we want to list them on the information elements page, then we need to add them. We need to standardize the mappings files as well."
The text was updated successfully, but these errors were encountered: