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

Interaction Improvements:

• Sector values in GET /facilities/ responses via API. Previously, you could search and filter the facilities returned by the /facilities endpoint, but the sector values with facilities were left out of the response. You can now get all sector values that have been contributed for a particular facility in the /facilities response. Use the details = true parameter to get the most detailed set of information about each contribution on a facility.
• Contributing data to OS Hub? You can now use comma separated lists to upload multiple values for sector, product_type, sector_product_type, facility_type, processing_type, and facility_type_processing_type. Previously, vertical bar characters ("|") were required to separate discrete values when uploading multiple values to these fields. Read more about how these fields are processed in our guide to preparing your data for upload. This changes applies to data contributed through the API and to data contributed with a list upload.

Refactoring, Automation and Architecture Changes:

• In our ongoing effort to improve how data is parsed at upload, and processed for display on the front-end, we have made a changes related to:

  • Implementing serializers to transform incoming data for sector, product type, facility type, and processing type data

  • Connecting the processing component in our system ("ContriCleaner") to API and list uploads

Resolved Bugs:

• Geocode errors disguised as timeouts. Previously, there was an issue where API users could encounter a system timeout when trying to post facility data using the OS Hub API. We discovered that in many cases, this was actually being caused by a geocode error, where the submitted data could not be geocoded by our system. This sort of error can often be resolved by the user making sure that their address data does not contain extra/confusing information; however, because the error looked like a system timeout, a user wouldn't know to check their address data. Now, when this geocode error occurs, API users will receive a response like:

  • {
    "matches": [],
    "item_id": 1858794,
    "geocoded_geometry": null,
    "geocoded_address": null,
    "status": "GEOCODED_NO_RESULTS",
    "message": "The address you submitted can not be geocoded."
    }

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.