This repository has been archived by the owner on Jan 5, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Disable enable inferencing at startup
Michael J. Giarlo edited this page May 21, 2018
·
1 revision
Whether inferencing is enabled or disabled when Vitro starts up is dependent on the contents of webapp/src/main/webapp/WEB-INF/resources/startup_listeners.txt. If the following line is not found, inferencing will be turned off:
edu.cornell.mannlib.vitro.webapp.servlet.setup.SimpleReasonerSetup
Else, it is enabled. You can see where we removed it in sul-dlss-labs/Vitro#3: https://github.com/sul-dlss-labs/Vitro/pull/2/files#diff-d33445b89aedcf20cae03b97d873457fL32
To re-enable it, add the line above directly beneath:
edu.cornell.mannlib.vitro.webapp.application.ApplicationImpl$ReasonersSetup
- RIALTO Wiki Homepage
- RIALTO Use Cases
- RIALTO Architecture
- RIALTO Data Models
- RIALTO Acceptance Criteria
- RIALTO Data Sources
- Demo Videos
- Neptune/λ Integration
- Core/Combine Integration
- SPARQL Proxy λ
- Derivatives λ
- Entity Resolver Service
- Rebuild Trigger Task
- Solr Setup
- Ingest Service
- Combine Data Sources
- Data Mappings
- Load Procedure
- Starting & Monitoring ETL
- Counting # of Publications
- Jena/TDB vs Blazegraph
- Vitro Ingest Options
- VIVO/Vitro Assessment
- VIVO Community Convo Notes
- Vitro vs Stand-Alone Datastore
- Provisioning a VM
- Deployment Process
- Toggle inferencing
- Check Inferencing is On
- Recompute inferences
- Toggle indexing
- Working with Vitro Solr
- Vitro Solr Samples
- Ingest via Fuseki SPARQL-over-HTTP
- Ingest via Jena ARQ
- Ingest via Jena tdbloader
- Ingest via Vitro SPARQL-over-HTTP
- Ingest via TDB Java API
- Vitro Logging
- Detecting TDB Changes