Problem/Motivation

Finding the correct file through media library dialog can be difficult because, for most media types, the only information user is given in the UI the name of the media entity. The media entity name doesn't always provide enough context to allow finding the correct file. Name isn't also a reliable way for users to locate the file from the media list page because names aren't unique.

Proposed resolution

Provide an interface for users to preview media entities in the media library dialog. The preview could be opened to another dialog so that the state of the media library dialog wouldn't be lost.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#2 media-old-exploration.png43.23 KBckrina

Comments

lauriii created an issue. See original summary.

ckrina’s picture

StatusFileSize
new43.23 KB

As a really initial thought on this, we did some explorations during Media sprint in Barcelona, that would let us use a table/list where we would see more info for fields, for example. If I recall it properly, we discussed as an initial solution for this to have a list (not gallery, but more table-like) of files, with info like size, timestamp, author by default, and a gallery for images. Here's an screenshot of the "switcher" if the user would like to switch between the two views.
Anyway, I'm pretty sure this initial idea could be improved in several ways.

This is a very old exploration, please focus only on the "switcher".

lauriii’s picture

We already have the option to switch the list mode to table. However, it's not the default behavior. Also, the table doesn't really provide all that much of contextual information at the moment to really solve this issue.

Providing a preview for videos would be easier compared to PDF and other document files. Maybe the first step for other file types than videos would be to provide a link to the file so that it can be downloaded for checking the accuracy of the file?

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

luksak’s picture

Previous media library implementations like entity browser and D7 media supported something like "My media" that only displays media entities created by the current user. I think in some cases this can be helpful.

I've been searching for an issue regarding this, but couldn't find any. Should we create a new issue for this?

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

phenaproxima’s picture

Category: Bug report » Task
Priority: Normal » Major
Issue tags: +Media Initiative, +Triaged Media Initiative issue

I would not consider this a bug; everything is working as designed, but it could certainly be better. But since this is a pretty important aspect of the media library's usability, I'm bumping up the priority.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.