When doing a manifest import, the data and model graphs get cleared by default. Here's what the console output looks like:
INFO: Ingestion package upload staged
INFO: Ingestion package C:\Users\200005944\Data\GitHub\linkedUpdate\data\ingestionpackage.zip upload queued
INFO: Loading manifest for 'SPDM Sample Data'...
INFO: Clear graph http://rack001/model
INFO: Clear graph http://rack001/data
INFO: Load OWL OwlModels/AGENTS.owl to http://rack001/model
INFO: Load OWL OwlModels/ANALYSIS.owl to http://rack001/model
INFO: Load OWL OwlModels/BASELINE.owl to http://rack001/model
INFO: Load OWL OwlModels/CLAIM.owl to http://rack001/model
...
We suspect it is because the CLEAR_FOOTPRINT_GRAPHS_ ON_LOAD option is defaulted to true when using the zip uploader.
We should let the user select whether or not to clear. Although the original idea was that an ingestion package is inclusive of everything (ontology + data), one possible use case for when you don't want to clear is loading 2 ingestion packages, one after another, that are complimentary. For instance, the second package adds data based on query returns from the first ingestion package.
When doing a manifest import, the data and model graphs get cleared by default. Here's what the console output looks like:
We suspect it is because the CLEAR_FOOTPRINT_GRAPHS_ ON_LOAD option is defaulted to true when using the zip uploader.
We should let the user select whether or not to clear. Although the original idea was that an ingestion package is inclusive of everything (ontology + data), one possible use case for when you don't want to clear is loading 2 ingestion packages, one after another, that are complimentary. For instance, the second package adds data based on query returns from the first ingestion package.