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
{{ message }}
This repository has been archived by the owner on Sep 19, 2023. It is now read-only.
ua-nsdc-person-176-2018-213: no link, not sure this source has individual pags
NK-33dvfMLd6hCdByWC8Gjntp: no link, not sure which this source is
Also, it'll be much neater if you show the links right into the respective "Data sources" and "External databases" blocks.
When I'm researching about Bushuev, I want to see a link to his "Ukraine NABC Sanctions Tracker" page, and the count of entries in that list (7452) is less important for me
The text was updated successfully, but these errors were encountered:
That's really cool feedback, I appreciate it. I need to have a think about how to process it, basically because it crosses some weird system boundary: datasets are traditionally outside of the FtM ontology. That's an artefact of it not being an RDF vocab, and the dataset boundaries doubling as authorisation contexts. So, strictly speaking, FtM entities just don't know what dataset they're in. It may be worth changing that at some point, especially because I buy the story about deep-linking the source URL, rather than having it as an array.
Wikidata
external-id
properties are resolved to direct links to external source pages, whenever possible.This is a great feature to allow people to do research amongst sources, and I think a similar thing should be on the OpenSanctions UI.
Take a look at https://www.opensanctions.org/entities/Q112194249/. It has a number of IDs, but only 1 leads to a page
Also, it'll be much neater if you show the links right into the respective "Data sources" and "External databases" blocks.
When I'm researching about Bushuev, I want to see a link to his "Ukraine NABC Sanctions Tracker" page, and the count of entries in that list (7452) is less important for me
The text was updated successfully, but these errors were encountered: