search

identifiers-org / identifiers-org.github.io

MIT License
8 stars 1 forks source link

incorrect Assembly link generated #175

Open toritris opened 2 years ago

toritris commented 2 years ago

This accession JAHGQF000000000 is accepted by identifiers.org, which gives this link: https://identifiers.org/assembly:JAHGQF000000000 . However, the link does not resolve. The same assembly also has the accession GCA_019321825.1, which identifiers.org also converts, but which does work: https://identifiers.org/assembly:GCA_019321825.1 . I’m unsure what the difference is between the two accessions, but it doesn’t matter. What’s important is that identifiers.org shouldn't recommend accessions that don’t work.

renatocjn commented 1 year ago

Hello, Could you explain what you mean by identifiers.org recommending the accession JAHGQF000000000?

toritris commented 1 year ago

Hi,

In the 'Resolution' tab, in the 'Resolve a Compact Identifier' field, input: 'assembly:JAHGQF000000000'

This succeeds and identifiers.org generates this link: https://identifiers.org/assembly:JAHGQF000000000

However, the generated link does not resolve.

renatocjn commented 1 year ago

Thank you for clearing things. I see what you mean. The LUI pattern does look too open for this namespace.

But it does seem that the JAHGQF000000000 ID is related to the GCA_019321825.1 ID as the NIH search bar for the assembly dataset directs us to it. From the network logs, it directs us via the link: https://www.ncbi.nlm.nih.gov/assembly/?term=JAHGQF000000000. Maybe we should use a URL pattern for that instead.

I will try to clear things up with the NCBI team before making this change. Thank you for bringing this to our attention.