Run tanuki on beta site

[kshefchek]

Will require some updates to tanuki to crawl over client generated content, cc @kltm.

[kltm]

This will, unfortunately, have to be a low priority for the time being. Probably the easiest way to do it would be to use Armed Bear to get access to PhantomJS or similar.

[kshefchek]

I've ran tanuki a few times and we're not getting many errors, just on legacy pages and external links to GO Phenotype links, for example http://purl.obolibrary.org/obo/GO_0016049PHENOTYPE on http://beta.monarchinitiative.org/phenotype/GO:0016049PHENOTYPE

However, we're not getting much coverage of our site with all of the client side content, so take these results with a grain of salt. Will close for now as I don't think we'll be able to update tanuki for this release.

[kltm]

Just to verify, you're using both internal and extra crawling agents?

This is now an open issue here: kltm/tanuki#1
Pull requests welcomed.

[kshefchek]

@kltm that's correct (if you mean external)

[kltm]

True.

[kshefchek]

It also might be tricky since we don't load the GOlr tables until you click on a tab, but it would be easy to remove this on a branch and use that to test.

[kltm]

Again, it might be fine, but that would depend on how many simultaneous connections are allowed and how many tabs there are. Anyways, it's always to test the application as-is, rather than having a special branch--the tanuki agent would have to be smart enough to do these things.