Here’s what you can expect from the most recent updates to Open Supply Hub:

Interaction Improvements:

• Moderation Events Endpoint - API users can use the moderation events endpoint to query for merge events that have occurred within a certain period of time for any set of contributors. To pull these events, make a GET call to opensupplyhub.org/api/moderation-events/merge/. The default behavior is to return all merge events that have occurred across the system within the specified timeframe (or all events for all dates if no timeframe is specified).
• Available parameters:
  • date_greater_than_or_equal (YYYY-MM-DD; this is the beginning of the timeframe you want to query for merges)
  • date_less_than (YYYY-MM-DD; this is the end of the timeframe you want to query for merges)
  • contributors (use this to specify a set of contributors by contributor ID whose facilities you want to check for merges)

Resolved Bugs:

• Create=false API Parameter - An issue with the API returning an error response when an GET request to the facilities endpoint was made with create=false. In some cases, this issue prevented users from finding facilities that could have been matches for their data.

• Unable to Update a Claim - An issue with claims prevented users from editing their claimed information when the field for Facility / Processing Types was filled in. This issue has been resolved and claimants can now update this field.

• Average Lead Time Not Displaying - Claimants are able to share additional data points about their claimed facilities. One of these data points is average lead time. Claimants were able to enter data into this field, but the value was not displaying on the profile. This issue has been resolved and claimants can now enter and display this information on their facility profiles.

Refactoring, Automation and Architecture Changes:

• Search Infrastructure - As part of our continuing work to implement fuzzy search, we've added an automated process to update our Logstash service with new features and improvements. Logstash will help transfer data from our current database to the powerful OpenSearch search engine, enabling quick and efficient fuzzy search features for both front-end users and API users. This automation is crucial for developing new features for Facility Search 2.0, ensuring results reach users smoothly and quickly. Currently, Search 2.0 is in progress, and we are making sure everything is in place for a successful release.

• Potential Matches - A potential match is what results when OS Hub's matching system is not sure if incoming data is a match with existing records. In these cases, the system will suggest a potential match(es) and ask the user to determine if there is a match. Prior to this update, these pending records were left open indefinitely. With this change, pending records will be deleted after 30 days. This significantly reduces the amount of data stored in OS Hub and is expected to improve performance.

New features and updates like these are often built based on feedback from OS Hub users. If you have any questions about these updates or would like to make a suggestion for future improvements, please contact us.