Meta Cartridges Usage via REST Request

Description.vsp underlies the /about/html/ page, and accepts the parameters described below.
ParameterSort in ascending order Value Description Example
@Lookup@ The type of lookup
refresh 0,1,2 etc. Usage: for cache invalidation.
When used 1 or larger number (n), adds get:refresh "N"(explicit refresh interval in seconds) as a directive to Sponger.
A refresh of zero ("0") seconds will make a new graph on the next lookup with the '@Lookup@' parameter value.
Refresh the graph with all current cartridges
refresh clean Usage: for overwriting.
The 'clean' usage explicitly clears the graph i.e. will cause the Sponger to drop cache even if it is marked to be in the fly.
Thus, if fetched cache by some reason is left in some inconsistent state like shutdown during Network Resource fetching, then 'clean' is required as it doesn't check cache state.
Note: must be used with caution as other threads may be doing fetching of network resources at same time.
Explicitly clear the graph
sponger:get add Usage: Add new triples to named graphs, progressively. This is the default value for the parameter sponger:get. May be used together with refresh=<seconds> to overwrite the expiration in the cache. Add new triples and refresh on every 10 seconds
sponger:get soft Usage: Network Resource Fetch data subject to cache invalidation mode and associated rules of instance. May be used together with refresh=<seconds> to overwrite the expiration in the cache. Network Resource Fetch data with option soft and refresh on every 10 seconds
sponger:get replace Usage: Replace subject to cache invalidation mode and rules, but coverage includes non fetched triples if such exist in a given named graph. may be used together with refresh=<seconds> to overwrite the expiration in the cache. Replace data and refresh on every 10 seconds
No Value When value is not given (i.e., @Lookup@=), all will work as if the parameter were not present.
The "Lookup" name is chosen to distinguish between parameters belonging to the URL being processed, and parameters for the Sponger.
Refresh the graph with all current cartridges, either type
0 NLP meta only Execute only NLP meta extraction
-2 Keywords-based only Execute only keywords-based meta extraction
x,y... A list of meta cartridges to be executed, by their unique IDs. The ID column can be found in Conductor -> RDF -> Sponger -> Meta Cartridges Execute only CNET (ID=19) and NYT: The TimesTags (ID=22) meta cartridges

Related