Skip to main content
U.S. flag

An official website of the United States government

EORES Release 9.1.0 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

  • Sampling Conditions pick lists are sorted in the desired order for the End User.
  • Dates through the GUI, import/export, and Web Services have been changed to the YYYY-MM-DD format for the End User.
  • Fixed VT import job processing for the End User to not be dependent on the date format.
  • Fixed date displayed for the End User in VT import page that was broken by "B" update.
  • Single sensor export capability has been added to the sensor detail section for the End User.
  • The person browse filter has options to filter by EOR, EOS, and/or VTI connections for the End User.
  • A download button has been added to the Person browse that will download a spreadsheet of the filtered records for the End User.
  • EOR Export now has an option to export attributes without PR Trend and Weight columns for the End User.
  • The option on the EOR export dialog formatting has been fixed for the End User.
  • Special characters are no longer stripped from the POH site_name for the End User.
  • A separate tab for EOR / PALMA ID connections has been added to the EOR export spreadsheet with the requested functionality for the End User.
  • The End User can export a single platform from the platform details (download icon in the upper left of the details).
  • The POH, Bus Unit, VT and GCMD filters have been updated to have consistent look and feel for the End User:

    - no delayed "lazy" loading of tree data (trees are fully loaded at the start)

    - expand all and collapse all buttons

    - hide unused toggle button to alternate showing only current selections

    - checkbox selections are saved and reloaded, even if they don't correspond to filterable selections (e.g. GCMD Topic / Term levels).
  • Fixed so if a node is checked and then the child nodes are unchecked, executing the filter and reloading does not re-check the children (keeps them unchecked) for the End User.
  • An "Exact" text search mode has been added to the EOR filter for the End User. This mode allows any characters to be substring being searched.
  • The EOR and EOS filters for the End User now have an option to filter on the date item last updated. For EOS, the option is available on the Obs Sys, Network, Platform, and Sensor levels.
  • The SQL statements used to query the DCW information are no longer written to the export log for Admin Users.
  • Multi-select fields are checked for duplicates during EOR import for the End User.
  • Export of EPs with multiple sensors have a separate line for each sensor for the End User.
  • When a VT node is missing the Value_Tree_Hierarchy_Master record that defines it for the End User:

    - VT browse and EOR browse by Strategic Value Tree shows the node accordion fold with an error message in red.

    - top-of-tree browse shows a pop-up dialog

    - EOR edit displays the node without a checkbox (existing behavior)
  • VTW Ingest for the End User now requires a parent node to be defined on its own line before adding a child.
  • EP Data Type has been added as a filtering option to the EP Group of filters for the End User.
  • Data sources on the current value tree are bolded for the End User and DS not on the current tree are not.



    Also, there is an "All" checkbox which if unchecked causes the unconnected DS to be hidden in the dropdown list. Note however that if the user begins typing a name, all DS matching the substring are shown.
  • Key Dates have been added to the EOS filtering for the End User.
  • EOS Import for the End User will import country associations if the code is present without the country name and vice versa. If both are present, they are compared to each other.
  • App Admins have a "Manage Users" option under the "Manage" menu that provides the following user management features:

    1. Users are listed with role, last login date, created date, view and edit buttons

    2. A button is provided to create a new user account

    3. The view button displays a single record and includes the count of the user's saved filters.

    4. The edit button allows changing the user name or role, or deleting the user.

    5. The list view includes a "Maintenance Mode" button that will toggle all user (but not the current user) roles to Data Analyst. Clicking it again restores the original roles.
  • The More/Less button for attribute notes has been replaced with a "View Notes" button for the End User that pops up a dialog that is up to 90% of the screen height and 90% of the width. The notes are in a scrollable section of the dialog.



    The background coloring of attribute rows and the star icon for Fab 5 attributes have been changed.
  • Trend values have been changed to mixed case for the End User.
  • Warning message for the End User added to the export dialog for the specified EOR and EOS browse modes.
  • The transaction history log report has been updated for better performance with current data for the End User.
  • The prescribed sorting has been implemented for the End User.
  • A Requirement ID column has been added to each EOR tab for the End User. The ID stays in synch when the user changes the name column.
  • A button labeled "Export Records" has been added to the POH admin page for the End User. When clicked, the current POH definition is exported to a spreadsheet and downloaded. The spreadsheet is simple export without picklist support.
  • An Export Records button has been added to the Documentation Info admin. When clicked a spreadsheet of the Documentation records is downloaded for the End User.
  • The POH IDs for the End User are synched with NOAA.
  • Since NOAA's user names are all lowercase for the End User, the SAML authentication routine will now lookup users case insensitively.
  • Requested text has been added for the End User.

Bug Fixes

  • When there is a VTI export failure for the End User, the GUI will prepare a download zip file with log file (and any completed export sheets) for the user to investigate.
  • EOR attributes with a value but no units set can be deleted for the End User.
  • The Band Spacing input prompt shows (nm) for the End User.
  • The CasRT view has been fixed so the ODS fields are output as expected for the End User.
  • After a new EOR record is submitted, a prompt indicating success is presented for the End User and the browser loads the new record.
  • EOR import with a non-numeric string in the ID field will result in a user friendly error instead of a SQL error for the End User.
  • DCW Ingest parsing has been reworked to be "line oriented" where keywords are checked only on the lines they're expected to appear on. Thus, "Organization" or "Date" in a product name or "Data Sources" in a data source level 1 name on the notes page do not confuse the parsing and cause problems for the End User.

Web Services Impacts

  • Dates through the GUI, import/export, and Web Services have been changed to the YYYY-MM-DD format for the End User.
  • Fixed VT import job processing for the End User to not be dependent on the date format.
  • Fixed date displayed for the End User in VT import page that was broken by "B" update.
  • The get_reports_eor_basic_information web service output is sorted by requirement name (case insensitive) for the End User.
  • Hard-coded "threshold" and "objective" levels for the End User have been removed from the

    get_casrt_earth_observing_parameter_attribute web service.
  • EOR connections to ARCHIVED value trees are excluded from the web service output and EOR export for the End User.
  • The poh_url has been added to the get_reports_physical_organization_hierarchy WS for the End User.
  • The product date last updated field has been addded to the get_reports_surveyed_product_elicitation_information web service output for the End User.
  • Titles of elicitation team members are now output by the web services for the End User.

Compatibility may be impacted

  • None.