This codebase is based on the latest version of the Play framework and as such it needs Java 8 to build. Modules are defined under modules. The main Play app is defined in app. To build the main app, type

$ ./activator {target}

where {target} can be one of {compile,run,test, dist}. Building modules is similar:

$ ./activator {module}/{target}

where {module} is the module name as it appears under modules/ and {target} can be {compile, test}. To run a particular class in a particular module, use the runMain syntax, e.g.,

$ ./activator "project stitcher" "runMain ncats.stitcher.tools.DuctTape"

We propose a graph-based approach to entity stitching and resolution. Briefly, our approach uses clique detection to do the stitching and resolution as follows:

1. For a given hypergraph (multi-edge) of stitched entities, extract connected components based on stitching keys as defined in StitchKey.

2. For each connected component, perform exhaustive clique enumeration over each stitch key. A clique is a complete subgraph of size 3 or larger.

3. Next we identify a set of high confidence cliques. A high confidence clique is a clique for which its members do not belong to any other clique. All nodes in a clique are merged to become a stitched node.

4. For the leftover cliques, we perform a sort by descending order of the value |V| * |E| where |V| and |E| are the clique size and the cardinality of stitch keys, respectively. Stitched nodes are created as we iterate through this order ignoring any nodes that have already been stitched.

1. Try invoking the sbt shell to check if it is available, then exit.

$ sbt

2. Initiate (define auxiliary functions, check for java version, etc.), then exit.

$ bash activator2

3. Build, stitch, and calculate events. a) Make sure you have a file .sbtopts in your stitcher directory that has the following content:

-J-Xms1024M -J-Xmx16G -J-Xss1024M -J-XX:+CMSClassUnloadingEnabled -J-XX:+UseConcMarkSweepGC

b) Check the script and search for the database name (e.g. stitchv1.db):

$ cat scripts/stitch-all-current.sh

If you have a database with the same name in your stitcher directory, either remove it or modify the script to have a different db name (e.g. stitchv2.db).

c) From the stitcher directory, run:

$ bash scripts/stitch-all-current.sh

NOTE: Building the databse and stitching should take about 4 and 5 hours, respectively, on a laptop (i5-4200U @ 2.3 GHz, 8GB RAM). Complete process on a server (ifxdev.ncats.nih.gov) takes approximately 5-6 hours.

NOTE: Since the process takes a while, it's better run the process in a separate screen to keep the process running, if the connection to the server/terminal is reset. While nohup is another option, it is problematic in this case, as it will stop the job at the end of every command due to a tty output attempt.

$ screen
$ bash scripts/stitch-all-current.sh > stitch.out 2>&1
#press 'ctrl+a', then 'd' to disconnect from the screen

NOTE: If you encounter errors, try cleaning the project by removing all target directories directly, and then re-run the script:

$ find . -name target -type d -exec rm -rf {} \;
$ bash scripts/stitch-all-current.sh

1. In your stitcher directory, make a symbolic link stitcher.ix/data.db pointing to the database you have just made.

#first, remove old link or a folder with the same name (if present)
$ rm -r stitcher.ix/data.db
#then create the symlink
$ ln -s ../stitchv1.db stitcher.ix/data.db

2. Navigate to your stitcher directory and run the project.

$ sbt run

3. When prompted in the console, navigate to http://localhost:9000/app/stitches/latest in your browser.

####(optional -- only do this if you have changed the stitcher code or starting anew)

0. !!!Please make sure you run the following test when you update the stitching algorithm

sbt stitcher/"testOnly ncats.stitcher.test.TestStitcher"

and ensure all the basic stitching test cases are passed before doing a build

1. Make a distribution. In the stitcher directory run:

sbt dist

It will be created in stitcher/target/universal/ and have a name similar to ncats-stitcher-master-20171110-400d1f1.zip.

2. Copy the archive to the deployment server (e.g. dev.ncats.io). For example:

#navigate to path-to-stitcher-parent-directory/stitcher/target/universal/ 
#scp to the server
$ scp ncats-stitcher-master-20171110-400d1f1.zip [email protected]:/tmp

3. Unzip into the desired folder (on [email protected], it is ~).

#navigate to the desired folder on the deployment server
$ ssh [email protected]
#unzip
$ unzip /tmp/ncats-stitcher-master-20171110-400d1f1.zip

1. In the stitcher folder (where you have prepared the database), archive the database folder and copy it over to the deployment server.

$ zip -r stitchv1db.zip stitchv1.db/
$ scp stitchv1db.zip [email protected]:/tmp

2. On the deployment server, navigate to a directory containing the stitcher distribution folder and unzip the database.

$ ssh [email protected]
$ unzip /tmp/stitchv1db.zip

3. Start up the app. The script takes the distribution and db folders as arguments.

$ bash restart-stitcher.sh ncats-stitcher-master-20171110-400d1f1 stitchv1.db

1. A distribution folder (e.g. ~/ncats-stitcher-master-20171110-400d1f1).
2. A database (e.g. ~/stitchv1.db).
3. A files-for-stitcher.ix folder with three files.
4. The script for (re)starting stitcher restart-stitcher.sh.

https://stitcher.ncats.io/app/stitches/latest
https://stitcher.ncats.io/app/stitches/latest/ + UNII
https://stitcher.ncats.io/app/stitches/latest/aspirin
https://stitcher.ncats.io/api/datasources

• Problem:

  java.lang.NumberFormatException: For input string: "0x100"
  

  Cause:
  SBT uses jline for terminal output. The latter in turn uses the infocmp utility provided by ncurses, which expects only decimal values. This behaviour was fixed in a new version of jline and and newer version of SBT, however version 0.13.15 used for this project still suffers from it.
  Solution:
  Add the following to your ~/.bashrc:

  export TERM=xterm-color
  

The underlying Neo4j for stitcher is publicly accessible here. Please specify stitcher.ncats.io:80 in the Host field. No credentials are needed.