Page History

...

...

Permits external applications to provide to request specific updates to the VIVO search index, by providing a list of URIs , and to request that the corresponding records in the search index be updatedwhose search records may be out of date.

When the VIVO triple-store is updated in any a way that bypasses VIVO's internal data channels, the search index will not reflect the changesupdates. Prior to VIVO release 1.6, the only solution was to rebuild the entire search index, from the Site Administration page.

...

Some sites use two VIVO instances. One is : a staging instance , and all a production instance. All ingests occur there. The other is a production instance, and periodically on the staging instance. Periodically, the triple-store is copied from staging to production. When this is done, you have 3 options:

• Copy the search index files from staging to production to keep it consistent with the triple-store
• Rebuild the search index in production
• Use the Search Indexing service to update specific records in the search index.

...

[vivo]/searchService/updateUrisInSearch

Examples:

...

http://vivo.cornell.edu/searchService/updateUrisInSearch

 

 

http://localhost:8080/vivo/searchService/updateUrisInSearch

 

HTTP Method

The API supports only HTTP POST requests with a content type of multipart/form-data.

...