- From: Martin Bailey <martin.bailey@gmail.com>
- Date: Mon, 4 Dec 2017 11:09:42 +0000
- To: Stephen Ficklin <stephen.ficklin@wsu.edu>, public-hydra@w3.org
- Message-ID: <CACOb-1MRH=RYYP3ZevrUY7KciQXTyZMy-g1bGHkCxbJ=jSypVA@mail.gmail.com>
Hi Stephen I am currently working on an software project that handles biomedical bibliographic data for systematic review. The input of this system is millions of bibliographic items, pubmed etc. The output of this system will be used to produce medical guidelines and recommendations. This is a project run by University College London, and in collaboration with the UK National Institute for Health and Care Excellence (NICE). We have previously built a system that unifies pubmed, ovid, proquest, embase, ontologies to the FaBiO bibliographic ontology, from the SPAR ontology suite. We created a single query languages to allow queries across these disparate databases using one standard syntax. We have a 3rd system that discovers the 'free text' information give some citation data, it can automatically order from the British Library if no free text is available. All of these systems use Hydra as there API vocabulary. We are now able to seamlessly link these systems, and make them available to other parties in the future. I have 3 years experience of using Hydra as an API vocabulary. We use the Hydra vocabulary as the internal view model structure of our application. All of these systems content negotiate both HTML and JSON by default. Since I am a keen advocate of REST, the adoption of Hydra, internally within the application domain, as been an invaluable way of standardizing and testing our code. We don't limit its use to just the output format of our systems, it is also used as a mechanism for enforcing the hypermedia constraint within our domain. I am keen to hook up with others in this community. If you consider any of this experience to be of use to you, please don't hesitate in getting back to me. Kind regards Martin On Thu, Aug 17, 2017 at 12:44 AM, Stephen Ficklin <stephen.ficklin@wsu.edu> wrote: > Hello Hydra Community! > > As suggested by Markus in a GitHub issue (https://github.com/lanthaler/ > HydraConsole/issues/26#issuecomment-313217684). I'm writing to introduce > a project we're working on that includes Hydra as the framework for our > API. The project is Tripal (http://tripal.info/). Tripal is an > open-source, freely available toolkit for construction of online biological > databases. Genomics is undergoing a massive increase in the quantity of > data available across all species. Often, researchers who generate this > type of data need a way to publish them in a searchable online website for > their research communities using common data standards. The Tripal project > is intended to decrease the barrier for wet-bench scientists to publish > their data, and to provide a common framework for development of groups > with more advanced IT folks. With multiple genome projects now using > Tripal from across the world we're working to make data in Tripal sites > exchangeable in a federated manner via web services using controlled > vocabularies. Our approach has been to choose Hydra for this. We are > funded by several US National Science Foundation (NSF) award to make this > happen. > > We'd love to be a bit more integrated with the Hydra community, and hope > there may be some interest in our project, and I'm happy to share further > details for anyone interested. > > Best, > > Stephen Ficklin, Ph.D. > Assistant Professor of Bioinformatics and Systems Genetics > Washington State University > > > >
Received on Monday, 4 December 2017 13:23:24 UTC