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
Hi, in the bioschemas records we have a number of places for all sorts of "identifiers". They need to be specified, documented and possible updated in the schema output:
identifier for a MolecularEntity would be the InChIkey, except if that does not exist (R-groups!)
url points to the MassBank URL for both DataSet and MolecularEntity, so it'd be identical to @id above, except it does not have to be unique, so the # trick would not be required.
This will also be of interest to the harvesters, e,g, @bhavin2897
Would that work ? Yours, Steffen
The text was updated successfully, but these errors were encountered:
Hi, in the bioschemas records we have a number of places for all sorts of "identifiers". They need to be specified, documented and possible updated in the schema output:
@id
is the URL pointing to the actual web page this metadata points to, e.g. theDataSet
https://massbank.eu/MassBank/RecordDisplay?id=PB000123Since
@id
s on one page need to be unique, for theMolecularEntity
on that page we use the#
trick e.g. https://massbank.eu/MassBank/RecordDisplay?id=MSBNK-IPB_Halle-PB000123#FTVWIRXFELQLPI-ZDUSSCGKSA-NNote that tentative molecules with R groups will not have an InChIkey, there it'd degrade to https://massbank.eu/MassBank/RecordDisplay?id=MSBNK-IPB_Halle-PB000123#
identifier
for aDataSet
is recommended to be "CURIEs that can be resolved using Identifiers.org" e.g.massbank:MSBNK-IPB_Halle-PB000166
via https://identifiers.org/massbank:MSBNK-IPB_Halle-PB000166.identifier
for aMolecularEntity
would be the InChIkey, except if that does not exist (R-groups!)url
points to the MassBank URL for bothDataSet
andMolecularEntity
, so it'd be identical to@id
above, except it does not have to be unique, so the#
trick would not be required.This will also be of interest to the harvesters, e,g, @bhavin2897
Would that work ? Yours, Steffen
The text was updated successfully, but these errors were encountered: