Community Meeting Recap (May 17)



  • Deployment of the API v2.5.0 and frontend v.3.3.0 [ref]
  • Catalog: Data refresh process in the catalog made clearer [ref]
  • Frontend: Saving network requests by not fetching the data twice on the search page [ref]
  • Frontend: layout PR fixed a lot of issues with scrolling and the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. [ref]
  • Frontend: fix for the image size jumps on single result page [ref]
  • OpenverseOpenverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at Addition of the Renovate version management to the Openverse repo [ref]

In progress

Needs review

  • APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.: Overhaul serializer to eliminate manually-defined fields [ref]
  • API: Refactor search controller for consistency and clarity [ref]
  • Frontend: Fix for Copy attribution tabs [ref]
  • Frontend: Support for additional sources with a feature flag [ref]


We are reviewing the required data fields in the catalog to see if any required fields are missing and trying to backfill missing data. This will help us establish trust in the availability of the data and help clean up duplicated code that is necessary now on all layers of the stack because data is not always present.

We also plan on deployingDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. the API with the fix for email registration and the audio length query .