WordPress / openverse

Openverse is a search engine for openly-licensed media. This monorepo includes all application code.
https://openverse.org
MIT License
254 stars 204 forks source link

Unexpected url from Provider link in Single result view #560

Open fcoveram opened 2 years ago

fcoveram commented 2 years ago

Description

Clicking the provider link on the audio metadata information takes you to the track page on the provider rather than the provider's main page. Reported by @sarayourfriend

Reproduction

  1. Search anything.
  2. Open one result to see the single result view.
  3. Click on the provider's name in the Audio information area.
  4. It opens the audio link instead of the source site's homepage.

Solution

We will need to read from the provider store inside of these components and switch from using the image's foreign landing URL to using the source URL of the provider.

Resolution

krysal commented 2 years ago

This made sense to me in the audio view because the main button was for downloads, there wasn't a "Go to the audio's website" button/link but also it's the same behavior in the image view. Personally, I think is fine this way but I understand there can create confusion. What do you think @panchovm?

fcoveram commented 2 years ago

As more I think of this, I believe we need to switch to "Go to the content site" button for all content. This because we will start integrating the search engine in core, and because it solves the friction we might have with providers on redirecting user traffic.

obulat commented 1 year ago

@panchovm , do we need to change the provider link to link to the provider's main page for this issue? So, for this screenshot, the "Science Museum - UK" should link to the home page of the Science Museum "https://www.sciencemuseum.org.uk/home"? Or maybe we need to link to the page of the open collections on the provider ("https://collection.sciencemuseumgroup.org.uk/")?

Screenshot 2022-12-13 at 9 00 18 AM
fcoveram commented 1 year ago

I am drawn to link the source homepage as the field shows the source name. Landing on a collection page also makes sense, but in this case, the section mentions the organization responsible for the content.

Since the link opens an external site, we should add the external icon.

Note that this change is in line with allowing entry points to see source results in Openverse, an idea we have discussed before. But for that case, it seems better to replace the "Related images" heading with actions going to related content, content from same author, content from same source, content in collections, and so on.

obulat commented 1 year ago

We have updated the source and provider links to link to the main sites of the providers or the sources.

However, now it is confusing for items with sources that are different from providers.

For instance, this image is from SpaceX as source, and Flickr as provider. Source links to the SpaceX main page because that is the link that we have in Django admin for the SpaceX source.

I think we should link to the homepage of the open media collection of the provider and the open media collection page of the source.

So, for a SpaceX image, I would prefer to link to https://www.flickr.com/people/spacex/ for source and https://flickr.com for provider. For Smithsonian images, for instance Stage Design by Angelo Toselli, to link to https://collection.cooperhewitt.org/ (instead of the current https://www.cooperhewitt.org/) as source and https://www.si.edu/search/collection-images for provider (currently, we don't have a record for Smithsonian at all in Django admin.

fcoveram commented 1 year ago

I agree it's confusing

I think we should link to the homepage of the open media collection of the provider and the open media collection page of the source.

Very much agree with this. The link should open the collection landing page in the provider site.