Skip to content

PathwayCommons/factoid

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Factoid

DOI License

Biofactoid (biofactoid.org), is a web-based system that empowers authors to capture and share machine-readable summaries of molecular-level interactions described in their publications.

Biofactoid's codebase is licensed under MIT.

Getting the data

All contributed pathway data is freely available for download at https://biofactoid.org/api/document/zip which contains files for each pathway represented in:

  • JavaScript Object Notation (JSON). This is the native format for Biofactoid data and contains interaction data, metadata of the record itself, metadata of the corresponding article, and visualisation data (layout and colors as Cytoscape JSON (Franz et al. (2016) Bioinforma. Oxf. Engl., 32, 309–311.)).
  • Biological Pathway Exchange (BioPAX) (Demir et al. (2010) Biotechnol., 28, 935–942.) for detailed semantic exchange.
  • Systems Biology Graphical Notation Markup Language (SBGNML), a format that supports biological process visualization (Le Novère et al. Nat. Biotechnol., 27, 735–741. (2009); van Iersel et al. (2012) Bioinforma. Oxf. Engl., 28, 2016–2021.)

Our data is licensed under CC0.

Required software

Required software for Graph Database if Docker not used

The following lines should be present in the neo4j.conf file of ~/neo4j-community-5.X.X/conf:

  • server.default_advertised_address=localhost
  • server.default_listen_address=0.0.0.0
  • server.bolt.enabled=true
  • server.bolt.tls_level=DISABLED
  • server.bolt.listen_address=:7687
  • server.bolt.advertised_address=:7687
  • server.http.enabled=true
  • server.http.listen_address=:7474
  • server.http.advertised_address=:7474

Configuration

The following environment variables can be used to configure the server:

General:

  • NODE_ENV : the environment mode; either production or development (default)
  • PORT : the port on which the server runs (default 3000)
  • LOG_LEVEL : minimum log level; one of info (default), warn, error
  • BASE_URL : used for email linkouts (e.g. https://factoid.baderlab.org)
  • API_KEY : used to restrict new document creation (e.g. 8365E63B-9A20-4661-AED8-EDB1296B657F)

CRON:

  • CRON_SCHEDULE : second (optional), minute, hour, day of month, month, day of week
  • DOCUMENT_CRON_UPDATE_PERIOD : Milliseconds between successive Document cron update calls
  • DOCUMENT_CRON_STALE_PERIOD : Milliseconds since Documemt was last edited; criteria for trashing
  • GRAPHDB_CRON_REFRESH_PERIOD_MINUTES : Minimum time (minutes) between refreshes of graph DB data

Database:

  • DB_NAME : name of the db (default factoid)
  • DB_HOST : hostname or ip address of the database host (default localhost)
  • DB_PORT : port where the db can be accessed (default 28015, the rethinkdb default)
  • DB_USER : username if the db uses auth (undefined by default)
  • DB_PASS : password if the db uses auth (undefined by default)
  • DB_CERT : local file path to certificate (cert) file if the db uses ssl (undefined by default)

Downloads:

  • BULK_DOWNLOADS_PATH : relative path to bulk downloads
  • BIOPAX_DOWNLOADS_PATH : relative path to biopax downloads
  • BIOPAX_IDMAP_DOWNLOADS_PATH : relative path to id-mapped biopax downloads
  • EXPORT_BULK_DELAY_HOURS : period to delay (batch) export tasks

Services:

  • DEFAULT_CACHE_SIZE : default max number of entries in each cache
  • REACH_URL : full url of the reach textmining endpoint
  • PC_URL : base url for pathway commons apps, to search or link
  • BIOPAX_CONVERTER_URL : url for the factoid to biopax/sbgn converter
  • GROUNDING_SEARCH_BASE_URL: url for the grounding service
  • NCBI_EUTILS_BASE_URL : url for the NCBI E-utilities
  • NCBI_EUTILS_API_KEY : API key for the NCBI E-utilities
  • INDRA_DB_BASE_URL : url for INDRA (Integrated Network and Dynamical Reasoning Assembler)
  • INDRA_ENGLISH_ASSEMBLER_URL : url for service that assembles INDRA statements into models
  • SEMANTIC_SEARCH_BASE_URL : url for semantic-search web service
  • ORCID_BASE_URL : url for ORCID website
  • ORCID_PUBLIC_API_BASE_URL : url for version of ORCID public API
  • NO_ABSTRACT_HANDLING : labels directing how to sort documents missing query text. 'text' (default): autogenerate text from templates; 'date': sort by date and ignore text.
  • CROSSREF_API_BASE_URL : url for Crossref Unified Resource API
  • NCBI_BASE_URL : url for the NCBI/NLM/NIH
  • PUBTATOR_API_PATH : url path for the PubTator3 web service API

Links:

  • UNIPROT_LINK_BASE_URL : base url concatenated to id to generate a linkout
  • CHEBI_LINK_BASE_URL: base url concatenated to id to generate a linkout
  • PUBCHEM_LINK_BASE_URL: base url concatenated to id to generate a linkout
  • NCBI_LINK_BASE_URL: base url concatenated to id to generate a linkout
  • PUBMED_LINK_BASE_URL: base url concatenated to unique id to generate linkout
  • DOI_LINK_BASE_URL: base url concatenated to doi to generate linkout
  • GOOGLE_SCHOLAR_BASE_URL : base url concatenated to doi, title, or pmid to generate linkout
  • IDENTIFIERS_ORG_ID_BASE_URL : base url concatenated to collection id_prefix:id (i.e. prefix:accession)

Demo:

  • DEMO_ID : the demo document id (default demo)
  • DEMO_SECRET : the demo document secret (default demo)
  • DEMO_JOURNAL_NAME : the journal name for the demo doc
  • DEMO_AUTHOR : the author display name for the demo doc
  • DEMO_TITLE : the title of the demo doc's article
  • DEMO_CAN_BE_SHARED : whether the demo can be shared (default false)
  • DEMO_CAN_BE_SHARED_MULTIPLE_TIMES : whether the demo can be shared multiple times (normal docs can be shared only once; default false)
  • SAMPLE_DOC_ID : id for document that is used as homepage example (production)

Sharing:

  • DOCUMENT_IMAGE_CACHE_SIZE : number of images to cache in memory
  • DOCUMENT_IMAGE_PLL_LIMIT : max number of images to be generated in parallel (expensive)
  • DOCUMENT_IMAGE_WIDTH : tweet card image width
  • DOCUMENT_IMAGE_HEIGHT : tweet card image height
  • DOCUMENT_IMAGE_PADDING : padding around tweet card image (prevents twitter cropping issues)
  • TWITTER_ACCOUNT_NAME : twitter account visible on card
  • TWITTER_CONSUMER_KEY : twitter api key
  • TWITTER_CONSUMER_SECRET : twitter api secret
  • TWITTER_ACCESS_TOKEN_KEY : twitter app key
  • TWITTER_ACCESS_TOKEN_SECRET : twitter app secret
  • MAX_TWEET_LENGTH : max characters a user can type as a share caption

Email:

  • EMAIL_ENABLED: boolean to enable third-party mail service (default false)
  • EMAIL_FROM: name to send emails from (default Biofactoid)
  • EMAIL_FROM_ADDR: address to send emails from (default support@biofactoid.org)
  • SMTP_PORT: mail transport port (default 587)
  • SMTP_HOST: mail transport host (default localhost)
  • SMTP_USER: mail transport auth user
  • SMTP_PASSWORD: mail transport auth password
  • EMAIL_VENDOR_MAILJET: name of Mailjet vendor
  • MAILJET_TMPLID_INVITE: vendor email template id for an invitation
  • MAILJET_TMPLID_FOLLOWUP: vendor email template id for a follow-up
  • MAILJET_TMPLID_REQUEST_ISSUE: vendor email template id for a request error notification
  • EMAIL_TYPE_INVITE: name to indicate invite email
  • EMAIL_TYPE_FOLLOWUP: name to indicate follow-up email
  • EMAIL_TYPE_REQUEST_ISSUE: name to indicate request error email
  • EMAIL_SUBJECT_INVITE: subject text for invitation email
  • EMAIL_SUBJECT_FOLLOWUP: subject text for follow-up email
  • EMAIL_SUBJECT_REQUEST_ISSUE: subject text for request error email

AppSignal:

  • APPSIGNAL_PUSH_API_KEY : AppSignal API key
  • APPSIGNAL_APP_NAME : name of this app (e.g. 'Biofactoid')
  • APPSIGNAL_APP_ENV : used to indicate which instance is running (e.g 'master', 'production', 'unstable')

Graph Database:

  • GRAPHDB_CONN : The connection string
  • GRAPHDB_USER : Authentication username
  • GRAPHDB_PASS : Authentication password

The following environment variables should always be set in production instances:

  • NODE_ENV : set to production
  • BASE_URL : the production url
  • API_KEY : set to a uuid that you keep secret (used in management panel)
  • TWITTER_ACCOUNT_NAME : twitter account visible on card
  • TWITTER_API_KEY : twitter api key
  • TWITTER_API_KEY_SECRET : twitter api secret
  • TWITTER_ACCESS_TOKEN : twitter app key
  • TWITTER_ACCESS_TOKEN_SECRET : twitter app secret
  • NCBI_EUTILS_API_KEY: the API key for pathwaycommons account
  • EMAIL_ENABLED: true for Mailjet support
  • SMTP_HOST: Mailjet host name
  • SMTP_USER: Mailjet account credentials
  • SMTP_PASSWORD: Mailjet password credentials
  • APPSIGNAL_PUSH_API_KEY : AppSignal API key
  • APPSIGNAL_APP_ENV : used to indicate which instance is running (e.g 'master', 'production', 'unstable')

Run targets

  • npm start : start the server
  • npm stop : stop the server
  • npm run build : build project
  • npm run build-prod : build the project for production
  • npm run bundle-profile : visualise the bundle dependencies
  • npm run clean : clean the project
  • npm run watch : watch mode (debug mode enabled, auto rebuild, livereload)
  • npm test : run tests
  • npm run lint : lint the project
  • npm run fix : fix minor linting errors (ones that can be automatically fixed)

Running via Docker

Images are maintained at dockerhub. Also see factoid-docker-config.

Testing

All files /test will be run by Mocha. You can npm test to run all tests, or you can run mocha -g specific-test-name (prerequisite: npm install -g mocha) to run specific tests.

The tests expect rethinkdb to be running on localhost on the default port (28015).

Chai is included to make the tests easier to read and write.

Notes:

  • The Syncher.synch() is setup separately for each test file and namespaced. The reason for this is that the tests need to be able to be run independently and previous Syncher.synch() calls from other files would otherwise conflict.
  • Each test file should require('./util/conf') to make debugging with promises easier etc.

Publishing a release

  1. Make sure the tests are passing: npm test
  2. Make sure the linting is passing: npm run lint
  3. Bump the version number with npm version, in accordance with semver. The version command in npm updates both package.json and git tags, but note that it uses a v prefix on the tags (e.g. v1.2.3).
  4. For a bug fix / patch release, run npm version patch.
  5. For a new feature release, run npm version minor.
  6. For a breaking API change, run npm version major.
  7. For a specific version number (e.g. 1.2.3), run npm version 1.2.3.
  8. Push the release: git push origin --tags
  9. Publish a GitHub release so that Zenodo creates a DOI for this version.

Related software

Factoid depends on services whose software we maintain.