openverse-frontend

openverse-frontend copied to clipboard

Problem

We currently use two names "Meta Search" and "Additional Sources" to refer to the same feature: letting users search a list of external search engines that also contain CC-licensed content. I think "Additional Sources" is much more sensible for non-technical users. Additionally, using the word "Meta" in the context of our name "Openverse", as it relates to the "Metaverse" is also quite unfortunate.

Description

Let's remove all references to 'meta search' and replace them with 'additional sources', including internal naming of code, methods, string keys, and so on.

We need to make sure a redirect is in place to preserve url so that https://wordpress.org/openverse/meta-search/ redirects to https://wordpress.org/openverse/additional-sources/.

Alternatives

Additional context

Implementation

• [ ] 🙋 I would be interested in implementing this feature.

The word "additional sources" is confusing term as we are not adding anything to Openverse.

@sarayourfriend suggested in an internal conversation that “external sources” sounds more explicit about what will happen. And I agree with that point.

This term also relates to the "additional types" designed for the switcher popover to show non-supported-yet content types, like video. In that vein, it sounds reasonable revisiting both.

Based on the current pages and designs we made, here are the places that @obulat identified where we are using one or both terms.

Content switcher

Ticket WordPress/openverse-frontend#739 proposed creating an "additional types" section for the upcoming content types. The feature is not live yet but I think we are on time to revisit it.

Replacing "additional types" with "coming soon", as you suggested internally @zackkrida, is very accurate and explicit about what this content type belongs to.

Meta search section

For this section, the current implementation is outdated and ticket WordPress/openverse-frontend#734 addresses this change. It is currently blocked since it waits for this copy definition. Here is how it looks on desktop.

In this case, I would replace the “Try another source” with “Try an external source” to follow the idea shared initially.

Non-supported content type (video)

In previous conversations, we decided to create a page for the upcoming content types to show the existing external sources. We started with video for now, but this page applies to any future content type we decide to support.

Here is a screenshot of a design I am working on and plan to share once we find a path for this discussion.

For this page, I would replace “Try one of the additional sources below” with “Try one of the external sources below.”

Meta search page

Finally, the meta search page needs multiple updates by replacing and adding these two terms ("external sources" and "coming soon"). Something that we can do in parallel to control this ticket's scope.

Let me know what you all think of these changes.

As the comment above lists the changes necessary for moving out from "additonal sources" to "external sources", I am linking the tickets related to this update:

Content switcher

• [x] Replacing "additional types" with "coming soon" in WordPress/openverse-frontend#1665

Metasearch section

• [x] Replacing “Try another source” with “Try an external source” in the metasearch section, next to the dropdown menu in WordPress/openverse-frontend#1665

Non-supported content type

• [ ] Replacing “Try one of the additional sources below” with “Try one of the external sources below" in WordPress/openverse#507

Metasearch page

• [ ] Replacing and adding the "external sources" and "coming soon" phrases. WordPress/openverse-frontend#1766

@zackkrida The "Non-supported content type" refers to the non-supported page, like video results. I am not sure if you linked the incorrect issue or if we are tackling that change in WordPress/openverse-frontend#1665.

@dhruv mentioned the change I pointed out in this comment.

Reopening for the page changes needed in WordPress/openverse-frontend#1766

@panchovm you are right about the 'not supported' pages, I've made a new issue for them here https://github.com/WordPress/openverse/issues/507