Pull requests

#1 Merged
Repository
vinaytc/main-vinayFork main-vinayFork
Branch
default
Repository
dataup/main main
Branch
default

Changes made

Author
  1. Vinay TC
Reviewers
Description

Changes Completed: 1. Validation changes: a. Element: westBoundingCoordinate Possible values: -180.0000 to 180.0000 Help text: Longitude of western-most point of bounding box (-180 to 180 degrees) Error message: Must be between -180 and 180 degrees b. Element: eastBoundingCoordinate Possible values: -180.0000 to 180.0000 Help text: Longitude of eastern-most point of bounding box (-180 to 180 degrees) Error message: Must be between -180 and 180 degrees c. Element: northBoundingCoordinate Possible values: -90.0000 to 90.0000 Help text: Latitude of northern-most point of bounding box (-90 to 90 degrees) Error message: Must be between -90 and 90 degrees d. Element: southBoundingCoordinate Possible values: -90.0000 to 90.0000 Help text: Latitude of southern-most point of bounding box (-90 to 90 degrees) Error message: Must be between -90 and 90 degrees 2. Column Description : a. make all fields mandatory (Except units if the user chooses dateTime or text) b. replace "float" with "real" in generated XML c. there is a required element missing from the EML: if the user chooses <dateTime> in the UI, the EML generated should have the element <formatString> populated with a non-empty string. Rather than ask the user for this, please automatically populate the element with the phrase below. <dateTime> <formatString> The user has designated this column as some form of date and/or time. No standard is specified due to DataUp coding constraints. </formatString> </dateTime> 3. there is a required element missing from the EML: if the user chooses text (i.e. <nominal>), there should be non-empty string for <definition>. Rather than have the user define this (since it's not part of the UI right now), auto-fill this element with the value that what the user entered for <attributeDefinition> <nominal> <textDomain> <definition> auto-fill this with the value of the "attributeDefinition" element </definition> </textDomain> </nominal>

Comments (0)