EORES Release 8.3.0 User Release Notes

Return to EORES Release Notes

Feature Additions

• The End User can enter a reasonable number of decimal places on Radar Bands Azimuth Resolution in the GUI.
• The EOR filter has been rewritten for more flexibility.
  
  End Users can group filtering options under separate AND/OR operators.
  
  "Exclude Matches" option is per filter option.
  
  A separate AND/OR option is available on filters with multi-selects if the requirements can have more than one of the selections assigned to it.
• Fix so EOS and VTI default filters load correctly for the End User.
• Fix to processing an empty Requirement Type filter for the End User.
  
  Fixed End User Application typo in filter selection list.
  
  Fixed filtering Spectral Bands and Sampling Conditions.
  
  Made attributes data-driven, so all are available.
• Fix for filtering attributes with units (e.g. Sampling Interval) for the End User.
  
   - POC, Project Name, Sources of Information, End User Application, Licensing Type, and Validation Info filters restored (accidentally deleted for "C")
  
  - only active attributes are in the filter drop-down list, and they are moved to the bottom under an "Attributes" group
  
  - the filter count in the Modify Filter Options menu item is completely removed (including EOS and VTI)
  
  - EOR Import & Export, as well as template download, have also been fixed (affected by EOR filter changes)
• Requirement type filter fix for the End User.
  
  - excess blanks removed from full text search strings (which caused SQL errors)
  
  - when a value tree has "pseudo-nodes" (where branch "A -> B" is defined in the VT master, but not "A" then "A" is a pseudo-node that cannot have anything aligned to it) and the "pseudo-node" is included in the search criteria the fake ID is ignored and no SQL error occurs).
  
  - if a filter is added to the builder and no values are selected, the filter is highlighted and a prompt is given.
• Added "Strict" option to multi-select filters for requirements that can have more than one of the options for the End User. "Strict" limits the results to only those options (e.g. Spectral Requirements selections of "Red", "Green", and "Blue", the strict option will return requirements with only these 3 options).
  
  - fixed drop-down selections to stay on top of other filter options.
  
  - fixed generating queries for unit conversions so a null input (start or end) stays null (e.g. if start is entered, but not end each unit conversion will remain where value >= converted value).
  
  - Signal to Noise units are optional on the filter.
  
  - Changed Licensing Type filter to allow AND/OR option on the licensing options.
• The And/Or for multi-selects for the End User enables/disables the associated "Strict" and no others.
• The And/Or for multi-selects for the End User is re-initialized after filter execution to enable/disable the "Strict" checkbox.
• The info icon for the multi-select And/Or drop-down for the End User has been fixed so only one icon is presented and clicking it opens the info dialog.
  
   - the "Strict" checkbox has been removed for Full Text Search since it isn't used by the filter.
• Requested changes to EOR/EOS export filenames have been made for the End User.
• When import is started, the file size is checked against the current Apache max upload value for the End User. If the size exceeds the limit, an error is produced.
• When an EOR import includes a new document, the document is listed in the summary message with a link to view the details for the End User.
• Adding a new doc to a new requirement fixed for the End User.
• In the EOR and EOS import workbooks, if the name cell is blank before entering a new value, the prompt to replace the name on other tabs with the new name is skipped for the End User.
• The EOS System, Network, Platform, and Sensing Element acronyms appear on a separate line in the respective detail views for the End User.

Bug Fixes

• The "on-the-fly" view calculation for date last updated was replaced with a static field updated by triggers on the appropriate tables for the End User.
  
  The WS view is much faster (less than 1 sec) for NOAA data.
  
  The triggers add approximately 20% to an EOR import which seems acceptable.
• A decimal point is allowed for normal cost entry for the End User.
• Invalid characters are removed for the End User from email addresses and the result is checked to be a valid email address (i.e. format). An exception is made for the 'NA' placeholder.
• Incomplete branches are imported using NULLs instead of empty strings for the End User (avoids duplicate node name issue).
• A data source that has been removed from all surveys can be deleted without error for the End User.

Web Services Impacts

• The "on-the-fly" view calculation for date last updated was replaced with a static field updated by triggers on the appropriate tables for the End User.
  
  The WS view is much faster (less than 1 sec) for NOAA data.
  
  The triggers add approximately 20% to an EOR import which seems acceptable.
• Platform Name and Acronym added to view for the End User for a CasRT web service.
• Level 2 & 3 Variables added to CasRT web services for the End User.

Compatibility may be impacted

• None.