Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CH$LINK: clarification #304

Open
meowcat opened this issue Apr 26, 2021 · 5 comments
Open

CH$LINK: clarification #304

meowcat opened this issue Apr 26, 2021 · 5 comments

Comments

@meowcat
Copy link
Contributor

meowcat commented Apr 26, 2021

Hi,

in the record format, it is not clearly specified how to handle potential multiple entries for one CH$LINK: DATABASE, e.g. a link to multiple CAS numbers. Can they be added as multiple entries and/or as space-separated entries? I think both would pass the validator. I think the former would be better.

https://github.com/MassBank/MassBank-web/blob/main/Documentation/MassBankRecordFormat.md#228-chlink-subtag-identifier

@schymane
Copy link
Member

I would be pro multiple entries ... but ... there's only one CAS number per structure technically ... and the others are "alternative forms". So strictly correct would be to only report the CAS matching by InChIKey ... but .. the standards used are often the salt form which is a different CAS. Do we have to "comment" these differences somehow? (or should we introduce the ability to do so?)

Just some examples (I've also seen "related CAS" used)

https://pubchem.ncbi.nlm.nih.gov/compound/2256#section=Other-Identifiers

https://comptox.epa.gov/dashboard/dsstoxdb/results?search=DTXSID9020112#synonyms

@tsufz
Copy link
Member

tsufz commented Apr 26, 2021

@schymane and @meowcat,
I suggest that you develop a proposal for the MassBank meeting. I would like to go ahead with the preferred MassBank name anyway and other standardization issues can be part of this implementation.

@meowcat
Copy link
Contributor Author

meowcat commented Apr 26, 2021

The purpose I want to use this for is not actually CAS but a linking system I am working on for (currently) internal use (see #303); CAS was just an example to make clear that this case is not specified.

@meowcat
Copy link
Contributor Author

meowcat commented Apr 26, 2021

(I've also seen "related CAS" used)

I think that's what NIST does IIRC?

@schymane
Copy link
Member

I thought ChemSpider and some of the other DBs too but could not find quickly ... maybe I picked a bad example in atrazine ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants