From a7b786b856b1eaae7e1f83c43e9c9cd86681432a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Annama=CC=81ria=20Koren?= Date: Wed, 26 Aug 2026 07:13:20 +0200 Subject: [PATCH] harmonize product naming across the documentation - use "eccenca Corporate Memory" consistently instead of "CMEM", "Corporate Memory" or "Eccenca Corporate Memory" - format Keycloak realm and client names as code (`cmem`, `cmem-service-account`) - bold graph names such as **CMEM DI Project** --- CONTRIBUTING.md | 2 +- .../backup-and-restore/index.md | 2 +- .../index.md | 2 +- .../configuration/completion-setup/index.md | 2 +- .../environment-based-configuration/index.md | 2 +- .../file-based-configuration/index.md | 2 +- .../index.md | 2 +- .../finding-and-filtering-objects/index.md | 2 +- .../scripting-with-cmemc/index.md | 2 +- .../troubleshooting-and-caveats/index.md | 2 +- docs/automate/continuous-integration/index.md | 2 +- .../index.md | 2 +- docs/automate/scheduling-workflows/index.md | 2 +- docs/build/active-learning/index.md | 2 +- docs/build/cool-iris/index.md | 2 +- docs/build/evaluate-template/index.md | 2 +- .../extracting-data-from-a-web-api/index.md | 2 +- docs/build/index.md | 2 +- .../index.md | 2 +- docs/build/kafka-consumer/index.md | 2 +- .../index.md | 2 +- .../index.md | 6 +++--- docs/build/spark/index.md | 4 ++-- .../define-the-interfaces/index.md | 2 +- .../define-the-need/index.md | 4 ++-- .../index.md | 2 +- .../index.md | 6 +++--- .../index.md | 2 +- .../link-IDS-event-to-KG-via-cmem/index.md | 6 +++--- .../link-IDS-event-to-KG/index.md | 2 +- .../consume-graphs-in-apache-kafka/index.md | 2 +- .../consuming-graphs-in-power-bi/index.md | 2 +- docs/consume/index.md | 2 +- .../index.md | 6 +++--- .../configuration/caveats/index.md | 2 +- .../configuration/dataintegration/index.md | 2 +- .../dataintegration/jdbc/index.md | 2 +- .../docker-orchestration/index.md | 2 +- .../explore/dataplatform/application-full.md | 8 ++++---- .../dataplatform/application-graphdb-full.md | 2 +- .../dataplatform/application-neptune-full.md | 6 +++--- .../configuration/graphinsights/index.md | 4 ++-- .../change-passwords-and-keys/index.md | 6 +++--- .../configuration/keycloak/index.md | 2 +- .../keycloak/using-external-keycloak/index.md | 6 +++--- .../production-ready-settings/index.md | 2 +- .../quad-store-configuration/index.md | 2 +- .../configuration/reverse-proxy/index.md | 2 +- .../scenario-k8s-deployment/index.md | 2 +- .../scenario-local-installation/index.md | 2 +- .../index.md | 2 +- .../index.md | 2 +- docs/develop/cmemc-scripts/index.md | 2 +- docs/develop/index.md | 4 ++-- docs/develop/packages/development/index.md | 2 +- .../packages/development/tutorial/index.md | 2 +- docs/develop/packages/installation/index.md | 2 +- .../python-plugins/development/index.md | 4 ++-- .../visually-authoring-ontologies/index.md | 2 +- docs/explore-and-author/companion/index.md | 2 +- .../index.md | 2 +- .../index.md | 6 +++--- .../graph-exploration/graph-insights/index.md | 2 +- .../graph-insights/navigating-to-cmem.md | 4 ++-- docs/explore-and-author/index.md | 2 +- docs/explore-and-author/link-rules/index.md | 4 ++-- .../workspace-configuration/index.md | 2 +- docs/getting-started/index.md | 2 +- .../corporate-memory-26-2/index.md | 19 ++++++++++++------- 69 files changed, 106 insertions(+), 101 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6f0de9241..c5a3add3b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -114,7 +114,7 @@ On this page is search function for icons available as well. |Success|Success admonitions are a type of documentation element used to highlight successful outcomes or positive results associated with a particular task, process, or feature|Graph is created successfully.| |Bug|A bug admonition include a description of the bug or issue, as well as steps that the user can take to avoid or work around the problem. It may also include information about when the bug will be fixed or patched, if applicable.|Users may experience issues with the file saving feature when running this software on Windows 10. To avoid data loss or corruption, be sure to save your work frequently and consider using an external backup device. Our development team is working to resolve this issue in the next software update.| |Example|The example admonition is typically used in instructional or educational documents to clarify complex concepts or demonstrate how to perform a specific task.|To create a new email account, click on the "Sign Up" button on the homepage and enter your name, email address, and desired password. Be sure to choose a strong password with a mix of uppercase and lowercase letters, numbers, and special characters. Once you have entered your information, click "Create Account" to complete the process.| -|Task|The Task admonition type is used to describe a series of steps or tasks required to complete a process or action. Clear and concise descriptions of each step, along with any relevant details or instructions, should be included. It's helpful to use images or diagrams to illustrate the process. Overall, The Task admonition is useful for providing detailed instructions to readers.|Loading Data into a CMEM involves 3 steps:
1. Connect to the database.
2. Choose the data file and appropriate file type.
3. Run workflow to import.| +|Task|The Task admonition type is used to describe a series of steps or tasks required to complete a process or action. Clear and concise descriptions of each step, along with any relevant details or instructions, should be included. It's helpful to use images or diagrams to illustrate the process. Overall, The Task admonition is useful for providing detailed instructions to readers.|Loading Data into eccenca Corporate Memory involves 3 steps:
1. Connect to the database.
2. Choose the data file and appropriate file type.
3. Run workflow to import.| diff --git a/docs/automate/cmemc-command-line-interface/backup-and-restore/index.md b/docs/automate/cmemc-command-line-interface/backup-and-restore/index.md index 93ce8b1f2..938f3f394 100644 --- a/docs/automate/cmemc-command-line-interface/backup-and-restore/index.md +++ b/docs/automate/cmemc-command-line-interface/backup-and-restore/index.md @@ -9,7 +9,7 @@ tags: ## Introduction -cmemc can export and re-import all data which Corporate Memory manages: the knowledge graphs in the store, the projects in the workspace, and any subset of them. +cmemc can export and re-import all data which eccenca Corporate Memory manages: the knowledge graphs in the store, the projects in the workspace, and any subset of them. This page describes which artifacts you can create, how to restore each of them, and - just as important - which parts of a deployment cmemc does **not** cover. !!! warning "A cmemc export is not a complete instance backup" diff --git a/docs/automate/cmemc-command-line-interface/configuration/certificate-handling-and-ssl-verification/index.md b/docs/automate/cmemc-command-line-interface/configuration/certificate-handling-and-ssl-verification/index.md index 90427c283..0cc2c2048 100644 --- a/docs/automate/cmemc-command-line-interface/configuration/certificate-handling-and-ssl-verification/index.md +++ b/docs/automate/cmemc-command-line-interface/configuration/certificate-handling-and-ssl-verification/index.md @@ -10,7 +10,7 @@ tags: ## Introduction -In a reasonable production deployment, all client-accessible Corporate Memory APIs will be securely available as HTTPS endpoints. +In a reasonable production deployment, all client-accessible eccenca Corporate Memory APIs will be securely available as HTTPS endpoints. This document clarifies how to deal with certificates. cmemc will validate the certificates of your HTTPS endpoints and indicate validation errors. If the certificates of your Corporate Memory deployment are based on a common and publicly available Certificate Authority (such as [Let's Encrypt](https://letsencrypt.org/)), cmemc is able to validate your certificates out of the box. diff --git a/docs/automate/cmemc-command-line-interface/configuration/completion-setup/index.md b/docs/automate/cmemc-command-line-interface/configuration/completion-setup/index.md index 1089a92cf..efc5787f6 100644 --- a/docs/automate/cmemc-command-line-interface/configuration/completion-setup/index.md +++ b/docs/automate/cmemc-command-line-interface/configuration/completion-setup/index.md @@ -12,7 +12,7 @@ tags: In case you are using bash or zsh as your terminal shell, you should enable [Command-line tab completion](https://en.wikipedia.org/wiki/Command-line_completion) for cmemc. Tab completion is a powerful feature and will save you a lot of typing work. -Furthermore, it will help you to learn the different commands, parameters and options and will auto-complete parameter values taken live from your Corporate Memory instance (such as graph IRIs, project IDs, etc.). +Furthermore, it will help you to learn the different commands, parameters and options and will auto-complete parameter values taken live from your eccenca Corporate Memory instance (such as graph IRIs, project IDs, etc.). ![cmemc - Create Dataset](22.1-cmemc-create-dataset.gif "cmemc - Create Dataset") diff --git a/docs/automate/cmemc-command-line-interface/configuration/environment-based-configuration/index.md b/docs/automate/cmemc-command-line-interface/configuration/environment-based-configuration/index.md index 7c8add5a3..6c0eef4d8 100644 --- a/docs/automate/cmemc-command-line-interface/configuration/environment-based-configuration/index.md +++ b/docs/automate/cmemc-command-line-interface/configuration/environment-based-configuration/index.md @@ -69,7 +69,7 @@ export CMEMC_CONFIG_FILE=cmemc.ini export CMEMC_CONNECTION=mycmem ``` -This alone allows us to save a lot of typing for a series of commands on the same Corporate Memory instance. +This alone allows us to save a lot of typing for a series of commands on the same eccenca Corporate Memory instance. ``` shell-session $ cmemc graph list --raw diff --git a/docs/automate/cmemc-command-line-interface/configuration/file-based-configuration/index.md b/docs/automate/cmemc-command-line-interface/configuration/file-based-configuration/index.md index 3427d9e7a..1ca228288 100644 --- a/docs/automate/cmemc-command-line-interface/configuration/file-based-configuration/index.md +++ b/docs/automate/cmemc-command-line-interface/configuration/file-based-configuration/index.md @@ -31,7 +31,7 @@ If you start cmemc without any command or option, it outputs a general introduct $ cmemc Usage: cmemc [OPTIONS] COMMAND [ARGS]... - Eccenca Corporate Memory Control (cmemc). + eccenca Corporate Memory Control (cmemc). cmemc is the eccenca Corporate Memory Command Line Interface (CLI). diff --git a/docs/automate/cmemc-command-line-interface/configuration/getting-credentials-from-external-processes/index.md b/docs/automate/cmemc-command-line-interface/configuration/getting-credentials-from-external-processes/index.md index 6244eb7dc..f489fadc6 100644 --- a/docs/automate/cmemc-command-line-interface/configuration/getting-credentials-from-external-processes/index.md +++ b/docs/automate/cmemc-command-line-interface/configuration/getting-credentials-from-external-processes/index.md @@ -54,7 +54,7 @@ export OAUTH_CLIENT_SECRET=$(get-my-secret.sh) ## External Processes -Another option, which is interesting when working with multiple Corporate Memory instances, is the configuration of an external process in your [cmemc configuration file](../file-based-configuration/index.md). +Another option, which is interesting when working with multiple eccenca Corporate Memory instances, is the configuration of an external process in your [cmemc configuration file](../file-based-configuration/index.md). In order to get credential information from an external process you need to use the following configuration variables to set up an external executable: diff --git a/docs/automate/cmemc-command-line-interface/finding-and-filtering-objects/index.md b/docs/automate/cmemc-command-line-interface/finding-and-filtering-objects/index.md index b34dfd2b8..aee87c37d 100644 --- a/docs/automate/cmemc-command-line-interface/finding-and-filtering-objects/index.md +++ b/docs/automate/cmemc-command-line-interface/finding-and-filtering-objects/index.md @@ -58,7 +58,7 @@ The following table gives an impression of how different these name sets are: !!! tip With [command-line completion](../configuration/completion-setup/index.md) enabled, you do not need to remember any of this. - Pressing ++tab++ after `--filter` offers the filter names of the current command, and pressing ++tab++ again often completes the values as well, taken live from your Corporate Memory instance. + Pressing ++tab++ after `--filter` offers the filter names of the current command, and pressing ++tab++ again often completes the values as well, taken live from your eccenca Corporate Memory instance. ## Combining filters diff --git a/docs/automate/cmemc-command-line-interface/scripting-with-cmemc/index.md b/docs/automate/cmemc-command-line-interface/scripting-with-cmemc/index.md index eaf62d9f0..19fbd412c 100644 --- a/docs/automate/cmemc-command-line-interface/scripting-with-cmemc/index.md +++ b/docs/automate/cmemc-command-line-interface/scripting-with-cmemc/index.md @@ -49,7 +49,7 @@ Combining `--id-only` with `--filter` is the basic building block of most cmemc ## JSON output -The `--raw` option is available on more than 40 commands and outputs the JSON as it was received from the Corporate Memory APIs. +The `--raw` option is available on more than 40 commands and outputs the JSON as it was received from the eccenca Corporate Memory APIs. Together with a tool such as [jq](https://jqlang.github.io/jq/), this allows for arbitrary post-processing: ``` shell-session title="IRIs of all writeable graphs" diff --git a/docs/automate/cmemc-command-line-interface/troubleshooting-and-caveats/index.md b/docs/automate/cmemc-command-line-interface/troubleshooting-and-caveats/index.md index 6622577f1..8bcc64c40 100644 --- a/docs/automate/cmemc-command-line-interface/troubleshooting-and-caveats/index.md +++ b/docs/automate/cmemc-command-line-interface/troubleshooting-and-caveats/index.md @@ -11,7 +11,7 @@ This page lists and documents possible issues and warnings when working with cme ## Proxy is in the way -If you feel that your system's proxy configuration negatively impacts the communication between cmemc and Corporate Memory, you can disable using any proxy by setting this variable: +If you feel that your system's proxy configuration negatively impacts the communication between cmemc and eccenca Corporate Memory, you can disable using any proxy by setting this variable: ``` shell-session export no_proxy='*' diff --git a/docs/automate/continuous-integration/index.md b/docs/automate/continuous-integration/index.md index c7780dc01..6e3b9b987 100644 --- a/docs/automate/continuous-integration/index.md +++ b/docs/automate/continuous-integration/index.md @@ -7,7 +7,7 @@ subtitle: and Delivery ## Introduction Project teams often manage crucial parts of their work assets inside of git repositories. -This includes Corporate Memory related files such as ontologies, shapes or project configurations. +This includes eccenca Corporate Memory related files such as ontologies, shapes or project configurations. Given such a project setup, it is often wanted to start activities with these Corporate Memory files. Continuous integration (CI) is the practice of automating the integration of changes from multiple contributors into a single project. Originated from software projects, CI can (and should) be applied to Knowledge Graph projects as well. diff --git a/docs/automate/processing-data-with-variable-input-workflows/index.md b/docs/automate/processing-data-with-variable-input-workflows/index.md index 1470475dc..9913e8f05 100644 --- a/docs/automate/processing-data-with-variable-input-workflows/index.md +++ b/docs/automate/processing-data-with-variable-input-workflows/index.md @@ -10,7 +10,7 @@ tags: ## Introduction -This tutorial shows how you can create and use data integration workflows to process data coming from outside Corporate Memory (i.e., without registering datasets). +This tutorial shows how you can create and use data integration workflows to process data coming from outside eccenca Corporate Memory (i.e., without registering datasets). This is achieved with the **Allow replacement** flag on input and/or output datasets. This flag is supported by most file dataset types. A replaceable dataset is created and used inside a workflow as an input for other tasks (e.g., a transformation). diff --git a/docs/automate/scheduling-workflows/index.md b/docs/automate/scheduling-workflows/index.md index 7c35df02d..a30e36caa 100644 --- a/docs/automate/scheduling-workflows/index.md +++ b/docs/automate/scheduling-workflows/index.md @@ -9,7 +9,7 @@ tags: ## Introduction -For a time-based execution of a workflow, Corporate Memory provides the Scheduler operator. Please note that, in case you want to schedule workflows externally, [cmemc can be used for that](../cmemc-command-line-interface/workflow-execution-and-orchestration/index.md). +For a time-based execution of a workflow, eccenca Corporate Memory provides the Scheduler operator. Please note that, in case you want to schedule workflows externally, [cmemc can be used for that](../cmemc-command-line-interface/workflow-execution-and-orchestration/index.md). ## Create a scheduler diff --git a/docs/build/active-learning/index.md b/docs/build/active-learning/index.md index f33b3ca7d..2ccac6342 100644 --- a/docs/build/active-learning/index.md +++ b/docs/build/active-learning/index.md @@ -15,7 +15,7 @@ Active learning infuses expert knowledge and creates new relationships between p > Active learning is a special case of machine learning in which a learning algorithm interactively queries a user to label new data points with the desired outputs. [[wikipedia]](https://www.wikiwand.com/en/Active_learning_(machine_learning)#introduction) -In Corporate Memory we apply this approach to the process of learning a linking rule by interactively label records from the configured source and target dataset. +In eccenca Corporate Memory we apply this approach to the process of learning a linking rule by interactively label records from the configured source and target dataset. Labeling in this case means to indicate if the pair of resources (from source and target) should be connected with the configured property. The labeling process creates reference links against which the linking rule can be created and further refined as more input is given by the user. diff --git a/docs/build/cool-iris/index.md b/docs/build/cool-iris/index.md index 2cc0fff4f..03fcee214 100644 --- a/docs/build/cool-iris/index.md +++ b/docs/build/cool-iris/index.md @@ -28,7 +28,7 @@ The following list of example IRIs demonstrate the broad scope of this concept: - `telnet://192.0.2.16:80/` - `urn:oasis:names:specification:docbook:dtd:xml:4.1.2` -## Best practices in Corporate Memory +## Best practices in eccenca Corporate Memory A good IRI is unique, stable, simple and manageable. diff --git a/docs/build/evaluate-template/index.md b/docs/build/evaluate-template/index.md index c0a22ca92..63c5b8341 100644 --- a/docs/build/evaluate-template/index.md +++ b/docs/build/evaluate-template/index.md @@ -56,7 +56,7 @@ The tutorial consists of the following steps, which are described in detail belo The vocabulary contains the classes and properties needed to map the source data into entities in the Knowledge Graph. -1. In Corporate Memory, click **Knowledge Graphs** in the navigation under **Explore** on the left side of the page. +1. In eccenca Corporate Memory, click **Knowledge Graphs** in the navigation under **Explore** on the left side of the page. ![Menu entry EXPLORE > Knowledge Graphs](menu-explore-knowledge-graphs.png){ class="bordered" width="40%" } diff --git a/docs/build/extracting-data-from-a-web-api/index.md b/docs/build/extracting-data-from-a-web-api/index.md index 975525b72..d8ae32f93 100644 --- a/docs/build/extracting-data-from-a-web-api/index.md +++ b/docs/build/extracting-data-from-a-web-api/index.md @@ -91,7 +91,7 @@ As we are only interested in the _HTTP Message Body_ which holds the JSON reposi ## 3 Create a JSON Dataset -To create a JSON-to-RDF-mapping within Corporate Memory, we have to first register an example response from the API (repos.json). Based on the schema of the response, we can then define step-by-step the mappings, which are used to build the Knowledge Graph. +To create a JSON-to-RDF-mapping within eccenca Corporate Memory, we have to first register an example response from the API (repos.json). Based on the schema of the response, we can then define step-by-step the mappings, which are used to build the Knowledge Graph. 1. Click the **Create** button (top right) in the data integration workspace and select the type **JSON**. diff --git a/docs/build/index.md b/docs/build/index.md index 6b69a550a..78c2f2f3e 100644 --- a/docs/build/index.md +++ b/docs/build/index.md @@ -34,7 +34,7 @@ The Build stage turns your source data—across files, databases, APIs, and stre - [Extracting data from a Web API](extracting-data-from-a-web-api/index.md) --- Build a Knowledge Graph based on input data from a Web API. - [Incremental Database Loading](loading-jdbc-datasets-incrementally/index.md) --- Load data incrementally from a JDBC Dataset (relational database Table) into a Knowledge Graph. - [Active learning](active-learning/index.md) --- Advanced workflows that improve results iteratively by incorporating feedback signals. - - [Connect to Snowflake](snowflake-tutorial/index.md) --- Connect Snowflake as a scalable cloud warehouse and lift/link its data in Corporate Memory to unify it with your other sources in one knowledge graph. + - [Connect to Snowflake](snowflake-tutorial/index.md) --- Connect Snowflake as a scalable cloud warehouse and lift/link its data in eccenca Corporate Memory to unify it with your other sources in one knowledge graph. - [Build Knowledge Graphs from Kafka Topics](kafka-consumer/index.md) --- Consume Kafka topics and lift event streams into a Knowledge Graph. - [Evaluate Jinja Template and Send an Email Message](evaluate-template/index.md) --- Template and send an email after a workflow execution. - [Link Intrusion Detection Systems to Open-Source INTelligence](tutorial-how-to-link-ids-to-osint/index.md) --- Link IDS data to OSINT sources. diff --git a/docs/build/introduction-to-the-user-interface/index.md b/docs/build/introduction-to-the-user-interface/index.md index 81fff3438..2f1c8ec12 100644 --- a/docs/build/introduction-to-the-user-interface/index.md +++ b/docs/build/introduction-to-the-user-interface/index.md @@ -59,7 +59,7 @@ A dataset represents an abstraction over raw data. In order to work with data, y There is a range of different dataset types for different kinds of source data. Important dataset types include: -- **Knowledge Graph** - Read RDF from or write RDF to a Knowledge Graph embedded in Corporate Memory. +- **Knowledge Graph** - Read RDF from or write RDF to a Knowledge Graph embedded in eccenca Corporate Memory. - **CSV** - Read from or write to an CSV file. - **XML** - Read from or write to an XML file. - **JSON** - Read from or write to a JSON file. diff --git a/docs/build/kafka-consumer/index.md b/docs/build/kafka-consumer/index.md index 907a6abe5..9186585e2 100644 --- a/docs/build/kafka-consumer/index.md +++ b/docs/build/kafka-consumer/index.md @@ -13,7 +13,7 @@ tags: [Apache Kafka](https://kafka.apache.org/) is a distributed event store and stream-processing platform. Kafka is widely used in enterprises for data pipelines, streaming analytics, data integration and other applications. -By using the [cmem-plugin-kafka](https://pypi.org/project/cmem-plugin-kafka/) [Python Plugin](../../develop/python-plugins/index.md), you can consume messages from Apache Kafka and use them inside Corporate Memory Workflows. +By using the [cmem-plugin-kafka](https://pypi.org/project/cmem-plugin-kafka/) [Python Plugin](../../develop/python-plugins/index.md), you can consume messages from Apache Kafka and use them inside eccenca Corporate Memory Workflows. ## Installation diff --git a/docs/build/lift-data-from-tabular-data-such-as-csv-xslx-or-database-tables/index.md b/docs/build/lift-data-from-tabular-data-such-as-csv-xslx-or-database-tables/index.md index 62fb4d209..bd5fabbdf 100644 --- a/docs/build/lift-data-from-tabular-data-such-as-csv-xslx-or-database-tables/index.md +++ b/docs/build/lift-data-from-tabular-data-such-as-csv-xslx-or-database-tables/index.md @@ -134,7 +134,7 @@ The vocabulary contains the classes and properties needed to map the data into t === "JDBC" - Instead of uploading the [services.csv](services.csv) sample file into Corporate Memory, you can also load it into a SQL database and access it from Corporate Memory using the JDBC protocol. + Instead of uploading the [services.csv](services.csv) sample file into eccenca Corporate Memory, you can also load it into a SQL database and access it from Corporate Memory using the JDBC protocol. 1. In the project, Click **Create** and select the **JDBC endpoint** type. diff --git a/docs/build/loading-jdbc-datasets-incrementally/index.md b/docs/build/loading-jdbc-datasets-incrementally/index.md index 3461908b3..42153b6cc 100644 --- a/docs/build/loading-jdbc-datasets-incrementally/index.md +++ b/docs/build/loading-jdbc-datasets-incrementally/index.md @@ -33,7 +33,7 @@ This tutorial walks you through the process of loading data incrementally from a ## 1 Create the JDBC dataset -To extract data from a relational database, you need to first register a **JDBC endpoint** in Corporate Memory. This tutorial assumes that you have access to the relational database from the Corporate Memory instance. +To extract data from a relational database, you need to first register a **JDBC endpoint** in eccenca Corporate Memory. This tutorial assumes that you have access to the relational database from the Corporate Memory instance. 1. In Corporate Memory, click Projects under **BUILD** in the navigation on the left side of the page. @@ -82,13 +82,13 @@ Now that we have the JDBC endpoint IRI, we will build the Metadata Graph to stor The following three RDF triples hold the (minimal) necessary information we need for this tutorial: -1. The first triple imports the CMEM DI Project graph into our Metadata Graph to enable access to the LIMIT property defined earlier and to additional information we may need in the future. +1. The first triple imports the **CMEM DI Project** graph into our Metadata Graph to enable access to the LIMIT property defined earlier and to additional information we may need in the future. 2. The second triple defines a label for the Graph. 3. The third triple defines the <...**lastOffset**> property we need for this tutorial. As a default, we set it to 0 to start with the first row in the table. For your project: -1. adjust the CMEM DI Project IRI and +1. adjust the **CMEM DI Project** IRI and 2. the JDBC endpoint IRI. **Import the Graph** in the Exploration tab → Graph (menu) → Add new Graph → Provide Graph IRI + Select file. diff --git a/docs/build/spark/index.md b/docs/build/spark/index.md index 1fad411cf..b89780f0a 100644 --- a/docs/build/spark/index.md +++ b/docs/build/spark/index.md @@ -4,11 +4,11 @@ tags: - Introduction - Explainer --- -# Apache Spark within Corporate Memory Build +# Apache Spark within eccenca Corporate Memory Build ## Introduction -This documentation provides an overview of Apache Spark and its integration within Corporate Memory’s Build component. +This documentation provides an overview of Apache Spark and its integration within eccenca Corporate Memory’s Build component. The goal is to provide a conceptual understanding of Spark, its purpose in Build, and how workflows leverage Spark-aware datasets for efficient, distributed data processing. The documentation is structured in two parts: diff --git a/docs/build/tutorial-how-to-link-ids-to-osint/define-the-interfaces/index.md b/docs/build/tutorial-how-to-link-ids-to-osint/define-the-interfaces/index.md index 23fe2db7c..7a52ff3a4 100644 --- a/docs/build/tutorial-how-to-link-ids-to-osint/define-the-interfaces/index.md +++ b/docs/build/tutorial-how-to-link-ids-to-osint/define-the-interfaces/index.md @@ -38,7 +38,7 @@ Here, the figure 3 is nice but before this first schema during the project, ther ## Technical feasibility with the available information It's not really technical to check if the data is available or not, but without technical knowledge, it's hard to evaluate the difficulty to link each id to their instance in your RDF knowledge graph. -In this tutorial, we learn to use Corporate Memory of Eccenca to transform these IDs to IRI to import properly these ID with the other data necessary to build these interface. +In this tutorial, we learn to use eccenca Corporate Memory to transform these IDs to IRI to import properly these ID with the other data necessary to build these interface. After research and one meeting with analysts, we have chosen the datasets of Mitre Attack, the datasets of IoC rules (Sigma and Hayabusa) in Github and of course, the IoCs data already in the Splunk indexes. diff --git a/docs/build/tutorial-how-to-link-ids-to-osint/define-the-need/index.md b/docs/build/tutorial-how-to-link-ids-to-osint/define-the-need/index.md index 903e7e13e..d6db11373 100644 --- a/docs/build/tutorial-how-to-link-ids-to-osint/define-the-need/index.md +++ b/docs/build/tutorial-how-to-link-ids-to-osint/define-the-need/index.md @@ -16,7 +16,7 @@ There are three things to know to describe a need: 2. What 3. The context -With our customers, we claim a knowledge graph can reduce the work of analysts in the Cybersecurity. So, one of our customer wanted to help their IN Analysts with the software Corporate Memory of eccenca. +With our customers, we claim a knowledge graph can reduce the work of analysts in the Cybersecurity. So, one of our customer wanted to help their IN Analysts with the software eccenca Corporate Memory. After several meeting, we defined the need. ### For who @@ -64,7 +64,7 @@ Here, the context shows this project is an exploration with like deliverable pro During this step of R&D, we are developing the tools to request a SPARQL service via an authentification OAuth directly by Splunk dashboard. You will install these Splunk apps step-by-step during this tutorial or you can download their "tar.gz" in SPlunk now: - "[Linked Data App](../link-IDS-event-to-KG/eccenca_commands.tar.gz)" to install the SPARQL command. You need to configure it with the details in his README file or in [its tutorial page](../link-IDS-event-to-KG/index.md). -- "[Investigate lateral movements with a knowledge graph](../link-IDS-event-to-KG-via-cmem/eccenca_poc_investigate.tar.gz)" to install our demonstrator to connect SPLUNK to CMEM. You need to read his README or [its tutorial page](../link-IDS-event-to-KG/index.md) to understand this example. +- "[Investigate lateral movements with a knowledge graph](../link-IDS-event-to-KG-via-cmem/eccenca_poc_investigate.tar.gz)" to install our demonstrator to connect SPLUNK to eccenca Corporate Memory. You need to read his README or [its tutorial page](../link-IDS-event-to-KG/index.md) to understand this example. After several propositions, analysts oriented the implementation of our first dashboards and finally, we showed clearly a benefice to use a knowledge graph via these results. diff --git a/docs/build/tutorial-how-to-link-ids-to-osint/index.md b/docs/build/tutorial-how-to-link-ids-to-osint/index.md index 94bd82722..00d3c5910 100644 --- a/docs/build/tutorial-how-to-link-ids-to-osint/index.md +++ b/docs/build/tutorial-how-to-link-ids-to-osint/index.md @@ -17,7 +17,7 @@ tags: 2. [Indicators of compromise rules, like Hayabusa and Sigma rules](lift-data-from-YAML-data-of-hayabusa-sigma/index.md) 5. Link IDS event to a knowledge graph in dashboards via: 1. [Queries](link-IDS-event-to-KG/index.md) - 2. [Inferences](link-IDS-event-to-KG-via-cmem/index.md) (for the advanced users of Corporate Memory) + 2. [Inferences](link-IDS-event-to-KG-via-cmem/index.md) (for the advanced users of eccenca Corporate Memory) ## Introduction diff --git a/docs/build/tutorial-how-to-link-ids-to-osint/lift-data-from-STIX-2.1-data-of-mitre-attack/index.md b/docs/build/tutorial-how-to-link-ids-to-osint/lift-data-from-STIX-2.1-data-of-mitre-attack/index.md index 8d176897b..54a1d2332 100644 --- a/docs/build/tutorial-how-to-link-ids-to-osint/lift-data-from-STIX-2.1-data-of-mitre-attack/index.md +++ b/docs/build/tutorial-how-to-link-ids-to-osint/lift-data-from-STIX-2.1-data-of-mitre-attack/index.md @@ -14,7 +14,7 @@ The MITRE ATT&CK datasets in STIX 2.1 JSON collections are here: The "ontology" of MITRE ATT&CK with STIX is here: [https://github.com/mitre/cti/blob/master/USAGE.md](https://github.com/mitre/cti/blob/master/USAGE.md) -The objective of this tutorial is not focus on the ontologies. In our use case, we just need to extract several metadata. If the community of STIX wants to resolve their problems, it will be the moment to define a solid ontology. If you are a newbie with the Linked Data technologies, you have to learn to generate in first a functional knowledge graph for your needs before building a perfect ontology for everybody. When you masterize the ontologies, we will modify this first ontology and you could refresh your knowledge graph when you want with Corporate Memory. +The objective of this tutorial is not focus on the ontologies. In our use case, we just need to extract several metadata. If the community of STIX wants to resolve their problems, it will be the moment to define a solid ontology. If you are a newbie with the Linked Data technologies, you have to learn to generate in first a functional knowledge graph for your needs before building a perfect ontology for everybody. When you masterize the ontologies, we will modify this first ontology and you could refresh your knowledge graph when you want with eccenca Corporate Memory. This tutorial is written in order to gradually acquire all the skills necessary to build from scratch a knowledge graph with Corporate Memory and update it automatically via Corporate Memory Console. This tutorial must be completed in order. @@ -626,7 +626,7 @@ Here, we are creating a new SPARQL Update task to calculate and insert automatic ### Refresh all automatically -The datasets of Mitre are updated regularly. You may want to update them automatically via a command line in a bash file. In this script, we use CMEM. +The datasets of Mitre are updated regularly. You may want to update them automatically via a command line in a bash file. In this script, we use eccenca Corporate Memory. 1. [Install CMEMC - a Command Line Interface of CMEM](../../../automate/cmemc-command-line-interface/installation/index.md) @@ -788,7 +788,7 @@ STIX uses JSON syntax and can therefore be converted to RDF via Corporate Memory ## Ressources * [RDF schemas (Model, pattern, etc)](RDF_model_and_pattern.drawio) -* [Archive of CMEM project](MITREATTCK_tutorial.zip) +* [Archive of Corporate Memory project](MITREATTCK_tutorial.zip) --- diff --git a/docs/build/tutorial-how-to-link-ids-to-osint/lift-data-from-YAML-data-of-hayabusa-sigma/index.md b/docs/build/tutorial-how-to-link-ids-to-osint/lift-data-from-YAML-data-of-hayabusa-sigma/index.md index ec1c1fa19..b6b15c5d6 100644 --- a/docs/build/tutorial-how-to-link-ids-to-osint/lift-data-from-YAML-data-of-hayabusa-sigma/index.md +++ b/docs/build/tutorial-how-to-link-ids-to-osint/lift-data-from-YAML-data-of-hayabusa-sigma/index.md @@ -11,7 +11,7 @@ Here, we are working with the Hayabusa/Sigma rules available via GitHub: - [https://github.com/Yamato-Security/hayabusa-rules](https://github.com/Yamato-Security/hayabusa-rules) - [https://github.com/SigmaHQ/sigma](https://github.com/Yamato-Security/hayabusa-rules) -The problem of interoperability, here, is the YAML format of files, their random position in their folders in their Github projets. Moreover, the same rule can exist in different projects but in this tutorial, we will not fix this problem and we consider the IRI rule is their Web address. In Corporate Memory, we would fix that with the Linked Tool, we will study this tool in a next part of this tutorial. +The problem of interoperability, here, is the YAML format of files, their random position in their folders in their Github projets. Moreover, the same rule can exist in different projects but in this tutorial, we will not fix this problem and we consider the IRI rule is their Web address. In eccenca Corporate Memory, we would fix that with the Linked Tool, we will study this tool in a next part of this tutorial. To build this knowledge graph of rules, we need to: diff --git a/docs/build/tutorial-how-to-link-ids-to-osint/link-IDS-event-to-KG-via-cmem/index.md b/docs/build/tutorial-how-to-link-ids-to-osint/link-IDS-event-to-KG-via-cmem/index.md index cc9e47626..e3ec796e9 100644 --- a/docs/build/tutorial-how-to-link-ids-to-osint/link-IDS-event-to-KG-via-cmem/index.md +++ b/docs/build/tutorial-how-to-link-ids-to-osint/link-IDS-event-to-KG-via-cmem/index.md @@ -4,7 +4,7 @@ In this tutorial, we are using the Splunk app "Investigate lateral movements with a knowledge graph", like example. This app contains several dasboards to help the analysts to navigate in the Hayabusa or Sigma alerts before searching in the Suricata and Sysmon alerts. We hope this method can "Accelerate Cyber Threat Hunting". -In the demo of this Splunk app via the video 1, the user selects the data about one investigation via Splunk and generate a bash script to export these data via the Splunk API in tempory graphs in Corporate Memory for each investigation. +In the demo of this Splunk app via the video 1, the user selects the data about one investigation via Splunk and generate a bash script to export these data via the Splunk API in tempory graphs in eccenca Corporate Memory for each investigation.
![Video 1: Splunk dashboards of the Splunk app "Investigate lateral movements with a knowledge graph"](splunk-app-demo-poc-app.gif) @@ -139,7 +139,7 @@ There are not consensus about the manner to calculate inferences on the RDF data We use two manners to calculate new inferences: -- when the inference is simple to calculate with SPARQL, we use a SPARQL update query with parameters in Corporate Memory (like "inferenceID" to build the name of destination tempory graph). "queryIRI" is the IRI of the query in the catalog of Corporate Memory. +- when the inference is simple to calculate with SPARQL, we use a SPARQL update query with parameters in eccenca Corporate Memory (like "inferenceID" to build the name of destination tempory graph). "queryIRI" is the IRI of the query in the catalog of Corporate Memory. - when the inference is complex to calculate, we use a workflow of Corporate Memory. With these tokens "source_1", "source_2", etc and "inferences" in the dashboard, the app can generate a bash script for CMEMC. @@ -180,7 +180,7 @@ In the previous chapter, you explain the role of token "source_x" to create a ne Here the example is simple with one external token, but when you have several external tokens in the token "source_x", there are often problems to generate a complet SPL query (to check the SPL query, you need to use the Javascript console via the Javascript "investigation.js" to read the final SPL queries in the tokens "source_x"). -You can add in your dashboard several tokens "source_1", "source_2", "source_3", etc. Each source generates a part of final bash script where a curl command requests the Splunk API and a CMEMC command executes the specified worflow via its ID in the token. With this method, the analyst is free to import any Splunk data and choose any CMEM workflow according to these data. The SPL queries are executed by the Splunk API (via curl), so the analyst is free to use all commands supported in Splunk to select the data. For example, with low-level investigation, these SPL queries contains also the selected period by the analyst to limit the quantity of data to import. +You can add in your dashboard several tokens "source_1", "source_2", "source_3", etc. Each source generates a part of final bash script where a curl command requests the Splunk API and a CMEMC command executes the specified worflow via its ID in the token. With this method, the analyst is free to import any Splunk data and choose any Corporate Memory workflow according to these data. The SPL queries are executed by the Splunk API (via curl), so the analyst is free to use all commands supported in Splunk to select the data. For example, with low-level investigation, these SPL queries contains also the selected period by the analyst to limit the quantity of data to import. ## Reasoning with data in Corporate Memory via Splunk diff --git a/docs/build/tutorial-how-to-link-ids-to-osint/link-IDS-event-to-KG/index.md b/docs/build/tutorial-how-to-link-ids-to-osint/link-IDS-event-to-KG/index.md index 776a74185..2a7d1b4c9 100644 --- a/docs/build/tutorial-how-to-link-ids-to-osint/link-IDS-event-to-KG/index.md +++ b/docs/build/tutorial-how-to-link-ids-to-osint/link-IDS-event-to-KG/index.md @@ -420,6 +420,6 @@ In the next page, we are using advanced tools in Coporate Memory to "Accelerate Tutorial: [how to link Intrusion Detection Systems (IDS) to Open-Source INTelligence (OSINT)](../index.md) -Next chapter: [Link IDS event to a knowledge graph in dashboards via inferences](../link-IDS-event-to-KG-via-cmem/index.md) (for the advanced users of Corporate Memory) +Next chapter: [Link IDS event to a knowledge graph in dashboards via inferences](../link-IDS-event-to-KG-via-cmem/index.md) (for the advanced users of eccenca Corporate Memory) Previous chapter: [Build a Knowledge Graph from indicators of compromise rules, like Hayabusa and Sigma rules](../lift-data-from-YAML-data-of-hayabusa-sigma/index.md) diff --git a/docs/consume/consume-graphs-in-apache-kafka/index.md b/docs/consume/consume-graphs-in-apache-kafka/index.md index a0e6d165e..fb964a4e4 100644 --- a/docs/consume/consume-graphs-in-apache-kafka/index.md +++ b/docs/consume/consume-graphs-in-apache-kafka/index.md @@ -12,7 +12,7 @@ tags: [Apache Kafka](https://kafka.apache.org/) is a distributed event store and stream-processing platform. Kafka is widely used in enterprises for data pipelines, streaming analytics, data integration and other applications. -By using the [cmem-plugin-kafka](https://pypi.org/project/cmem-plugin-kafka/) [Python Plugin](../../develop/python-plugins/index.md), you can produce and send messages to Apache Kafka from inside of our Corporate Memory Workflows. +By using the [cmem-plugin-kafka](https://pypi.org/project/cmem-plugin-kafka/) [Python Plugin](../../develop/python-plugins/index.md), you can produce and send messages to Apache Kafka from inside of our eccenca Corporate Memory Workflows. ## Installation diff --git a/docs/consume/consuming-graphs-in-power-bi/index.md b/docs/consume/consuming-graphs-in-power-bi/index.md index 68f2d7a8b..aea5bfe88 100644 --- a/docs/consume/consuming-graphs-in-power-bi/index.md +++ b/docs/consume/consuming-graphs-in-power-bi/index.md @@ -8,7 +8,7 @@ tags: ## Introduction -Learn how to consume data from your Corporate Memory Knowledge Graph with our Microsoft Power-BI-Connector. +Learn how to consume data from your eccenca Corporate Memory Knowledge Graph with our Microsoft Power-BI-Connector. This manual and tutorial describes how you can consume data from your knowledge graph in Microsoft Power BI through our Corporate Memory Power-BI-Connector. diff --git a/docs/consume/index.md b/docs/consume/index.md index 6e4278ee9..75189de79 100644 --- a/docs/consume/index.md +++ b/docs/consume/index.md @@ -9,7 +9,7 @@ hide: # :material-star: Consume -This section outlines how to consume data from Corporate Memory Knowledge Graphs. +This section outlines how to consume data from eccenca Corporate Memory Knowledge Graphs. While there are several options to retrieve information from the Knowledge Graph, the most direct way is to issue SPARQL queries. SPARQL queries can be managed and executed in the Query Module UI. External applications may access the query catalog and execute queries through the REST API directly or more conveniently by using the [cmemc - Command Line Interface](../automate/cmemc-command-line-interface/index.md). diff --git a/docs/consume/provide-data-in-any-format-via-a-custom-api/index.md b/docs/consume/provide-data-in-any-format-via-a-custom-api/index.md index 4ac61c3d0..426d71f2b 100644 --- a/docs/consume/provide-data-in-any-format-via-a-custom-api/index.md +++ b/docs/consume/provide-data-in-any-format-via-a-custom-api/index.md @@ -9,7 +9,7 @@ tags: ## Introduction -Learn how to provide data via a customized Corporate Memory API in a text format of your choice and how to consume it in your applications. +Learn how to provide data via a customized eccenca Corporate Memory API in a text format of your choice and how to consume it in your applications. This tutorial describes how you can provide data in a text format of your choice via your own custom Corporate Memory API, and how you request those APIs. In this tutorial, we describe how you can set up an endpoint which provides [iCalendar data](https://en.wikipedia.org/wiki/ICalendar). @@ -58,7 +58,7 @@ WHERE { As a next step, we will define a template that generates iCalendar data from our previously defined SPARQL query. -Select in *Graphs* the CMEM Query Catalog graph, select in *Navigation* the Select Result Template and click `Create a new Select Result Template` to create a new template. +Select in *Graphs* the Corporate Memory Query Catalog graph, select in *Navigation* the Select Result Template and click `Create a new Select Result Template` to create a new template. ![result-template](22-1-2-result-template.png) @@ -108,7 +108,7 @@ END:VCALENDAR As a next step, we will set up the API which serves the data in the format we defined in the previous template. -Select in *Graphs* the CMEM Query Catalog graph, select in *Navigation* the Select Query Endpoint and click "Create a new Select Query Endpoint" to create a new endpoint. +Select in *Graphs* the Corporate Memory Query Catalog graph, select in *Navigation* the Select Query Endpoint and click "Create a new Select Query Endpoint" to create a new endpoint. ![query-endpoint](22-1-3-query-endpoint.png) diff --git a/docs/deploy-and-configure/configuration/caveats/index.md b/docs/deploy-and-configure/configuration/caveats/index.md index 322f2b9d2..a8239e4c0 100644 --- a/docs/deploy-and-configure/configuration/caveats/index.md +++ b/docs/deploy-and-configure/configuration/caveats/index.md @@ -25,7 +25,7 @@ See [GraphDB technical-requirements](https://graphdb.ontotext.com/documentation/ ## Load Balancer -Depending on the deployment, load balancers or proxies in between Corporate Memory components (such as Build (DataIntegration) <-> Explore backend, Explore backend <-> Triplestore) tend to drop long running TCP connections when they are idle. +Depending on the deployment, load balancers or proxies in between eccenca Corporate Memory components (such as Build (DataIntegration) <-> Explore backend, Explore backend <-> Triplestore) tend to drop long running TCP connections when they are idle. As e.g. SPARQL Update requests may be idle for a long time (while the update is performed) the client will not receive the response. Hence, DI workflow execution will not proceed even though the update went through. diff --git a/docs/deploy-and-configure/configuration/dataintegration/index.md b/docs/deploy-and-configure/configuration/dataintegration/index.md index 61e5bac69..f742ea6a4 100644 --- a/docs/deploy-and-configure/configuration/dataintegration/index.md +++ b/docs/deploy-and-configure/configuration/dataintegration/index.md @@ -115,7 +115,7 @@ The following sections describe the available workspace provider plugins and how ### RDF-store Workspace - backend -When running in Corporate Memory, by default the workspace is held in the RDF store configured in the eccenca Explore. +When running in eccenca Corporate Memory, by default the workspace is held in the RDF store configured in the eccenca Explore. The workspace is held using the eccenca Explore backend (DataPlatform), i.e., it requires the `eccencaDataPlatform.url` parameter to be configured. diff --git a/docs/deploy-and-configure/configuration/dataintegration/jdbc/index.md b/docs/deploy-and-configure/configuration/dataintegration/jdbc/index.md index 2106b99cb..30ae8f584 100644 --- a/docs/deploy-and-configure/configuration/dataintegration/jdbc/index.md +++ b/docs/deploy-and-configure/configuration/dataintegration/jdbc/index.md @@ -5,7 +5,7 @@ tags: --- # Setup and use of JDBC Drivers -Corporate Memory supports JDBC connections to database management systems (DBMSs). +eccenca Corporate Memory supports JDBC connections to database management systems (DBMSs). The platform includes several JDBC drivers by default. You can also add and use custom drivers. diff --git a/docs/deploy-and-configure/configuration/docker-orchestration/index.md b/docs/deploy-and-configure/configuration/docker-orchestration/index.md index 04f4efe52..3146eef5b 100644 --- a/docs/deploy-and-configure/configuration/docker-orchestration/index.md +++ b/docs/deploy-and-configure/configuration/docker-orchestration/index.md @@ -15,7 +15,7 @@ In this document we provide an overview on how the environment files are loaded, ## Environment Files: Loading Sequence The environment files are supplied in the CONFIGFILE environment variable to the make targets inside the orchestration. -For example, in [Scenario: Single Node Cloud Installation](../../installation/scenario-single-node-cloud-installation/index.md) we have created a `prod.env` environment file and created the Corporate Memory instance using `prod.env` configuration: +For example, in [Scenario: Single Node Cloud Installation](../../installation/scenario-single-node-cloud-installation/index.md) we have created a `prod.env` environment file and created the eccenca Corporate Memory instance using `prod.env` configuration: ``` shell-session CONFIGFILE=environments/prod.env make clean-pull-start-bootstrap diff --git a/docs/deploy-and-configure/configuration/explore/dataplatform/application-full.md b/docs/deploy-and-configure/configuration/explore/dataplatform/application-full.md index 1eb842b9d..dbb4cd883 100644 --- a/docs/deploy-and-configure/configuration/explore/dataplatform/application-full.md +++ b/docs/deploy-and-configure/configuration/explore/dataplatform/application-full.md @@ -313,19 +313,19 @@ Use this property to enable or disable the AI capabilities of Explore Changeable configuration settings of the companion mcp server and mcp client integration. Explore can integrate external mcp servers via plain spring ai mcp client configuration -and CMEM MCP servers in the authentication realm of the companion via spring.ai.mcp.client.cmem properties +and eccenca Corporate Memory MCP servers in the authentication realm of the companion via spring.ai.mcp.client.cmem properties Every connection is registered under a name and the tools of a connection are exposed to the LLM prefixed with that name, so that equally named tools of different servers stay distinguishable: external mcp servers: external__ - CMEM MCP servers: cmem__ + Corporate Memory MCP servers: cmem__ Since the complete tool name must not exceed 64 characters, keep the connection names short. ***Property: spring.ai.mcp.client.cmem*** -CMEM MCP Servers requiring bearer token authentication in same realm are configured here +Corporate Memory MCP Servers requiring bearer token authentication in same realm are configured here Both SSE and streamable connections are supported. -The configurations under CMEM are the same as Spring AI mcp client configuration. +The configurations under Corporate Memory are the same as Spring AI mcp client configuration. The name of a connection ("build" in the examples below) is part of the tool names. For instance for Streamable: spring.ai.mcp.client.cmem.streamableConnections.build.url= diff --git a/docs/deploy-and-configure/configuration/explore/dataplatform/application-graphdb-full.md b/docs/deploy-and-configure/configuration/explore/dataplatform/application-graphdb-full.md index fc01381a6..9fcde40c1 100644 --- a/docs/deploy-and-configure/configuration/explore/dataplatform/application-graphdb-full.md +++ b/docs/deploy-and-configure/configuration/explore/dataplatform/application-graphdb-full.md @@ -8,7 +8,7 @@ tags: Configuration example: This example configures a connection with HTTPS to a remote graphdb store () using the workbench import directory -which is shared with the GraphDB instance. The repository will be created on startup of CMEM. +which is shared with the GraphDB instance. The repository will be created on startup of eccenca Corporate Memory. ```yaml store: diff --git a/docs/deploy-and-configure/configuration/explore/dataplatform/application-neptune-full.md b/docs/deploy-and-configure/configuration/explore/dataplatform/application-neptune-full.md index 2f11537c0..06114689a 100644 --- a/docs/deploy-and-configure/configuration/explore/dataplatform/application-neptune-full.md +++ b/docs/deploy-and-configure/configuration/explore/dataplatform/application-neptune-full.md @@ -8,9 +8,9 @@ tags: Configuration example: This example configures a connection to a neptune instance in the AWS region eu-central-1. Authentication is enabled -so it is assumed that CMEM runs on a EC2 VM with configured role for authentication to neptune. Files (uncompressed) greater than 100MB are +so it is assumed that eccenca Corporate Memory runs on a EC2 VM with configured role for authentication to neptune. Files (uncompressed) greater than 100MB are uploaded via S3 based bulk loader. The S3 bucket is accessed in this case via an access point which is configured here. The EC2 -role CMEM runs under has write access to the bucket. One of the role the neptune cluster runs under is configured in this setting and has read access to the bucket. +role Corporate Memory runs under has write access to the bucket. One of the role the neptune cluster runs under is configured in this setting and has read access to the bucket. On bulk load the loading runs parallel in the setting HIGH which causes higher cpu load but better performance. Also the example disables DPs generation of tracing IDs by micrometer tracing - Neptune needs UUIDs as IDs for queries etc. @@ -98,7 +98,7 @@ Settings for S3 bucket connection and upload of large files to the neptune insta ***Property: store.neptune.s3.bucketNameOrAPAlias*** -The name of the bucket or access point -> the role CMEM runs under needs write access to the bucket +The name of the bucket or access point -> the role Corporate Memory runs under needs write access to the bucket | Category | Value | |--- | ---: | diff --git a/docs/deploy-and-configure/configuration/graphinsights/index.md b/docs/deploy-and-configure/configuration/graphinsights/index.md index 581a370d1..9e04e6602 100644 --- a/docs/deploy-and-configure/configuration/graphinsights/index.md +++ b/docs/deploy-and-configure/configuration/graphinsights/index.md @@ -12,7 +12,7 @@ Follow the instructions related to your deployment type: a) docker-compose or b) ### (a) Enable in docker-compose deployment -In our Corporate Memory docker-orchestration all main configurations can be directed by setting environment +In our eccenca Corporate Memory docker-orchestration all main configurations can be directed by setting environment variables in `environments/config.env`. You can find the environment variables set as usual in `environments/default.env` and `environments/config.env`. @@ -325,7 +325,7 @@ accordingly: ``` yaml global: # GraphInsights service account OAuth credentials (if using GraphInsights). - # Can use the same credentials as CMEM or separate ones. + # Can use the same credentials as Corporate Memory or separate ones. graphinsightsClientId: graph-insights-service-account graphinsightsClientSecret: changeme # IMPORTANT: Change this to a secure value! diff --git a/docs/deploy-and-configure/configuration/keycloak/change-passwords-and-keys/index.md b/docs/deploy-and-configure/configuration/keycloak/change-passwords-and-keys/index.md index 8eed7ed7a..62eb2d5d9 100644 --- a/docs/deploy-and-configure/configuration/keycloak/change-passwords-and-keys/index.md +++ b/docs/deploy-and-configure/configuration/keycloak/change-passwords-and-keys/index.md @@ -34,7 +34,7 @@ Set a new password. ## Change credentials of cmem-service-account -Make sure the realm Cmem is selected, go to Clients in left sidebar and edit cmem-service-account: +Make sure the realm `cmem` is selected, go to Clients in left sidebar and edit the `cmem-service-account`: ![cmem-selection](22-1-cmem-selection.png) @@ -44,9 +44,9 @@ Switch to "Credentials" tab and press "Regenerate Secret" Button. ## Change credentials of user accounts -In default configuration, there are two users: user and admin. Both are configured with different groups to have different permissions inside Corporate Memory. +In default configuration, there are two users: user and admin. Both are configured with different groups to have different permissions inside eccenca Corporate Memory. -To change the default passwords, select the Cmem Realm and open Users in the left sidebar: +To change the default passwords, select the `cmem` realm and open Users in the left sidebar: ![users-lookup](22-1-users-lookup.png) diff --git a/docs/deploy-and-configure/configuration/keycloak/index.md b/docs/deploy-and-configure/configuration/keycloak/index.md index 975066327..44c2a9754 100644 --- a/docs/deploy-and-configure/configuration/keycloak/index.md +++ b/docs/deploy-and-configure/configuration/keycloak/index.md @@ -8,7 +8,7 @@ tags: ## Introduction -This page describes important steps in order to configure Keycloak as an authentication backend for Corporate Memory. +This page describes important steps in order to configure Keycloak as an authentication backend for eccenca Corporate Memory. The screenshots displayed in this documentation were taken from Keycloak v20 using the `keycloak.v2` theme. !!! info diff --git a/docs/deploy-and-configure/configuration/keycloak/using-external-keycloak/index.md b/docs/deploy-and-configure/configuration/keycloak/using-external-keycloak/index.md index 9dc583584..32a5040e3 100644 --- a/docs/deploy-and-configure/configuration/keycloak/using-external-keycloak/index.md +++ b/docs/deploy-and-configure/configuration/keycloak/using-external-keycloak/index.md @@ -4,11 +4,11 @@ tags: - Security - Keycloak --- -# Configure Corporate Memory with an external Keycloak +# Configure eccenca Corporate Memory with an external Keycloak ## Introduction -Maybe you already operate a central Keycloak deployment in your infrastructure or you want to deploy multiple stages of Corporate Memory with a single Keycloak. +Maybe you already operate a central Keycloak deployment in your infrastructure or you want to deploy multiple stages of eccenca Corporate Memory with a single Keycloak. Very often this results in a Keycloak which is deployed in a different domain than your Corporate Memory (such as Corporate Memory is available on `https://cmem.example.com` and Keycloak is available on `https://keycloak.example.com`). For this scenario, this page provides additional configuration requirements. @@ -23,7 +23,7 @@ Depending on your infrastructure around Corporate Memory, you need to change som - Headers for Corporate Memory URLs: - `Access-Control-Allow-Origin: *` -For example, if you are using our helm charts, adapt the followin ingress annotations: +For example, if you are using our helm charts, adapt the following ingress annotations: ``` yaml # KEYCLOAK ingress diff --git a/docs/deploy-and-configure/configuration/production-ready-settings/index.md b/docs/deploy-and-configure/configuration/production-ready-settings/index.md index cc6942189..edf98c040 100644 --- a/docs/deploy-and-configure/configuration/production-ready-settings/index.md +++ b/docs/deploy-and-configure/configuration/production-ready-settings/index.md @@ -5,7 +5,7 @@ tags: --- # Production-Ready Settings -If you plan to deploy Corporate Memory in a non-trusted environment, you need to take care about some final configuration steps. +If you plan to deploy eccenca Corporate Memory in a non-trusted environment, you need to take care about some final configuration steps. ## Restrict Redirect URLs diff --git a/docs/deploy-and-configure/configuration/quad-store-configuration/index.md b/docs/deploy-and-configure/configuration/quad-store-configuration/index.md index 18171cf2f..9553da0c9 100644 --- a/docs/deploy-and-configure/configuration/quad-store-configuration/index.md +++ b/docs/deploy-and-configure/configuration/quad-store-configuration/index.md @@ -156,7 +156,7 @@ xsd:unsignedShort "42"^^xsd:integer . xsd:unsignedByte "42"^^xsd:integer . ``` -If data is to be copied between CMEM setups backed by Stardog, the `index.literals.canonical` options of the corresponding databases must be set to the same value on both setups. +If data is to be copied between eccenca Corporate Memory setups backed by Stardog, the `index.literals.canonical` options of the corresponding databases must be set to the same value on both setups. It is recommended to only turn this canonicalization off when it is strictly necessary, due to a negative impact on database performance without it. diff --git a/docs/deploy-and-configure/configuration/reverse-proxy/index.md b/docs/deploy-and-configure/configuration/reverse-proxy/index.md index 13b040b64..244459cbd 100644 --- a/docs/deploy-and-configure/configuration/reverse-proxy/index.md +++ b/docs/deploy-and-configure/configuration/reverse-proxy/index.md @@ -4,7 +4,7 @@ tags: --- # Reverse Proxy -A reverse proxy forwards all requests from the users to the called service and returns the result to the users. Corporate Memory is tested with an Apache HTTP server as a reverse proxy. +A reverse proxy forwards all requests from the users to the called service and returns the result to the users. Eccenca Corporate Memory is tested with an Apache HTTP server as a reverse proxy. Reverse proxy is a necessary component in the Corporate Memory deployment. It enables you to: diff --git a/docs/deploy-and-configure/installation/scenario-k8s-deployment/index.md b/docs/deploy-and-configure/installation/scenario-k8s-deployment/index.md index 6aa008a85..88fe4e98b 100644 --- a/docs/deploy-and-configure/installation/scenario-k8s-deployment/index.md +++ b/docs/deploy-and-configure/installation/scenario-k8s-deployment/index.md @@ -5,7 +5,7 @@ icon: simple/kubernetes ## Introduction -This page describes the basic principles of installing Corporate Memory in a +This page describes the basic principles of installing eccenca Corporate Memory in a Kubernetes cluster with `helm` and `kubectl`. It will not explain the basic principles of Kubernetes or help in installing the required tools. diff --git a/docs/deploy-and-configure/installation/scenario-local-installation/index.md b/docs/deploy-and-configure/installation/scenario-local-installation/index.md index e8e8cbf78..6959a9fea 100644 --- a/docs/deploy-and-configure/installation/scenario-local-installation/index.md +++ b/docs/deploy-and-configure/installation/scenario-local-installation/index.md @@ -33,7 +33,7 @@ Install the requirements gnupg lsb-release gettext zip unzip git \ make=4.3-4.1 vim jq ``` - To install Corporate Memory, you need to modify your local hosts file (located in /etc/hosts), minimal configuration is as follows: + To install eccenca Corporate Memory, you need to modify your local hosts file (located in /etc/hosts), minimal configuration is as follows: ```shell ## diff --git a/docs/deploy-and-configure/installation/scenario-single-node-cloud-installation/index.md b/docs/deploy-and-configure/installation/scenario-single-node-cloud-installation/index.md index c257fd950..63fcf1945 100644 --- a/docs/deploy-and-configure/installation/scenario-single-node-cloud-installation/index.md +++ b/docs/deploy-and-configure/installation/scenario-single-node-cloud-installation/index.md @@ -53,7 +53,7 @@ sudo apt-get install docker-ce docker-ce-cli containerd.io \ ## Installation -Corporate Memory uses Ontotext GraphDB triple store as default backend. +eccenca Corporate Memory uses Ontotext GraphDB triple store as default backend. Graphdb is available as free version and does not requires a license. You need to copy your license for Ontotext GraphDB to the `license` folder inside Corporate Memory's root folder. diff --git a/docs/develop/accessing-graphs-with-java-applications/index.md b/docs/develop/accessing-graphs-with-java-applications/index.md index 035f6c4a7..83dd35d5f 100644 --- a/docs/develop/accessing-graphs-with-java-applications/index.md +++ b/docs/develop/accessing-graphs-with-java-applications/index.md @@ -9,7 +9,7 @@ hide: ## Introduction -This short recipe covers how to connect to Corporate Memory using a Java program. +This short recipe covers how to connect to eccenca Corporate Memory using a Java program. Such program can connect to Corporate Memory at any time autonomously, independently of whether a user is logged in or not. ## Java Example diff --git a/docs/develop/cmemc-scripts/index.md b/docs/develop/cmemc-scripts/index.md index 034396a9a..1af35b446 100644 --- a/docs/develop/cmemc-scripts/index.md +++ b/docs/develop/cmemc-scripts/index.md @@ -90,7 +90,7 @@ for workflow in cmemc(command): ## Using a shebang to create an executable file -As a nice addon, you could extend your script with a [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) to start [uv](https://docs.astral.sh/uv/). +As a nice add on, you could extend your script with a [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) to start [uv](https://docs.astral.sh/uv/). This will also install and manage dependencies and python versions for you: The complete script looks like this: diff --git a/docs/develop/index.md b/docs/develop/index.md index 458f9a4dc..455eb899e 100644 --- a/docs/develop/index.md +++ b/docs/develop/index.md @@ -13,13 +13,13 @@ API documentation and programming recipes. --- - [Accessing Graphs with Java Applications](accessing-graphs-with-java-applications/index.md) covers how to connect to Corporate Memory using a Java program. + [Accessing Graphs with Java Applications](accessing-graphs-with-java-applications/index.md) covers how to connect to eccenca Corporate Memory using a Java program. - :material-language-python: Python --- - For Python developers, we offer a [Plugin SDK](python-plugins/index.md) as well as an API for accessing and manipulating Corporate Memory Instances ([cmem-cmempy](cmempy-python-api/index.md)). + For Python developers, we offer a [Plugin SDK](python-plugins/index.md) as well as an API for accessing and manipulating eccenca Corporate Memory Instances ([cmem-cmempy](cmempy-python-api/index.md)). - :material-shopping: Marketplace Packages diff --git a/docs/develop/packages/development/index.md b/docs/develop/packages/development/index.md index eb3b8b11a..4f053e5e5 100644 --- a/docs/develop/packages/development/index.md +++ b/docs/develop/packages/development/index.md @@ -9,7 +9,7 @@ tags: ## Introduction -Marketplace Packages are archives that bundle content, functionality, and configuration from Corporate Memory for sharing and reuse. +Marketplace Packages are archives that bundle content, functionality, and configuration from eccenca Corporate Memory for sharing and reuse. Each package has its own release cycle. Packages can be installed and uninstalled during runtime. diff --git a/docs/develop/packages/development/tutorial/index.md b/docs/develop/packages/development/tutorial/index.md index fdf4720b4..bd9cdbcda 100644 --- a/docs/develop/packages/development/tutorial/index.md +++ b/docs/develop/packages/development/tutorial/index.md @@ -43,7 +43,7 @@ You should now have a folder with two levels of files: The nested folder `my-package-id` represents your working directory for developing the package. -To add content to the package, simply copy the files you want to add into this folder, or extract existing content from a live Corporate Memory instance into the working directory. +To add content to the package, simply copy the files you want to add into this folder, or extract existing content from a live eccenca Corporate Memory instance into the working directory. !!! example "Extracting Corporate Memory content to add to the package" diff --git a/docs/develop/packages/installation/index.md b/docs/develop/packages/installation/index.md index 49788a23a..62d121313 100644 --- a/docs/develop/packages/installation/index.md +++ b/docs/develop/packages/installation/index.md @@ -9,7 +9,7 @@ tags: ## Introduction -Marketplace Packages can be installed directly from a Corporate Memory Marketplace Server (e.g. [https://eccenca.market](https://eccenca.market)), or from local **C**orporate Memory **P**ackage **A**rchives (`.cpa` files) and package directories. +Marketplace Packages can be installed directly from the eccenca Corporate Memory Marketplace Server (e.g. [https://eccenca.market](https://eccenca.market)), or from local **C**orporate Memory **P**ackage **A**rchives (`.cpa` files) and package directories. This page describes how to search, install, list, and uninstall Marketplace Packages using `cmemc`. diff --git a/docs/develop/python-plugins/development/index.md b/docs/develop/python-plugins/development/index.md index 0c9c13ad7..f57ffd849 100644 --- a/docs/develop/python-plugins/development/index.md +++ b/docs/develop/python-plugins/development/index.md @@ -19,7 +19,7 @@ This page gives an overview of the concepts you need to understand in order to d ## Base Package -`cmem-plugin-base` is a Python library that provides a set of base classes for developing plugins for the eccenca Corporate Memory (CMEM) platform. These base classes provide a consistent interface for defining new plugins, handling configuration, and communicating with the Build (DataIntegration) of CMEM. +`cmem-plugin-base` is a Python library that provides a set of base classes for developing plugins for the eccenca Corporate Memory platform. These base classes provide a consistent interface for defining new plugins, handling configuration, and communicating with the Build (DataIntegration) of Corporate Memory. ## Plugin Types @@ -672,4 +672,4 @@ Python’s [concurrent.futures.ProcessPoolExecutor](https://docs.python.org/3/li In contrast, Python’s [concurrent.futures.ThreadPoolExecutor](https://docs.python.org/3/library/concurrent.futures.html#threadpoolexecutor) does not encounter these issues. It uses threads that share the same memory space and operate within a single process, avoiding the need for subprocess creation. -**Recommendation:** Always use `ThreadPoolExecutor` in CMEM Python plugins running under JEP, as `ProcessPoolExecutor` may cause deadlocks. +**Recommendation:** Always use `ThreadPoolExecutor` in Corporate Memory Python plugins running under JEP, as `ProcessPoolExecutor` may cause deadlocks. diff --git a/docs/explore-and-author/bke-module/visually-authoring-ontologies/index.md b/docs/explore-and-author/bke-module/visually-authoring-ontologies/index.md index fcc002f0e..f7f9b1d36 100644 --- a/docs/explore-and-author/bke-module/visually-authoring-ontologies/index.md +++ b/docs/explore-and-author/bke-module/visually-authoring-ontologies/index.md @@ -11,7 +11,7 @@ tags: This beginner-level tutorial shows how to use Business Knowledge Editor to visually create new ontology (vocabulary) **classes** and **properties** (object properties and datatype properties). -There are other ways to create new classes and properties in Corporate Memory, for example by using SHACL shapes. Business Knowledge Editor provides an intuitive diagram-based approach that simplifies this process. +There are other ways to create new classes and properties in eccenca Corporate Memory, for example by using SHACL shapes. Business Knowledge Editor provides an intuitive diagram-based approach that simplifies this process. The tutorial consists of the following steps, which are described in detail below: diff --git a/docs/explore-and-author/companion/index.md b/docs/explore-and-author/companion/index.md index 7af251116..1c7b61876 100644 --- a/docs/explore-and-author/companion/index.md +++ b/docs/explore-and-author/companion/index.md @@ -52,7 +52,7 @@ To maximize the relevance and accuracy of the generated answer, your question is ![Companion Tool Selection](companion-tool-selection.png){ class="bordered" width="40%" } -The companion chat uses various tools to interact with Corporate Memory. +The companion chat uses various tools to interact with eccenca Corporate Memory. These tools are used autonomously by the configured LLM model to gather the relevant context needed to generate the best answer. If your use case or question requires you to limit the available tools (e.g. if you only want to use queries from the query catalogue and not generate any), you can configure the tools the model can use via the drop-down widget. diff --git a/docs/explore-and-author/embedding-services-via-the-integrations-module/index.md b/docs/explore-and-author/embedding-services-via-the-integrations-module/index.md index 730161242..3ddeab934 100644 --- a/docs/explore-and-author/embedding-services-via-the-integrations-module/index.md +++ b/docs/explore-and-author/embedding-services-via-the-integrations-module/index.md @@ -9,7 +9,7 @@ tags: This module is not activated by default and can be configured in the application view configuration. -The **Service integrations** module embeds external web applications directly into the Corporate Memory user interface. +The **Service integrations** module embeds external web applications directly into the eccenca Corporate Memory user interface. Instead of switching to a separate tool, users open the integrated service from the main navigation and work with it without leaving their Application view. A typical use case is a dashboarding service that visualizes data from your Enterprise Knowledge Graph. diff --git a/docs/explore-and-author/graph-exploration/building-a-customized-user-interface/index.md b/docs/explore-and-author/graph-exploration/building-a-customized-user-interface/index.md index 6139bbb2e..141c5cd9d 100644 --- a/docs/explore-and-author/graph-exploration/building-a-customized-user-interface/index.md +++ b/docs/explore-and-author/graph-exploration/building-a-customized-user-interface/index.md @@ -18,14 +18,14 @@ You can define forms using SHACL rules. The rules state: 3. Which other, linked resources are shown in the form. Linked resources can either be shown as links or as their full form. 4. Which texts are used to name and describe fields, as well as the tab in the user interface. -Forms are defined in the CMEM Shapes Catalog graph. The graph URI is `https://vocab.eccenca.com/shacl/`. +Forms are defined in the eccenca Corporate Memory Shapes Catalog graph. The graph URI is `https://vocab.eccenca.com/shacl/`. Form definitions are twofold: 1. The form itself is defined as so called `NodeShape`. NodeShapes define which types of resources the form applies to (the target class), and which fields are shown in the form (the Properties). 2. The individual fields are defined as so called `PropertyShape`. PropertyShapes define which property is used to retrieve data for the field (the path), the name of the field, a description, its cardinality (min and max count), its position in the form (the order), and if it should always be shown. In case of object properties, it also defines the type of the linked resource (the class). The full list of features is described in [PropertyShapes](property-shapes/index.md). -To define a new form, for example for `foaf:Person` resources, navigate to the CMEM Shapes Catalog graph and select `NodeShape` in Navigation. The list of existing NodeShapes is shown. Click "Create a new SHACL Node shape" in the upper right to create a new NodeShape. Enter a name of the resource. An empty NodeShape resource is created and shown. +To define a new form, for example for `foaf:Person` resources, navigate to the Corporate Memory Shapes Catalog graph and select `NodeShape` in Navigation. The list of existing NodeShapes is shown. Click "Create a new SHACL Node shape" in the upper right to create a new NodeShape. Enter a name of the resource. An empty NodeShape resource is created and shown. ![](./createNodeShape.png){ class="bordered" } @@ -37,7 +37,7 @@ You have now created an "empty" form that covers `foaf:Person` resources with ![](./nodeshape.png){ class="bordered" } -To define new fields, for example showing the email address of the person (defined as `foaf:mbox`), navigate to the CMEM Shapes Catalog graph and select `PropertyShape` in Navigation. The list of existing PropertyShapes is shown. Click CREATE NEW PROPERTYSHAPE in the upper right to create a new PropertyShape. Enter a name of the resource. An empty PropertyShape resource is created and shown. +To define new fields, for example showing the email address of the person (defined as `foaf:mbox`), navigate to the Corporate Memory Shapes Catalog graph and select `PropertyShape` in Navigation. The list of existing PropertyShapes is shown. Click CREATE NEW PROPERTYSHAPE in the upper right to create a new PropertyShape. Enter a name of the resource. An empty PropertyShape resource is created and shown. Edit the form using ![](./ic_mode_edit_black_18dp_1x.png). A form is shown with all relevant properties of a field definition. Required in this step are: diff --git a/docs/explore-and-author/graph-exploration/graph-insights/index.md b/docs/explore-and-author/graph-exploration/graph-insights/index.md index 6f0e8488c..f88e97b7b 100644 --- a/docs/explore-and-author/graph-exploration/graph-insights/index.md +++ b/docs/explore-and-author/graph-exploration/graph-insights/index.md @@ -60,4 +60,4 @@ The **user guide** presents the visual analysis workflow of Graph Insights. It d - **Interaction:** [Groups](features/groups.md), [Connections](features/connections.md), and [Details](features/objects.md#object-details). - **Analysis:** [Histograms](features/groups.md#histograms) and [Persistence](features/persistence.md). -4. **[Platform Integration](navigating-to-cmem.md):** Learn how to seamlessly jump from a graph node to other Corporate Memory views. +4. **[Platform Integration](navigating-to-cmem.md):** Learn how to seamlessly jump from a graph node to other eccenca Corporate Memory views. diff --git a/docs/explore-and-author/graph-exploration/graph-insights/navigating-to-cmem.md b/docs/explore-and-author/graph-exploration/graph-insights/navigating-to-cmem.md index 4f25c4ade..ceb9bbf86 100644 --- a/docs/explore-and-author/graph-exploration/graph-insights/navigating-to-cmem.md +++ b/docs/explore-and-author/graph-exploration/graph-insights/navigating-to-cmem.md @@ -4,9 +4,9 @@ tags: - GraphInsights --- -# Navigating to Corporate Memory +# Navigating to eccenca Corporate Memory -Graph Insights allows you to seamlessly jump from your visual analysis directly back to the source records in Corporate Memory. This creates a smooth transition from a high-level exploration to operational data management. +Graph Insights allows you to seamlessly jump from your visual analysis directly back to the source records in eccenca Corporate Memory. This creates a smooth transition from a high-level exploration to operational data management. --- diff --git a/docs/explore-and-author/index.md b/docs/explore-and-author/index.md index fb0741744..963de7a36 100644 --- a/docs/explore-and-author/index.md +++ b/docs/explore-and-author/index.md @@ -10,7 +10,7 @@ hide: # :material-star: Explore -In the Explore section you will learn how Corporate Memory allows you to interact with your Enterprise Knowledge Graph. +In the Explore section you will learn how eccenca Corporate Memory allows you to interact with your Enterprise Knowledge Graph. Exploring includes authoring: besides browsing, searching and visualizing, the modules described here let you create, edit and curate graph content. All relevant modules and functionalities are described. You will also learn how we make use of [SHACL Shapes](https://www.w3.org/TR/shacl/) in order to [customize the way how you can interact with your data](./graph-exploration/building-a-customized-user-interface/index.md). diff --git a/docs/explore-and-author/link-rules/index.md b/docs/explore-and-author/link-rules/index.md index 3533d02b3..9437f0539 100644 --- a/docs/explore-and-author/link-rules/index.md +++ b/docs/explore-and-author/link-rules/index.md @@ -10,7 +10,7 @@ tags: The Link Rules provides mechanisms to simplify creating data linking and to imposes role specific workflows over the whole process. -Linking tasks allow the creation of links between resources based on rules in the Corporate Memory Build component. Such a linking task demands the configuration of source and target input resource selections (dataset, resource type or additional restrictions), the link type and an output dataset. These configurations demand a thorough understanding of your Knowledge Graph internals and may become a repetitive task. The Link rules allows to streamline this process in a way that also users with limited understanding of the knowledge graph can create link rules based on pre-defined templates. +Linking tasks allow the creation of links between resources based on rules in the eccenca Corporate Memory Build component. Such a linking task demands the configuration of source and target input resource selections (dataset, resource type or additional restrictions), the link type and an output dataset. These configurations demand a thorough understanding of your Knowledge Graph internals and may become a repetitive task. The Link rules allows to streamline this process in a way that also users with limited understanding of the knowledge graph can create link rules based on pre-defined templates. ## Usage @@ -103,7 +103,7 @@ This access conditions is used by the Link Rules module to grant write access to !!! info - It is currently not possible to set a *Access Condition Identifier* nor to simply retrieve the IRI of an existing access condition. Hence the admin needs to retrieve the IRI of this access condition from the CMEM Access Conditions graph. + It is currently not possible to set a *Access Condition Identifier* nor to simply retrieve the IRI of an existing access condition. Hence the admin needs to retrieve the IRI of this access condition from the Corporate Memory Access Conditions graph. In order to enable users to use the Link Rules Module, the following must be allowed (this can be granted in this rule or be defined separately): diff --git a/docs/explore-and-author/workspace-configuration/index.md b/docs/explore-and-author/workspace-configuration/index.md index 639fa07ec..979ba41d8 100644 --- a/docs/explore-and-author/workspace-configuration/index.md +++ b/docs/explore-and-author/workspace-configuration/index.md @@ -6,7 +6,7 @@ tags: --- # Application view -An Application view determines which modules are available in the Corporate Memory +An Application view determines which modules are available in the eccenca Corporate Memory user interface. The Application view configuration module lets you select the Application view you work in, configure its details, and create or delete Application views. diff --git a/docs/getting-started/index.md b/docs/getting-started/index.md index 6ea5e7acf..ef4464aac 100644 --- a/docs/getting-started/index.md +++ b/docs/getting-started/index.md @@ -8,7 +8,7 @@ tags: ## Introduction -This page describes how to work with Corporate Memory and shortly outlines all functionalities of the user interface. +This page describes how to work with eccenca Corporate Memory and shortly outlines all functionalities of the user interface. For the installation and configuration of Corporate Memory refer to the [☆ Deploy and Configure](../deploy-and-configure/index.md) section. !!! info diff --git a/docs/release-notes/corporate-memory-26-2/index.md b/docs/release-notes/corporate-memory-26-2/index.md index be5d3ef1f..424ec7edf 100644 --- a/docs/release-notes/corporate-memory-26-2/index.md +++ b/docs/release-notes/corporate-memory-26-2/index.md @@ -4,7 +4,7 @@ tags: - ReleaseNote --- -# Corporate Memory 26.2.0 +# eccenca Corporate Memory 26.2.0 Corporate Memory 26.2 is the second major release in 2026. It introduces reusable rule blocks and execution variables in Build, a new Manage module and SHACL based resource authoring in Explore, ships eccenca Marketplace as a generally available component, and adds workspace status reporting and Explore view administration to cmemc. @@ -37,12 +37,17 @@ The highlights of this release are: This release delivers the following component versions: -- [eccenca DataIntegration v26.2.0](#eccenca-dataintegration-v2620) -- [eccenca Explore v26.2.0](#eccenca-explore-v2620) -- [eccenca Marketplace v26.2.4](#eccenca-marketplace-v2624) -- [eccenca Corporate Memory Control (cmemc) v26.2.0](#eccenca-corporate-memory-control-cmemc-v2620) -- [eccenca Graph Insights v20.0.0](#eccenca-graph-insights-v2000) -- [eccenca n8n Corporate Memory Community Node v0.4.2](#eccenca-n8n-community-node-v042) +- [eccenca Corporate Memory 26.2.0](#eccenca-corporate-memory-2620) + - [eccenca DataIntegration v26.2.0](#eccenca-dataintegration-v2620) + - [eccenca Explore v26.2.0](#eccenca-explore-v2620) + - [eccenca Marketplace v26.2.4](#eccenca-marketplace-v2624) + - [eccenca Corporate Memory Control (cmemc) v26.2.0](#eccenca-corporate-memory-control-cmemc-v2620) + - [eccenca Graph Insights v20.0.0](#eccenca-graph-insights-v2000) + - [eccenca n8n Community Node v0.4.2](#eccenca-n8n-community-node-v042) + - [Migration Notes](#migration-notes) + - [eccenca DataIntegration](#eccenca-dataintegration) + - [eccenca Explore](#eccenca-explore) + - [cmemc](#cmemc) We tested this release with the following dependency components: