...

Ability to search across multiple VIVO installations. (Please refine this)

What features are desired for the search? What type of search? What is the goal of the search?

Full text?  "semantic"?  faceted?  other? Complex queries? For people? For publications? (Please refine this)

High level description of approach

...

       add the document to the Solr index

High level

...

approach to keeping the index up-to-date.

  For each institution:

    get a list of URIs that have been modified

...

 As of 2012 vivosearch.org uses Drupal and solrsearch javascript libraries. This chose could be revisited for the multi-site VIVO search project.  If the solrsearch javascript can provide almost all of the interactivity on the client side it might be desirable to

 have the server side be as simple as possible.  It may even be possible to use static HTML and .js files served by any old web server.

 In order to scale the process out we were planing to use Hadoop to manage parallel tasks.  Many approaches to the problem of indexing linked data from VIVO sites would be embarrassingly paralleled.

...

Serving the web site could be done with just about any system that allows interaction with Solr.  The solrsearch javascript libraries would allow any system that serves HTML and js to server this.  The options are expansive: httpd, wordpress, movible type, drupal, cold fusion.  If the solrsearch javascript can provide almost all of the interactivity on the client side it might be desirable for the server side be as simple as possible.  It may even be possible to use static HTML and .js files served by any old web server.

Onece an index was created how would it be updated?

...