VIVO Documentation
Page History
...
You will also need to move your customisations customizations into the new Maven structure.
...
It is recommended that you treat the "installer" (or standard distribution) project(s) as a third tier, and keep local customisations customizations only in those these project(s).
For Java files, you can place them directly in the "webapp/src/main/java" directory - these will be compiled and included into your web application as class files. As class files are loaded ahead of jars in WEB-INF/lib, this even allows you to completely overwrite and replace classes that are supplied by the VItro Vitro / VIVO jars.
Your theme - and any other template modifications, etc. - should be placed in the "webapp/src/main/webapp" directory.
...
The Capability Map is only linked from the main menu bar, which is dynamically generated from statements in the triple store. The file that includes those these definitions is only loaded once during the first startup of VIVO.
...
Once saved, you should see the new entry in the menu bar , and be able to navigate to the capability map.
| Note |
|---|
The Capability Map depends on having People with Research Areas defined. If you do not have enough research areas to make the capability map useful, you can remove the menu entry by using the page from the menu via Page Management. |
AltMetrics on Profiles
...
Overview
Content Tools