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
The current LDA documentation often has an example URIs for a compound, protein, or gene, but there is some use for more examples to give people an indication what database-style URIs they can use. The reference example from the IMS telcon today is the use of Wikipedia URLs for compounds.
The idea is to add the following text to the appropriate LDA documentation:
More example URIs are found [here].
The [here] could link to a page listing more examples. In reply to using a support.ops.org page, the suggestion was made to use a generated list. Such lists are already generated at two places:
But the production IMS is not public so it would not have the advantage of the first that it always be consistent (because it uses the exact same API version and thus data).
The text was updated successfully, but these errors were encountered:
The IMS link would have the advantage that no API keys are necessary. A disadvantage of both would be that the link is rather long to display in the documentation. Not sure if is is possible to only show "here" and make it an actual link on the doc page?
@danidi agreed... [here] should show visually just "here" and the hyperlink should be hidden. If that is technically possible needs to be explored. This was basically my question to @antonisloizou ... we'll figure that out. Possibly, we use a URL shortener :)
The current LDA documentation often has an example URIs for a compound, protein, or gene, but there is some use for more examples to give people an indication what database-style URIs they can use. The reference example from the IMS telcon today is the use of Wikipedia URLs for compounds.
The idea is to add the following text to the appropriate LDA documentation:
The [here] could link to a page listing more examples. In reply to using a support.ops.org page, the suggestion was made to use a generated list. Such lists are already generated at two places:
But the production IMS is not public so it would not have the advantage of the first that it always be consistent (because it uses the exact same API version and thus data).
The text was updated successfully, but these errors were encountered: