Skip to main content
U.S. flag

An official website of the United States government

EORES Release 8.6.1 User Release Notes

EORES is a relational database system architecture that provides an integrated web-enabled tool for end users to store EO user requirements, value tree information, and EO system capabilities and performance information. End users can display, edit, browse, and maintain this information using a graphical user interface as well as export any data that are in the architecture.

Return to EORES Release Notes

 

Feature Additions

  • None.

Bug Fixes

  • When entering into edit mode for a data source with double blanks, the edit form shows the extra blank(s) in the top title (brick red area) and in the DS name drop-down select. Editing the name to remove the extra blank(s) can be saved as expected for the End User.



    Note that the extra blanks are represented by a special code (  called nonbreaking space) in the select which affects the pattern matching when searching for a string.

    So, 'A B' (A blank blank B) is represented internally as 'A  B' and if the user types A blank blank B, the A blank matches, but the second blank does not due to the code. This is just a special circumstance for names with the double blanks. Names without the double blanks can be searched as expected.
  • When a top-of-tree node that's shared with an ARCHIVED tree is edited and a change is made to the name or type (the portion that's shared), the prompt explaining the sharing is given with the ARCHIVED tree disabled for receiving the edit and the edit update is applied to the selected un-ARCHIVED trees as expected for the End User.
  • A DB constraint has been added to enforce at most one instance of a specific validation information type per requirement and the GUI and import processing have been updated accordingly for the End User.



    Also, the error message from export that initiated this has been updated to the attached screen snip. However, this error should not occur since duplicates are completely prevented now.
  • The data source name drop down list for the End User shows the extra blanks. Extra blanks can be removed as expected.
    • When a data source edit form is open, no additional forms can be opened (prevents cross-form corruption of data)
    • Fix so "No Data Sources Found" error does not appear.
  • A DS that's shared with multiple trees can be uniquely updated with a new name for the End User without encountering the product unique Palma ID error.
  • A DS that is not scored on a product but is shared with multiple trees can be globally updated for the End User.
  • VTI Ingest no longer alters the status of other trees, leaving the tree ingested as "IN PROGRESS" for the End User.
  • Above fix for the End User applied.
  • Data source record update sharing prompt has been reworked to be more user friendly for the End User and issues identified in the description have been fixed.
  • Fix for the End User so a unique save of a DS without cost information does not encounter an SQL error.

Web Services Impacts

  • None.

Compatibility may be impacted

  • None.