All versions of this manual
X
Welcome to Linkurious administration manual v3.1.15. Use the menu to access other documentations.
  1. Introduction
  2. FAQ
  3. Getting started
    1. Release notes
    2. Client requirements
    3. Graph DB Feature Map
  4. Deploying on premise
    1. Technical requirements
    2. Downloading
    3. Installing
    4. Starting Linkurious
    5. Stopping Linkurious
  5. Deploying on Azure
    1. Pre-requisites
    2. Step-by-step deployment
    3. Updating
    4. Backing up your data
  6. Configuring
  7. Troubleshooting
    1. Checking Linkurious status
    2. Reading the logs
    3. Getting support
    4. Managing licenses
    5. Vulnerabilities
  8. Importing graph data
    1. Neo4j
    2. Cosmos db
    3. Updating your graph data
  9. Updating Linkurious
    1. Checking for updates
    2. Backing up your data
    3. Update procedure
  10. Configuring data-sources
    1. Neo4j
    2. Cosmos DB
    3. Alternative IDs
    4. Merging data-sources
    5. Advanced settings
  11. Search index
    1. Search Option Comparison
    2. Neo4j
    3. Azure search
    4. Configuring Elasticsearch
    5. Using Elasticsearch on AWS
    6. Incremental Indexing
    7. Numerical/Date search
  12. User-data store
    1. Migrating to an external database
    2. Backing-up your store
  13. Web server
  14. Authentication
    1. Getting started
    2. LDAP / Active Directory
    3. SSO with Azure AD
    4. SSO with Google
    5. SSO with OpenID Connect
    6. SSO with SAML2 / ADFS
    7. Configuration
  15. Access control
    1. Managing users
    2. Managing groups
    3. Standard access-rights
    4. Property-key access-rights
  16. Guest mode
    1. Guest mode
  17. Data Schema
    1. Property types
    2. Hiding data
    3. Strict mode
  18. Alerts
    1. Configuration
  19. Email Notifications
    1. Configuration
  20. Visualizations appearance
    1. Default styles
    2. Default captions
    3. Default properties order
    4. Geographic tiles
  21. Audit trail
    1. Log format
  22. Plugins
  23. Deep link
 

Importing graph data: Updating your graph data

When saving a visualization or a case, Linkurious Enterprise only stores the ID references to the nodes and edges stored in your graph database.
When updating your graph data you need to make sure your graph engine preserves those references to avoid any data loss.

There are 2 different strategies for updating your graph data. Each strategy has its own advantages and risks.

1. Updating your graph data incrementally.

This strategy consists in adding, removing or updating the nodes and edges within an existing database.
You can use this strategy when you know exactly the nodes and edges that have changed since your last database update.

After performing this update the following changes will be reflected in Linkurious Enterprise:

  • The nodes and edges modified will be reflected in your visualizations when you reopen them.
  • The nodes and edges added or modified will be properly searchable automatically or after a manual re-indexing operation depending on your search strategy. Learn more.
  • The nodes and edges removed from your graph database will be removed from your visualizations when you reopen them.

When you remove nodes and edges from your graph database, there is a chance those IDs are reused by the graph engine when you later create new nodes and edges. The consequence is that your existing visualizations may contain references to new nodes and edges unrelated to the existing context.
If you plan to incrementally remove data from your graph database, we recommend you use alternative identifiers before creating your visualizations.

2. Rebuilding your graph database.

This strategy consists in recreating your graph database from an external source.
You consider the current graph database stale, and you create a new graph database with fresh data.
This strategy is useful when your current infrastructure does not allow you to keep track of which nodes and edges are updated.

When you rebuild your graph database, new IDs will be assigned to all your nodes and edges, consequently breaking the references stored by Linkurious Enterprise.
If you are planning to use this strategy, it is very important you configure alternative identifiers before creating your visualizations.

In the unfortunate scenario that you have performed a database rebuild without configuring the alternative identifiers, Linkurious Enterprise will prevent access to your visualizations in an effort to prevent any data loss.

As an administrator, you can perform the following actions:

  1. Restore the previous version of the graph database from a backup
  2. Configure alternative identifiers
    1. After performing this configuration, you will need to re-open and save each visualization and case individually in order to apply the new configuration.