Skip to main content
Version: 7.3

How To: Load the ODS with Sample XML Data using Bulk Load Client Utility

info

This article uses the core sample data released with Ed-Fi Data Standard v5.1. If you have an extension that extends core entities with additional required fields, the core sample data may fail to fulfill those additional requirements and fail to load.

This article describes the steps needed to populate an Ed-Fi ODS with sample XML data, using the Ed-Fi Bulk Load Client utility.

Step 1. Install the Ed-Fi Bulk Load Client

  • Ensure that you have an instance of the Ed-Fi ODS / API running locally that has been set up following the Getting Started - Source Code Installation.

  • Ensure .NET 8.0 SDK is installed.

  • Add Ed-Fi package source by running the following command in PowerShell:

    if (-not [Net.ServicePointManager]::SecurityProtocol.HasFlag([Net.SecurityProtocolType]::Tls12)) {
    [Net.ServicePointManager]::SecurityProtocol += [Net.SecurityProtocolType]::Tls12
    }
    if(-not (Get-PackageSource -ProviderName NuGet | Where-Object -Property Name -eq "Ed-FiAzureArtifacts")){
    Write-Host "Registering Ed-Fi Package Source..."
    Register-PackageSource -Name Ed-FiAzureArtifacts `
    -Location "https://pkgs.dev.azure.com/ed-fi-alliance/Ed-Fi-Alliance-OSS/_packaging/EdFi/nuget/v3/index.json" `
    -ProviderName NuGet
    Write-Host "Ed-Fi package source configured"
    }
  • Install the Ed-Fi Bulk Load Client from a PowerShell prompt using the following commands:

    mkdir <YourInstallFolder>
    dotnet tool install EdFi.Suite3.BulkLoadClient.Console --version 7.3.413 --tool-path <YourInstallFolder>

    This will produce output like:

    You can invoke the tool using the following command: EdFi.BulkLoadClient.Console
    Tool 'edfi.suite3.bulkloadclient.console' (version '7.3.413') was successfully installed.
  • You can verify that the EdFi.BulkLoadClient.Console.exe is available by browsing to this location <YourInstallFolder>\EdFi.BulkLoadClient.Console.exe

Step 2. Download Scripts and Sample Data

  • Download and Extract Ed-Fi-SampleDataLoad.zip to a local folder. We recommend C:\Ed-Fi-SampleDataLoad. Ed-Fi-SampleDataLoad.zip contains all the scripts and directory structure used in this how-to article.
  • Download the Sample XML to Ed-Fi-SampleDataLoad\Sample XML
  • Download the Descriptors to Ed-Fi-SampleDataLoad\Bootstrap
  • Move the following files from Ed-Fi-SampleDataLoad\Sample XML to Ed-Fi-SampleDataLoad\Bootstrap
    • Standards.xml
    • EducationOrganization.xml
    • IndicatorDescriptor.xml
    • IndicatorGroupDescriptor.xml
    • IndicatorLevelDescriptor.xml
    • ProgramCharacteristicDescriptor.xml
info

The Bootstrap folder is used to load the necessary Descriptors and Education Organization used by the ODS / API. Since they require a special claimset (enabled in Step 4, below) they must be loaded separately from the other sample files.

Step 3. Create an Empty Sandbox

  • Open a PowerShell session.

  • Navigate to the Ed-Fi-ODS-Implementation directory

  • **Execute .\Initialize-PowershellForDevelopment.ps1 and then Reset-EmptySandboxDatabase.

    The script will create the EdFi_Ods_Sandbox_Empty Database.

Step 4. Create API Client for Empty Sandbox

  • Execute CreateApiClientforEmptySandbox.sql against the EdFi_Admin database. This will create claims needed to access the EdFi_Ods_Sandbox_Empty.

    For Ed-Fi implementations running SQL, SQL Server Agent needs to be configured

    Expand to view sample code...
    CreateApiClienforEmptySandbox.sql
    DECLARE @VendorName nvarchar(150) = 'Empty Test Vendor'
    DECLARE @NamespacePrefix nvarchar (255) = 'uri://ed-fi.org'
    DECLARE @NamespacePrefixEdu nvarchar (255) = 'uri://gbisd.edu'
    DECLARE @UserFullName varchar(150) = 'Empty Test User'
    DECLARE @UserEmailAddress varchar(150) = 'emptytest@ed-fi.org'
    DECLARE @ApplicationName nvarchar(255) = 'Default Sandbox Application Empty'
    DECLARE @ClaimSetName nvarchar(255) = 'Bootstrap Descriptors and EdOrgs'
    DECLARE @ApiClientName nvarchar(50) = 'Empty Demonstration Sandbox'
    DECLARE @EducationOrganizationId int = 255901 --Must be an ed-org in the ODS
    DECLARE @Key nvarchar(50) = 'empty'
    DECLARE @Secret nvarchar(100) = 'emptySecret'
    DECLARE @OdsInstanceName nvarchar(100) = 'Test ODS'
    DECLARE @OdsInstanceType nvarchar(100) = 'Test Type'
    DECLARE @OdsInstanceConnectionString nvarchar(500) = 'server=(local);trusted_connection=True;database=EdFi_Ods_Sandbox_Empty;application name=EdFi.Ods.WebApi;Encrypt=False'

    DECLARE @IsPopulatedSandbox bit = 0
    -- For Non-Sandbox deployments
    DECLARE @UseSandbox bit = 0
    -- For Sandbox
    --DECLARE @UseSandbox bit = 1

    DECLARE @VendorId int
    DECLARE @UserId int
    DECLARE @ApplicationId int
    DECLARE @ApplicationEducationOrganizationId int
    DECLARE @ApiClientId int
    DECLARE @OdsInstanceId int

    -- Clear @IsPopulatedSandbox if not using sandbox
    IF (@UseSandbox = 0)
    SET @IsPopulatedSandbox = 0

    -- Ensure Vendor exists
    SELECT @VendorId = VendorId FROM [dbo].[Vendors] WHERE VendorName = @VendorName

    IF(@VendorId IS NULL)
    BEGIN
    INSERT INTO [dbo].[Vendors] (VendorName)
    VALUES (@VendorName)

    SET @VendorId = SCOPE_IDENTITY()
    END

    -- Ensure correct namespace prefixes are set up
    DELETE FROM [dbo].[VendorNamespacePrefixes] WHERE Vendor_VendorId = @VendorId
    INSERT INTO [dbo].[VendorNamespacePrefixes] (Vendor_VendorId, NamespacePrefix)
    VALUES (@VendorId, @NamespacePrefix)
    INSERT INTO [dbo].[VendorNamespacePrefixes] (Vendor_VendorId, NamespacePrefix)
    VALUES (@VendorId, @NamespacePrefixEdu)
    -- Ensure User exists for test Vendor
    SELECT @UserId = UserId FROM [dbo].[Users] WHERE FullName = @UserFullName AND Vendor_VendorId = @VendorId

    IF(@UserId IS NULL)
    BEGIN
    INSERT INTO [dbo].[Users] (Email, FullName, Vendor_VendorId)
    VALUES (@UserEmailAddress, @UserFullName, @VendorId)

    SET @UserId = SCOPE_IDENTITY()
    END
    ELSE
    BEGIN
    UPDATE [dbo].[Users] SET Email = @UserEmailAddress WHERE UserId = @UserId
    END

    -- Ensure Application exists
    SELECT @ApplicationId = ApplicationId FROM [dbo].[Applications] WHERE ApplicationName = @ApplicationName AND Vendor_VendorId = @VendorId

    IF (@ApplicationId IS NULL)
    BEGIN
    INSERT INTO [dbo].[Applications] (ApplicationName, Vendor_VendorId, ClaimSetName)
    VALUES (@ApplicationName, @VendorId, @ClaimSetName)

    SET @ApplicationId = SCOPE_IDENTITY()
    END
    ELSE
    BEGIN
    UPDATE [dbo].[Applications] SET ClaimSetName = @ClaimSetName WHERE ApplicationId = @ApplicationId
    END

    -- Ensure ApiClient exists
    SELECT @ApiClientId = ApiClientId FROM [dbo].[ApiClients] WHERE Application_ApplicationId = @ApplicationId AND [Name] = @ApiClientName

    IF(@ApiClientId IS NULL)
    BEGIN
    INSERT INTO [dbo].[ApiClients] ([Key], [Secret], [Name], IsApproved, UseSandbox, SandboxType, Application_ApplicationId, User_UserId, SecretIsHashed)
    VALUES (@Key, @Secret, @ApiClientName, 1, @UseSandbox, @IsPopulatedSandbox, @ApplicationId, @UserId, 0)

    SET @ApiClientId = SCOPE_IDENTITY()
    END
    ELSE
    BEGIN
    UPDATE [dbo].[ApiClients] SET [Key] = @Key, [Secret] = @Secret, UseSandbox = @UseSandbox, SandboxType = @IsPopulatedSandbox, User_UserId = @UserId, SecretIsHashed = 0 WHERE ApiClientId = @ApiClientId
    END

    -- Ensure OdsInstance exists
    SELECT @OdsInstanceId = OdsInstanceId FROM [dbo].[OdsInstances] WHERE [Name] = @OdsInstanceName and InstanceType = @OdsInstanceType

    IF(@OdsInstanceId IS NULL)
    BEGIN
    INSERT INTO [dbo].[OdsInstances] ([Name], InstanceType, ConnectionString)
    VALUES (@OdsInstanceName, @OdsInstanceType, @OdsInstanceConnectionString)
    SET @OdsInstanceId = SCOPE_IDENTITY()
    END
    ELSE
    BEGIN
    UPDATE [dbo].[OdsInstances] SET ConnectionString = @OdsInstanceConnectionString WHERE OdsInstanceId = @OdsInstanceId
    END

    -- Ensure ApiClientOdsInstance exists
    IF NOT EXISTS (SELECT 1 FROM [dbo].[ApiClientOdsInstances] WHERE ApiClient_ApiClientId = @ApiClientId AND OdsInstance_OdsInstanceId = @OdsInstanceId)
    BEGIN
    INSERT INTO [dbo].[ApiClientOdsInstances] (ApiClient_ApiClientId, OdsInstance_OdsInstanceId)
    VALUES (@ApiClientId, @OdsInstanceId)
    END

    IF (@EducationOrganizationId IS NOT NULL)
    BEGIN
    -- Clear all education organization links for the selected application
    DELETE acaeo
    FROM dbo.ApiClientApplicationEducationOrganizations acaeo
    INNER JOIN dbo.ApplicationEducationOrganizations aeo
    ON acaeo.ApplicationEducationOrganization_ApplicationEducationOrganizationId = aeo.ApplicationEducationOrganizationId
    WHERE aeo.Application_ApplicationId = @ApplicationId
    DELETE FROM [dbo].[ApplicationEducationOrganizations] WHERE Application_ApplicationId = @ApplicationId

    -- Ensure correct education organizations are set up
    INSERT INTO [dbo].[ApplicationEducationOrganizations] (EducationOrganizationId, Application_ApplicationId)
    VALUES (@EducationOrganizationId, @ApplicationId)
    SELECT @ApplicationEducationOrganizationId = SCOPE_IDENTITY()

    INSERT INTO [dbo].[ApiClientApplicationEducationOrganizations] (ApplicationEducationOrganization_ApplicationEducationOrganizationId, ApiClient_ApiClientId)
    VALUES (@ApplicationEducationOrganizationId, @ApiClientId)
    END

Step 5. Run the Bootstrap Script to Load Descriptors, Standards and Education Organizations

  • Open a PowerShell session.

  • Navigate to Ed-Fi-SampleDataLoad directory (e.g., C:\Ed-Fi-SampleDataLoad).

  • Open the LoadBootstrapData.ps1 file in a text editor and update the $apiLoaderExe variable Value where EdFi.BulkLoadClient.Console is installed in Step 1.

  • Example $apiLoaderExe="<YourInstallFolderFullPath>\EdFi.BulkLoadClient.Console.exe"

  • For Postgres Only, please update Key &amp Secret "-k", "**E**mpty", "-s", "empty**S**ecret"

  • Save and Execute LoadBootstrapData.ps1.

    The script will run the Bulk Load Client loading data from the Bootstrap folder to the Empty Sandbox Database.

Step 6. Update Claim Set to Load Sample Data

  • **Execute EnableSandboxClaimset.sql against the EdFi_Admin database. This will change the claim set for the empty sandbox database you created in Step 4 to the Ed-Fi Sandbox claimset.

    EnableSandboxClaimset.sql
    UPDATE [dbo].[Applications]
    SET [ClaimSetName] = 'Ed-Fi Sandbox'
    WHERE [ApplicationName] = 'Default Sandbox Application Empty'
    GO

Step 7. Run the Sample Data Script to Load Sample Data

  • Restart the instance of the Ed-Fi ODS / API running locally again to refresh the claims.
  • Open a PowerShell session.
  • Navigate to Ed-Fi-SampleDataLoad directory (e.g., C:\Ed-Fi-SampleDataLoad).
  • Open the LoadSampleData.ps1 file in notepad or Windows PowerShell ISE and update the $apiLoaderExe variable Value where EdFi.BulkLoadClient.Console is installed in Step 1.
  • Example $apiLoaderExe="<YourInstallFolderFullPath>\EdFi.BulkLoadClient.Console.exe"
  • For Postgres Only, please update Key & Secret "-k", "Empty", "-s", "emptySecret"
  • Save and Execute LoadSampleData.ps1.

The script will run the Bulk Load Client to load data from the Sample XML folder to the Empty Sandbox Database.

note

The following link contains the scripts and directory setup used in this how-to article. Ed-Fi-SampleDataLoad.zip

The following GitHub links contain the sample XML files and the as-shipped Ed-Fi Descriptor XML. Sample XML Descriptors