When integrating Go1 content into your product offering, or when utilising the Go1 API to build a content search and discovery interface within your application, there are a minimum set of ‘discoverability requirements’ you must include as part of your integration. These have been outlined in detail below.
These requirements only apply if the integration you are building surfaces Go1 content inside your application, and are mandated to provide the best user experience for your customers - to help them find and identify Go1 content quickly and easily.
Discoverability Requirement 1: Add search filters (topic, provider & duration)
With over 80,000 pieces of learning content in the Go1 library - it's important to enable end-users to find the content they need as quickly and as easily as possible.
If you are building a search interface in your application utilising the Go1 API, to assist users in discovering the most relevant content it is a requirement to include the ability for your users to be able to filter searches by our base set of filters. These filters include topic, provider and duration.
You can learn how to implement these filters by visiting our Search and Discovery Filters documentation.
Discoverability Requirement 2: Display our base set of metadata fields on content items
When displaying Go1's content via a course card, table, catalogue or similar user interface within your application, it is required to always display our 'base set' of content metadata fields on each learning object. The base content metadata fields include; title, provider, duration and image.
Displaying these fields allows users to easily identify content that they are looking for and that is most relevant to them within the Go1 library.
Example of an integrated interface that meets this requirement
The example below uses our base set of filters (topic, provider and duration), and displays the title, image provider and duration on each learning object.
Example of an integration interface that does not meet the requirement
In the example below the search interface does not have any filters available, and the learning objects displayed do now contain our base set of metadata fields.
