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 24, 2019. It is now read-only.
SwissProt namespace concepts from resource-generator's RDF dataset reference primary and secondary accessions through the dcterms:identifier predicate.
For example look at the primary accession Q7Z5M8. This record has multiple secondary accession identifiers.
All primary and secondary identifiers for that record will correctly find Q7Z5M8, but the returned identifier field is incorrect. The API is expecting to return a single identifier, but when a resource has multiple it will pick the last one.
The identifier should be fixed such that the identifier field always holds the primary accession when resolving by primary or secondary. This should be possible by following the dcterms:replaces predicate upstream.
Going further we could also link secondary identifiers to the SKOS concepts if they are available.
The text was updated successfully, but these errors were encountered:
SwissProt namespace concepts from resource-generator's RDF dataset reference primary and secondary accessions through the
dcterms:identifier
predicate.For example look at the primary accession Q7Z5M8. This record has multiple secondary accession identifiers.
All primary and secondary identifiers for that record will correctly find Q7Z5M8, but the returned identifier field is incorrect. The API is expecting to return a single identifier, but when a resource has multiple it will pick the last one.
The identifier should be fixed such that the identifier field always holds the primary accession when resolving by primary or secondary. This should be possible by following the
dcterms:replaces
predicate upstream.Going further we could also link secondary identifiers to the SKOS concepts if they are available.
The text was updated successfully, but these errors were encountered: