Uploaded image for project: 'Ed-Fi Data Standard'
  1. Ed-Fi Data Standard
  2. DATASTD-939

Typo on LanguageDescriptor causing vendor an error when posting thru API

    XMLWordPrintable

Details

    Description

      Summary of outcomes for Data Standard 2.1

      • Problem Addressed: LanguageDescriptor enumeration "Hindi" has a trailing space.
      • High-level Reasoning: The trailing space on the LanguageDescriptor enumeration "Hindi" causes error when posting through the API and must be removed.
      • Changes Made: Removed trailing space after "Hindi"

      Original ticket description follows:

      API ODS 2.1v and Data Standard 2.1v

      The LanguageDescriptor CodeValue "Hindi" has a trailing space at the end of the causing an issue when posting the corrected value without the trailing space.

      This issue affects the following files and I plan to submit a pull request later tonight or in the monring with the fix Chris.Moffatt

      Ed-Fi-Standard\v2.0\Samples\Sample XML\Descriptors\Ed-Fi\LanguageDescriptor.xml
      Ed-Fi-ODS-Implementation\Database\Data\EdFi\Descriptors\Interchange-Descriptors.xml

      <LanguageDescriptor>
      <CodeValue>Hindi </CodeValue>
      <ShortDescription>Hindi </ShortDescription>
      <Description>Hindi </Description>
      <Namespace>http://ed-fi.org/Descriptor/LanguageDescriptor.xml</Namespace>
      <LanguageMap>Other</LanguageMap>
      </LanguageDescriptor>

      Those modifications will be checking into a pull request.

      However the EdFi_Ods_Populated_Template.bak would need to be modified or regenerated from the descriptors after applying the modification

      update EdFi_Ods_Populated_Template.edfi.Descriptor set CodeValue = 'Hindi',
      ShortDescription = 'Hindi', Description = 'Hindi'
      WHERE (Description LIKE '%Hindi%')

      Attachments

        Activity

          People

            Unassigned Unassigned
            sbrunetjones Silvia Jones (old account) (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Salesforce