FAQ

An Anzo Data Store, also known as a graph data source, is a designated directory on the File Store where Anzo can save the RDF files that are generated during the ETL process. All installations require at least one Anzo Data Store. You can create one data store and configure all pipelines to write to that store (each ETL run automatically creates a new sub-directory under the data store) or you can create multiple data stores to use for different Datasets. For information about creating data stores, see Creating an Anzo Data Store.

Dataset Pipelines are used to ingest data into Anzo. They produce new Datasets in the Dataset catalog and generate RDF files for loading data to AnzoGraph. All auto-ingested pipelines are Dataset Pipelines. For more information, see Creating a Dataset Pipeline.

ETL pipelines do not ingest data into Anzo; they are used to ingest data into a file or another database. ETL pipelines do not generate a new Dataset entry in the catalog or produce RDF load files for AnzoGraph. When you create mappings for ETL pipelines, you define a file schema or database as the target. For more information, see Creating an ETL Pipeline.

If the data in a CSV file changes, the way that you update the dataset in Anzo depends on the type of changes that were made to the file and the file system where the file is hosted. The table below provides guidance on the steps to take to update Anzo based on the type of content updates and the file location.

Using the Anzo for Office Excel plugin, users can duplicate mappings to use as a template for a new mapping. Follow the instructions below to duplicate a mapping.

1. In Excel, open the Anzo Mapper tool and connect to the Anzo server.
2. In the Mapper menu, click the folder icon () to list the mappings that are available to open. By default, the mapping tool lists only the mappings that you created. To display additional mappings, such as auto-generated files, type a term in the Search field, and then click the cog icon () to display the files. For example:

   

3. Click the mapping that you want to duplicate. Selecting a mapping activates the buttons at the top of the screen. For example:

   

4. Click the Duplicate icon () to copy the selected mapping. Anzo displays the Duplicate Mapping dialog box. For example:

   

5. Edit the mapping name and then click OK to create the duplicate. The new mapping is added to the list of mappings that are available to open.

Follow the instructions below to associate a model that is in Anzo with an onboarded data set.

1. In the Anzo application, expand the Blend menu and click Datasets. Anzo displays the Datasets catalog, which lists the existing data sets.
2. Click the data set that you want to add a model to. Anzo displays the Explore screen for the data set.
3. Click the Overview tab. Under the Description field, click Advanced to display the advanced options. For example:

   

4. Click the edit icon () for the Models field to open the Models drop-down list, and then select the model that you want to use for this data set. To include a system model, select the Include System Data checkbox. To select multiple models, click the drop-down list again and select another model.
5. When you have finished selecting models, click the checkmark icon () to save the change and associate the model or models with the data set.

Follow the instructions below to download a data model to your computer.

1. In the Anzo application, click Model. Anzo displays the Manage Data Model Working Set screen. For example:

   

2. On the Manage Working Set screen, select the checkbox next to the model that you want to download, and then click OK. Anzo opens the selected model in the editor. For example:

   

3. Open the model menu by clicking the menu icon () to the right of the model name. Then select Download Model.

   

   Anzo displays the Download Model dialog box:

   

4. In the Download Model dialog box, select the format to save the model in. By default Anzo saves models in TRIG format. If you want to save the file in OWL format, select the OWL radio button. Then click Download.

Anzo downloads the model to your computer in the selected format.

Anzo displays graphmart details, such as a list of the models in the graphmart, on the Overview screen for the graphmart. Follow the steps below to view the list of models in a graphmart.

1. In the Anzo application, expand the Blend menu and click Graphmarts. Anzo displays the Graphmarts screen.
2. In the list of Graphmarts, click the name of the Graphmart for which you want to view the included Models. Anzo displays the Graphmart Overview. For example:

   

   In the bottom right corner of the graph view in the center of the screen, there are three icons:

   

3. To view the associated Models, click the contents icon () on the right. For example, the image below shows a Graphmart with two Models:

   

Anzo displays graphmart details on the Overview screen for the graphmart. Follow the steps below to view and copy a Graphmart URI.

1. In the Anzo application, expand the Blend menu and click Graphmarts. Anzo displays the Graphmarts screen.
2. In the list of Graphmarts, click the name of the Graphmart for which you want to view or copy the URI. Anzo displays the Graphmart Overview. For example:

   

3. View the Graphmart URI in the statistics section on the right side of the screen. For example:

   

   You can click the clipboard icon () to copy the URI to your clipboard.

You can also copy a URL-encoded version of the Graphmart URI from the address bar in the browser when viewing the Graphmart Overview. For example:

You can retrieve a graph or Data Layer URI on the Data Layers screen for a Graphmart. Follow the steps below to copy a graph URI.

1. In the Anzo application, expand the Blend menu and click Graphmarts. Anzo displays the Graphmarts screen.
2. In the list of Graphmarts, click the name of the Graphmart that contains the Data Layer whose URI you want to copy. Anzo displays the Graphmart Overview.
3. Click the Data Layers tab. Anzo displays the Data Layers in the Graphmart. Each layer is a graph. For example:

   

4. To copy the URI for a layer to your clipboard, click the menu icon () for the layer and click Copy URI.

   

Follow the steps below to view and copy the URI for a Dataset in the catalog.

1. In the Anzo application, expand the Blend menu and click Datasets. Anzo displays the Dataset catalog, which lists the onboarded Datasets.
2. Click the name of the Dataset for which you want to copy the URI. Anzo displays the Explore tab. For example:

   

3. Click the Overview tab to view the general information for the Dataset. For example:

   

4. In the statistics section on the right side of the screen, click the clipboard icon () to copy the URI to your clipboard. For example, the image below shows the URI highlighted:

   

To query from a remote client (such as over the SPARQL endpoint) a linked data set (LDS) that is stored in a local volume, you need to specify the catalog entry URI for that LDS as the target data set. The catalog entry URI uniquely identifies an LDS because it encodes both the LDS and its data source (local volume) in the URI. Follow the steps below to find the catalog entry for an LDS.

1. First, retrieve the URI for the LDS whose catalog entry URI you want to find. For instructions, see How do I find the URI for a dataset? above.
2. Next, open the Find tab in the Query Builder. In the Anzo application, expand the Access menu and click Query Builder. Then click the Find tab. The Find screen opens and the System Datasource is selected as the target data source.

   

3. If the LDS is in a different volume, click the Source drop-down list and select the appropriate volume. Typically, linked data sets are stored in the system volume.
4. Paste in the Object field the LDS URI that you copied in the first step. Then click Find. Anzo returns the set of quads for which the LDS URI is the object. For example:

   

5. In the Subject field in the results, look for a URI that begins with http://openanzo.org/catEntry. The value is the catalog entry URI for the LDS. For example:

   

6. Copy the entire URI. This is the URI to use as the target data source for SPARQL endpoint queries against the LDS. For more information about the SPARQL endpoint, see Accessing Data from the SPARQL Endpoint.

Follow the instructions below if you want to clear out all of the existing components from the Managed Edition so that the Edition is recreated from scratch the next time the pipeline is published.

1. First, copy the URI of the Dataset for which you want to clear the Managed Edition. How do I find the URI for a dataset?
2. Next, In the Administration application, expand the Monitoring & Diagnostics menu and select Semantic Services.
3. Search for the LinkedDataService and view its details. Then click the Service Builder tab in Semantic Service Details.
4. Click the Please Select an Operation field and select clearWorkingEdition from the drop-down list. The Request Statements for the service call are populated:

   

5. Toward the bottom of the request, replace the <temp://value_to_fill_in_1> placeholder URI with the URI for the Dataset.

   <http://serviceRequesta9e72cca-a79b-42f6-94a7-1ef9dfb1e65c> {
     <http://serviceRequesta9e72cca-a79b-42f6-94a7-1ef9dfb1e65c> a ld:ClearWorkingEditionRequest ;
       ld:fldsToClear <temp://value_to_fill_in_1> ;
       ld:typesToClear <temp://value_to_fill_in_0> .
   
   <temp://value_to_fill_in_1> a ld:FileBasedLinkedDataSet .
   }

   For example:

   <http://serviceRequesta9e72cca-a79b-42f6-94a7-1ef9dfb1e65c> {
     <http://serviceRequesta9e72cca-a79b-42f6-94a7-1ef9dfb1e65c> a ld:ClearWorkingEditionRequest ;
       ld:fldsToClear <http://csi.com/FileBasedLinkedDataSet/ee8d3d5792fd218a03b70fdf850b6a4c> ;
       ld:typesToClear <temp://value_to_fill_in_0> .
   
   <http://csi.com/FileBasedLinkedDataSet/ee8d3d5792fd218a03b70fdf850b6a4c> a ld:FileBasedLinkedDataSet .
   }

6. Comment out the ld:typesToClear <temp://value_to_fill_in_0> line. For example:

   <http://serviceRequesta9e72cca-a79b-42f6-94a7-1ef9dfb1e65c> {
     <http://serviceRequesta9e72cca-a79b-42f6-94a7-1ef9dfb1e65c> a ld:ClearWorkingEditionRequest ;
       ld:fldsToClear <http://csi.com/FileBasedLinkedDataSet/ee8d3d5792fd218a03b70fdf850b6a4c> ;
     # ld:typesToClear <temp://value_to_fill_in_0> .
   
   <http://csi.com/FileBasedLinkedDataSet/ee8d3d5792fd218a03b70fdf850b6a4c> a ld:FileBasedLinkedDataSet .
   }

7. Click the Run Service button to clear the Edition. Anzo returns a response such as the following example when the request is processed:

   @prefix n-1060687345: <http://openanzo.org/ClearWorkingEditionResponse/> .
   @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
   @prefix ld: <http://cambridgesemantics.com/ontologies/2009/05/LinkedData#> .
   @prefix ss: <http://openanzo.org/ontologies/2008/07/SemanticService#> .
   
   n-1060687345:effbda5b-ce9c-4190-abb1-6f6efd07f5d8 {
     n-1060687345:effbda5b-ce9c-4190-abb1-6f6efd07f5d8 ld:wasWorkingEditionCleared 
       "true"^^<http://www.w3.org/2001/XMLSchema#boolean> .
     n-1060687345:effbda5b-ce9c-4190-abb1-6f6efd07f5d8 rdf:type ld:ClearWorkingEditionResponse .
     n-1060687345:effbda5b-ce9c-4190-abb1-6f6efd07f5d8 rdf:type ss:ServiceResponse
   } 

Now, if you browse the Managed Edition for the Dataset, you will see that the Edition does not contain any Jobs or Data Components. The next time this Dataset's pipeline is published, the Managed Edition will be repopulated.

When you make modifications to data layers in a graphmart, Anzo displays Reload and Refresh buttons on the top of the Data Layers screen. For example:

The Refresh option becomes available when changes have been made to one or more data layers. Clicking Refresh resets (deletes from AnzoGraph) and reloads only the data layers that have changed. Clicking Reload resets and reloads the entire graphmart to AnzoGraph, including the data layers that have not changed.

When you publish a pipeline that includes a job that onboards data incrementally, Anzo preserves the previously onboarded data by moving the existing RDF files to a hidden directory within the FLDS. The new RDF files for the current pipeline are then written to the FLDS. Since hidden directories are not loaded to AnzoGraph, only the most current data is loaded into memory. For information about onboarding data incrementally, see Creating an Incremental Schema.