EORES Release 8.5.0 User Release Notes

Return to EORES Release Notes

Feature Additions

• The EOS filter builder has been updated to Mode 1 and Mode 2 capabilities for the End User.
• Fixed so EOS Default Filter name is displayed (consistent with EOR) for the End User.
  • Changed “phrase” text search to case insensitive traditional “LIKE” (e.g. “Japanese Earth-observation satellite mission”).
  • Fixed organization filter to work with “AND” logic.
  • Fixed life cycle phase filter for browsing platforms (Mike’s endless spinning barber poles).
  • Fixed EOS import/export (which uses the EOS filter).
• Filter has been divided into EOS hierarchy levels for better control of logic across the levels for the End User.
• Rremoved extra connecting lines when a filter is reloaded for the End User. Also restored the EOR attributes in the filter select list.
• Most of the highlighted fields are now cast to numeric for the End User. However, several EOR and EOS attribute values are not numeric and cannot be cast to numeric.
• The web service application has been updated to check the web service view column types and cast the numeric columns from strings to doubles for the End User.
• A config option (additionalCasts) has been added to the web service application for the End User. When present and set to 'true', the above mentioned fields except for length_of_data_record (which the USGS data has non-numeric values) are cast to numeric,
• The requested note has been added to the new value tree node dialog for the End User.
• When editing or creating new products for the End User, a PALMA ID already in use by a product on the same value tree cannot be used on that product.
• Added an additional constraint check to prevent creating a duplicate Product / PALMA ID for the End User.  This catches the case where a product is “brought into” the tree from another tree when a duplicate was created in “B”.
• The EOR browse by VT now has Expand All and Collapse All buttons to expand/collapse the entire VT for the End User. Also, the counts displayed are the total number of requirements at that level and below, including requirements connected to products (previously, the product counted as one in the total even if it had more than one connected to it).
• When DS names are updated globally, the name record is updated instead of creating a new one and orphaning the old one. This will be transparent to the End User.
• SQL error fixed so the New Child Node Name drop-down list is populated for the End User.
• Change to Measurement Range for EOS EP attribute: still in work, ignore testing.
• EOS Min/Max Measurement converted to Meas Range low/high for the End User.

Bug Fixes

• When the name of a shared node is changed and saved "uniquely", any existing node information record (where description, long name, etc. are stored) is updated for the End User rather than a new one created. This corrects the MBW export to use the new name.
  
  
  
  A node name can be changed back to a previous name via the GUI.
• Empty strings in Person records have been replaced with null values for the End User. The GUI, DCW Import, and VTW Import no longer insert empty strings for optional person fields (title, preferred name, phone, and phone ext).
• After deleting a child node, the tree is moved so that it remains on screen for the End User.
• Problem occurred when a product node was loaded before deleting a branch.  The refresh for the End User tries to refresh the children of the product node which errored out.  This has been fixed to “skip” product nodes for the refresh.

Web Services Impacts

• A config option (additionalCasts) has been added to the web service application for the End User. When present and set to 'true', the above mentioned fields except for length_of_data_record (which the USGS data has non-numeric values) are cast to numeric,
• Updated release tags for the End User to include the additionalCasts.

 Compatibility may be impacted

• None.