feat: Update Solution to Leverage Your Own Data

Author: Avijit-Microsoft

documents/CustomizeData.md

@@ -0,0 +1,23 @@
+## Customize the solution with your own data 
+
+If you would like to update the solution to leverage your own data please follow the steps below. 
+> Note: you will need to complete the deployment steps [here](./DeploymentGuide.md) before proceeding. 
+
+## Prerequisites: 
+1. Your data will need to be in JSON or wav format with the file name formated prefixed with "convo" then a GUID followed by a timestamp. For more examples of the data format, please review the sample transcripts and audio data included [here](/infra/data/)
+    * Example: convo_32e38683-bbf7-407e-a541-09b37b77921d_2024-12-07 04%3A00%3A00 
+
+
+1. Navigate to the storage account in the resource group you are using for this solution. 
+2. Open the `data` container
+3. If you have audio files, upload them to `custom_audiodata` folder. If you have call transcript files, upload them to `custom_transcripts` folder.
+4. Navigate to the terminal and run the `run_process_data_script.sh` to process the new data into the solution with the following commands. 
+    ```shell
+    cd infra/scripts
+
+    az login
+
+    bash run_process_data_script.sh resourcegroupname_param
+    ```
+    a. resourcegroupname_param - the name of the resource group.
+

documents/DeploymentGuide.md

@@ -210,4 +210,8 @@ To help you get started, here are some **Sample Questions** you can ask in the a
 - Give a summary of billing issues
 - When customers call in about unexpected charges, what types of charges are they seeing?
 
-These questions serve as a great starting point to explore insights from the data.
+These questions serve as a great starting point to explore insights from the data.
+
+## Next Steps: 
+Now that you've completed your deployment, you can start using the solution. Try out these things to start getting familiar with the capabilities:
+* [Customize the solution](./CustomizeData.md) with your own data

infra/process_data_scripts.bicep

@@ -0,0 +1,25 @@
+param solutionLocation string
+param keyVaultName string
+param identity string
+
+var baseUrl = 'https://raw.githubusercontent.com/microsoft/Conversation-Knowledge-Mining-Solution-Accelerator/main/'
+
+resource process_data_scripts 'Microsoft.Resources/deploymentScripts@2020-10-01' = {
+  kind:'AzureCLI'
+  name: 'process_data_scripts'
+  location: solutionLocation // Replace with your desired location
+  identity: {
+    type: 'UserAssigned'
+    userAssignedIdentities: {
+      '${identity}' : {}
+    }
+  }
+  properties: {
+    azCliVersion: '2.52.0'
+    primaryScriptUri: '${baseUrl}infra/scripts/process_data_scripts.sh' 
+    arguments: '${baseUrl} ${keyVaultName}' // Specify any arguments for the script
+    timeout: 'PT1H' // Specify the desired timeout duration
+    retentionInterval: 'PT1H' // Specify the desired retention interval
+    cleanupPreference:'OnSuccess'
+  }
+}

infra/scripts/copy_kb_files.sh

@@ -32,4 +32,6 @@ echo "Script Started"
 az login --identity --client-id ${managedIdentityClientId}
 # Using az storage blob upload-batch to upload files with managed identity authentication, as the az storage fs directory upload command is not working with managed identity authentication.
 az storage blob upload-batch --account-name "$storageAccount" --destination data/"$extractedFolder1" --source /mnt/azscripts/azscriptinput/"$extractedFolder1" --auth-mode login --pattern '*' --overwrite
-az storage blob upload-batch --account-name "$storageAccount" --destination data/"$extractedFolder2" --source /mnt/azscripts/azscriptinput/"$extractedFolder2" --auth-mode login --pattern '*' --overwrite
+az storage blob upload-batch --account-name "$storageAccount" --destination data/"$extractedFolder2" --source /mnt/azscripts/azscriptinput/"$extractedFolder2" --auth-mode login --pattern '*' --overwrite
+az storage fs directory create --account-name "$storageAccount" --file-system data --name custom_audiodata --auth-mode login
+az storage fs directory create --account-name "$storageAccount" --file-system data --name custom_transcripts --auth-mode login