Background: Currently, the classifier analyzes the daily PubMed updates and identifies those containing pathway/interaction information. This information is persisted in a database (RethinkDB). Consequently, this data represents a continuous 'feed' of (some of the) pathway/interaction information added to the literature.
Problem/opportunity: Being stored in a database, it is rather difficult and cumbersome to access (need to dump, restore elsewhere; data is in a particular database/table). This information just as easily be offered as a customizable web feed.
Background: Currently, the classifier analyzes the daily PubMed updates and identifies those containing pathway/interaction information. This information is persisted in a database (RethinkDB). Consequently, this data represents a continuous 'feed' of (some of the) pathway/interaction information added to the literature.
Problem/opportunity: Being stored in a database, it is rather difficult and cumbersome to access (need to dump, restore elsewhere; data is in a particular database/table). This information just as easily be offered as a customizable web feed.
Details: Design-wise, it makes most sense to provide the web service on top of this code, to abstract away the details of the database.