Closed rombaum closed 1 month ago
@rombaum Roman, this is great! Thanks for sharing. I assume you are not using docker, but a completely customised fork of OLS/OxO right? Would you be able to describe a bit the kind of changes you did in the source code to enable your customised version?
Hi @matentzn Nico,
we created a fork in December 2018 and created an own docker. But I also tested it last week with the docker of OLS on my local machine. To run OLS just with an individual frontend you just have to change the following two files:
Next to this to small changes you could start to create your own frontend by duplicating the module 'ols-web'. So if there are any changed in the original code we only have to adapt the changed of our customized frontend module 'ols-web'.
Some highlights we did:
Independently from these frontend changes we also played a little bit around and updated some technologies inside of our OLS version:
edit: we created our fork in December 2018
Thank you so much for the detailed response! Very nice work!
This is the main instance from the TIB services. Next to the one from NFDI4Chem you could also found one for NFDI4ING
https://terminology.nfdi4ing.de/ts/
These three are using the same backend and using the parameter collection to identify the wished subset of ontologies in the TIB General.
Hi @matentzn ,
sadly I'm a little bit late with my response, but I would love to contribute how we would like to use OLS and OxO for our research for your overview.
SemLookP
The Semantic Lookup Platform SemLookP hosted by the ZB MED - Information Centre for Life Sciences should be used in the biomedical domain. We want to use the system as a backbone service for different other services. SemLookP should help us in the following task:
Our SemLookP services are accessible under:
One of our first use cases where we use SemLookP to show additional information for a concept is our COVID-19 preprint viewer preVIEW.
I hope the content fits the page. If you need anything else just contact me.
Best,
Roman