EORES Release 8.6.0 User Release Notes

Return to EORES Release Notes

Feature Additions

• The VTI filter has been updated with improved options for the End User.
  • Fixed EOR links when browsing by VT
  • Links from the EORES home page to list of VT names to the browse have been fixed.
  • DCW export has been fixed when browsing by VT

• Fixed data source option subquery to also filter by selected value tree for the End User.
  • added cost units to filter and unit conversions ($M/yr only for USGS, $M and $K for NOAA) to the filtering and removed the Cost Units management (under EOS Info).
  • in DS browse, a filter "match" icon is added to products that match product related search criteria (e.g. if a DS is attached to 50 products and a search is made for swing scores between 40 and 50, the products that scored the DS in this range will have the icon in the accordion fold). Also, a "Hide" checkbox is included in the DS info by the Edit check to hide the products that do not match.
• After opening a data source record for edit and then either submitting or cancelling the edit form, the Apply button for the filter is not removed for the End User.
  • when filtering DS by product criteria (e.g. swing weight score) the matching icon is displayed on matching products even when all products for a DS match (e.g. when there is only one, etc.).
• When the data source filter is cleared (no filtering), the products associated with each data source no longer receive the "match" icon for the End User.
• DCW import will reject Swing Weight Scores greater than or equal to the Status Weight Score for the End User.
• The top-of-tree Add New Value Tree Node dialog has been changed for the End User to use a text entry field for the name and a pop-up selection dialog to select from existing names.
  • fixed so the dialog can be canceled after using the pop-up to populate the new name.
  • the dialog to align products starts with a cleared rationale input (rather than defaulting to the previous rationale)

• Extraneous "discard changes?" prompt removed for the End User when creating a new node.
• Requested acronyms are spelled out for the End User.
  • also expanded "WAS Note" to "Weighted Average Scoring Note"
• The person web service for the End User is sorted by last_name, first_name, then email address.
• Requested units checks (and their exceptions) for the End User have been implemented.
• Requested EP attribute units checks for the End User have been implemented in EOS import.
• Added units requirement to EP attributes created/edited under the EOS admin.
• Added Measurement Range Units drop-down select values to EOS export (USGS-only issue) for the End User.

Bug Fixes

• When the EOR form submission encounters failures (validation or otherwise), an appropriate message is presented to the End User and the form is left in a state where the user can retry submission.
• When the connection to the server is lost (e.g., turning off WIFI) before submitting the form, a message pops up for the End User indicating an error.
• "Extra" blanks in data source names, product names, and node names are not hidden by the GUI for the End User.
• Products can be aligned to more than one node on a tree for the End User.
• The default sorting collation seems to ignore non-alphanumeric characters.  This is causing some confusion for the End User with "U.S. Census ..." appearing before "USDA ...", and then "U.S. Immigration".  It would be less confusing if the two "U.S. ..." entries were together.
  
  
  
  The default global collation is set during DB creation and cannot be changed except to build a new DB. However, individual columns can override the global default and these overrides can be changed without rebuilding the DB.
  
  
  
  So, this task is to update the default collation on the requirement name.
• Changed requirement name sorting to be case in-sensitive for the End User (in addition to the previous collation change).  This change has been applied as follows:
  • EOR Browse (all groupings)
  • EOR Record Admin
  • EOR Export (all tabs with EOR names, most were previously unsorted)
  • Person Admin Affiliations (previously unsorted, also added normal sorting to EOS names as well)
  • Documentation Admin Affiliations (previously unsorted, also added normal sorting to EOS names as well)
• In EOR export, requirements on the affiliations tab for the End User are sorted case insensitive.
• Elicitation_team_member_remarks has been added to v_dcw_elicitation_team (used by DCW export) and v_reports_elicitation_poc (used by WS) for the End User.
• The DS Groups WS no longer combines data from multiple trees for a data source for the End User.
• VTW Ingest now only checks the node levels of the current tree for duplicate names for the End User. The name can exist at any level of another tree.
• Checks for duplicate subtree names have also been limited to the tree being ingested for the End User.
• When an existing EOR attribute record field is "blanked" out and the field is cast to numeric in the web services (such as a weight field). The WS output succeeds without error and empty strings are no longer saved in the DB for the End User.

Web Services Impacts

• "notes" renamed to "notes_on_current_sources_of_info" and placed after "current_sources_of_info" in the EOR basic information web service for the End User.
• Requested columns for the End User added to the web services. Note for the eor_gcmd_information, the detailed_variable is presented for each pathway (primary_gcmd_variable, secondary_gcmd_variable, and tertiary_gcmd_variable).
• EP basic info web service restored to output measurement range columns as expected for the End User.
• EOR GCMD category columns for the End User moved to before topic/term columns for each path.
• Attribute Weighting Rationale and Other Remarks fields for the End User have been removed from the get_reports_eor_extended_attributes_information web service to the get_reports_eor_basic_information, in the specified column order.
• The DS Groups WS no longer combines data from multiple trees for a data source for the End User.

Compatibility may be impacted

• None.