...
I'm not sure if you've seen this. NIH now has a way to bulk link your institution's faculty URIs to their RePORTER records. Chris Dorney from Boston University was the first to use this feature by sending them all the URIs from his BU Profiles site with the attached Excel template. You might want to forward it to VIVO sites. I imagine that if faculty URIs are linked to RePORTER, then it could also make it easier in the future for SciENcv to link to institution based profiles.
(Chris) You can see the general announcement of what was done in an issue of The ReSource ( http://report.nih.gov/resource/issue7/#rep177 ), as well as on one of their blogs ( http://nexus.od.nih.gov/all/2013/04/26/making-the-link-with-report/ ). You can just email them the file - Jim's contact info is on the template (also on Google Docs) . It's a nice way to drive more traffic to your sites.
Notable implementation and development list issues
Registering a custom list view
- Do custom XML files for list views go in our theme along with the custom .ftl files? As long as the filename is identical, will it pick them up?
- (Tim) Your custom xml files have to be in the /config directory; otherwise, the app will use the default list view.
- (Ted) The documentation in the wiki on Custom List View Configurations should be helpful. When adding a new custom listView (rather than editing an existing
view) it needs to be 'registered' in the vivoListViewConfig.rdf file. That was a stumbling block for us when we first attempted to create a custom view.
VSTO ontology slowing down web app
- (Tyler) We are having trouble implementing the VSTO ontology into our local vivo web app at LASP. Basically I create a new jena model for the vsto.owl ontology and then I import the ontology and attach it to the tbox. Doing this successfully integrates VSTO with our existing ontologies, but the entire web app is considerably slowed down. It goes from taking a second to load a page to taking about 30 seconds to load a page. Has anyone had this issue before and do they have any tips to speed things up?
- (BrianL) This isn't documented anywhere, but that "attach to TBox" button is a remnant of an earlier feature designed for local testing and ingest work, not for production deployment of an ontology. Enabling it causes access to the entire TBox to become vastly more inefficient. We'll plan to remove it in 1.6 because it no longer serves an important purpose. What you probably want to do is add the VSTO file(s) to the /WEB-INF/filegraph/tbox directory and restart Tomcat. Each file will be loaded into its own separate graph, and if you change the files on the filesystem and restart, the triple store will be automatically updated. You should see no performance hit using this method; in fact you'll notice this is how the main VIVO ontology itself is loaded.
Jira server DuraSpace JIRA key VIVO-237
...