QUA-1518: Refactor Source Datastore Section

docs/anomalies/anomaly-detection.md

@@ -9,21 +9,21 @@ Let’s get started 🚀
 By setting up a datastore and establishing a connection to your data source (database or file system), you create a robust foundation for effective data management and analysis in Qualytics. This setup enables you to access, manipulate, and utilize your data efficiently, paving the way for advanced data quality checks, profiling, scanning, anomaly surveillance, and other analytics tasks.
 
 !!! note 
-    For more information, please refer to the [Configuring Source Datastores](../add-datastores/overview-of-a-datastore.md#configuring-source-datastores) documentation.
+    For more information, please refer to the [Configuring Source Datastores](../source-datastore/add-datastores/overview-of-a-datastore.md#configuring-source-datastores) documentation.
 
 **2. Sync Operation**
 
 The Sync operation detects new, changed, or removed containers and fields by comparing the current datastore state against what Qualytics already knows. It works incrementally, only processing the differences. This ensures a solid foundation for the subsequent Profile and Scan operations.
 
 !!! note
-    For more information, please refer to the [Sync Operation](../source-datastore/sync.md) Documentation.
+    For more information, please refer to the [Sync Operation](../source-datastore/operations/catalog.md) Documentation.
 
 **3. Profile Operation**
 
 The Profile operation enables training of the collected data structures and their associated metadata values. This is crucial for gathering comprehensive aggregated statistics on the selected data, providing deeper insights, and preparing the data for quality assessment.
 
 !!! note 
-    For more information, please refer to the documentation [Profile Operation](../source-datastore/profile.md).
+    For more information, please refer to the documentation [Profile Operation](../source-datastore/operations/profile.md).
 
 **4. Create Authored Checks**
 
@@ -38,7 +38,7 @@ Authored checks can range from simple, template-based checks to more complex rul
 The Scan operation asserts rigorous quality checks to identify any anomalies within the data. This step ensures data integrity and reliability by recording the analyzed data in your configured enrichment datastore, facilitating continuous data quality improvement.
 
 !!! note 
-    For more information, please refer to the documentation [Scan Operation](../source-datastore/scan.md). 
+    For more information, please refer to the documentation [Scan Operation](../source-datastore/operations/scan.md). 
 
 **6. Anomaly Analysis**
 

docs/anomalies/anomaly-fingerprints.md

@@ -69,7 +69,7 @@ The lack of a persistent identifier means **Qualytics** cannot distinguish betwe
 
 To handle recurring anomalies in truncate-and-reload tables, configure your scan to use fingerprint-based duplicate handling.
 
-Follow the steps in the [scan operation configuration](../source-datastore/scan.md#configuration) to reach the correct settings. Then, under **Step 8 → Scan Settings**, open the [anomaly options section](https://userguide.qualytics.io/source-datastore/scan/#configuration:~:text=Step%208%3A%20Configure%20the%20Scan%20Settings) and enable both duplicate-handling options:
+Follow the steps in the [scan operation configuration](../source-datastore/operations/scan.md#configuration) to reach the correct settings. Then, under **Step 8 → Scan Settings**, open the [anomaly options section](https://userguide.qualytics.io/source-datastore/scan/#configuration:~:text=Step%208%3A%20Configure%20the%20Scan%20Settings) and enable both duplicate-handling options:
 
 - **Archive Duplicate Anomalies:** When the same 127 anomalies appear again after the table reload, Qualytics recognizes their fingerprints and automatically marks them as duplicates rather than new anomalies.  
 - **Reactivate Recurring Anomalies:** If an anomaly was previously archived or resolved but reappears in subsequent scans, Qualytics reactivates the original anomaly record, maintaining full historical context.  

docs/anomalies/source-record.md

@@ -21,7 +21,7 @@ Users can view source records with selectable display limits of 10, 100, 1,000,
 
 ## Download Source Record
 
-User can download the source records that were captured for an anomaly during the scan run. The download always includes only the records that were selected to be stored in the [scan settings](../source-datastore/scan.md#configuration) at the time the scan was configured.
+User can download the source records that were captured for an anomaly during the scan run. The download always includes only the records that were selected to be stored in the [scan settings](../source-datastore/operations/scan.md#configuration) at the time the scan was configured.
 
 **For example**, if the user selected **100** as the maximum number of source records per anomaly, then **100 anomalous records will be shown on the Source Records** page and the same **100 records will be available for download**. If the **user selected 10**, only those **10 records will be displayed and downloadable**. If the user needs to download more source records, the limit must be increased in the scan settings and the scan must be re-run, as records that were not captured during the scan cannot be downloaded later.