Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-153204

Display what type of basic document is being shown in the Info Panel of the Content Dashboard

Details

    • Story
    • Status: Closed
    • Minor
    • Resolution: Completed
    • None
    • Master
    • Content Dashboard
    • None

    Description

      User Story

      As a content marketer, I want to see the MIME type of a document in the info panel, so that I can better understand the asset I am previewing.

      Design

      Figma

      Acceptance Criteria

      1. Documents selected in the Content Dashboard must show their MIME types (as defined here) in the Info Panel. The MIME types to be displayed are as follows:
        • Code
        • Compressed
        • Multimedia - changed to:
          • Audio
          • Image
          • Video
        • Presentation
        • Spreadsheet
        • Text
        • Vectorial  changed to PDF
      2. Documents with extensions not defined by MIME types will be categorized as "Document - Other". 
      3. Documents without any attached files will be categorized as "Document - Other". 
      4. Custom Documents will be categorized by the Custom Document Type Name.
      5. External Video Shortcuts will be categorized as "External Video Shortcut". 

      Testing Scenarios

      Acceptance Criteria
       
      Testing Scenarios
       
      Test Strategy
       
      Covered by frontend test? (Yes/No)
       
      Covered by backend test? (Yes/No)
       
      Documents selected in the Content Dashboard must show their MIME types in the Info Panel
      • Given a code asset
      • When user open its info panel
      • Then user can see its MIME type as code
       Low  yes no
       
      • Given a Compressed asset
      • When user open its info panel
      • Then user can see its MIME type as Compressed
       Low  yes no
       
      • Given a Multimedia Audio asset
      • When user open its info panel
      • Then user can see its MIME type as Audio
       Low  yes no
       
      • Given a Multimedia Image asset
      • When user open its info panel
      • Then user can see its MIME type as Image
      Medium yes  yes
       
      • Given a Multimedia Video asset
      • When user open its info panel
      • Then user can see its MIME type as Video
       Low  yes no
       
      • Given a Presentation asset
      • When user open its info panel
      • Then user can see its MIME type as Presentation
       Low  yes no
       
      • Given a Spreadsheet asset
      • When user open its info panel
      • Then user can see its MIME type as Spreadsheet
      Low   yes no
       
      • Given a Text asset
      • When user open its info panel
      • Then user can see its MIME type as Text
       Low yes  no
       
      • Given a Vectorial asset
      • When user open its info panel
      • Then user can see its MIME type as Vectorial
       Medium  yes no
      Documents with extensions not defined by MIME types will be categorized as "Document - Other". 
      • Given an asset with no listed MIME type
      • When user open its info panel
      • Then user can see its MIME type as "Other"
       Low  yes yes
      Documents without any attached files will be categorized as "Document - Other".
      • Given an asset with no file uploaded
      • When user open its info panel
      • Then user can see its MIME type as "Other"
      Low  yes no
      Custom Documents will be categorized by the Custom Document Type Name
      • Given a Custom Document asset
      • When user open its info panel
      • Then the asset will be categorized by the Custom Document Type Name
       Low  yes no
      External Video Shortcuts will be categorized as "External Video Shortcut".
      • Given an External Video Shortcut asset
      • When user open its info panel
      • Then the asset will be categorized as "External Video Shortcut"
       Low yes  no

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Validated by QA and Product Manager;
      • No critical bug related to Story scope (FP5 or Impedibugs);
      • Make sure that all system documentation were updated (if necessary)

      Discussion

      Tech refinement document in Confluence

      Attachments

        Issue Links

          Activity

            People

              support-qa Support QA
              joseph.pak Joseph Pak
              Cristina Gonzalez Cristina Gonzalez
              Kiyoshi Lee Kiyoshi Lee
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Packages

                  Version Package
                  Master