Decide on a set of fields and meta fields for media entities

Created on 9 December 2024, 4 months ago

The results from the media management survey and subsequent discussions indicate that we do not want to include extensive fields on media entities. We could consider adding a small number of useful fields however for editors to enter on the full media form.

The following is proposed.

'Media Tags' taxonomy reference field for categorisation to enable filtering by user entered category in the media library. Not to appear in content.
A single 'Caption' field to appear below the media item in full display mode only.

An attribution field is not proposed because typically the caption field can be used for attribution, but could be considered.

Let's review and see whether there are reasons for other fields, including SEO and accessibility considerations.

🌱 Plan
Status

Active

Component

Track: Media Management

Created by

πŸ‡¬πŸ‡§United Kingdom tonypaulbarker Leeds

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @tonypaulbarker
  • πŸ‡¬πŸ‡§United Kingdom tonypaulbarker Leeds

    @thejimbirch @pameeela @the_g_bomb I would welcome your thoughts on what fields (if any) we should include on media entities.

  • πŸ‡ΊπŸ‡ΈUnited States thejimbirch Cape Cod, Massachusetts

    In the Drupal CMS SEO Track Plan, we linked to the Google Search Gallery from Define Best Practices Requirements for Drupal CMS recipes section.

    Google defines best practices for image and (non-remote) video entities.

    ImageObject

    Required properties:

    contentUrl

    -and-

    Either creator or creditText or copyrightNotice or license.

    Recommended properties:

    acquireLicensePage
    creator
    creator.name
    creditText
    copyrightNotice
    license

    Caveats:

    1. The schema meta data would have to be set on any entities that use images since they are not standalone entities in Drupal.
    2. Google also consumes International Press Telecommunications Council (IPTC) photo metadata that is saved inside of the image. So anyone that does care about this most likely would set that.
  • πŸ‡ΊπŸ‡ΈUnited States thejimbirch Cape Cod, Massachusetts

    I believe we are not using local video.

  • πŸ‡¬πŸ‡§United Kingdom the_g_bomb

    I think I spotted already you are using the Decorative Image Widget, so that is good for me.

    I also don't like how alt text set when the media is uploaded goes everywhere, context is everything in terms of alt text, so how can there be one size fits all alt text.
    https://www.drupal.org/project/media_library_media_modify β†’ helps to add contextual modifications which means the alt text can be changed per use.

    If we went down the route of components, I would have a lot of requests. for example if there is a caption, an alt text is redundant in many cases. https://webaim.org/techniques/alttext/

    In terms of video most captioning etc should be done at source if we are only entertaining remote video.

  • πŸ‡©πŸ‡ͺGermany breidert

    Hej Tony,

    I second the idea of having an internal taxonomy to classify media. This allows editors to organize their media as they want.

    Regarding copyright (for me this is the same as creator, credit etc.) I would also recommend using a taxonomy. IMO the copyright field should not be mandatory but display in the frontend if it is set.

    I don't think a caption field should be part of the media entity itself. I think the caption is more of a contextual thing and should be entered when the media item is added on a page.

    We use above data model and conception in most of our projects.

Production build 0.71.5 2024