[MGNLDAM-809] New assets app UX polish Created: 25/Oct/19  Updated: 23/Oct/20  Resolved: 24/Feb/20

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0

Type: Improvement Priority: Neutral
Reporter: Anja von Gunten Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 58m
Original Estimate: Not Specified

Attachments: PNG File Bildschirmfoto 2019-11-19 um 09.22.32.png     PNG File assets name required.png     PNG File new assets app.png    
Issue Links:
Relates
relates to MGNLPN-468 UX Consolidation for migrated apps Closed
causality
is causing MGNLDAM-824 DOC: Update the visuals related to th... Open
dependency
is depended upon by EXTDAM-36 After uploading an asset to Bynder, w... Closed
is depended upon by EXTDAM-37 (Bynder) Upload action is available w... Closed
duplicate
is duplicated by MGNLDAM-830 Bring 6.2 asset form at par with 6.1 ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Migrate apps to new UI framework
Sprint: UI Framework 16, UI Framework 17
Story Points: 5

 Description   

A few polish items to ensure a smooth UX:
 
General

  • Rename app tile to "Assets" instead of "DAM“ (maybe add "NEW" for interim purpose)
  • Hide the first browser app (where currently all DAMS are combined / read only)
  • Show all DAMS separately in isolated sub apps with their according actions
  • Use the Assets icon instead of the JCR icon for all tabs 
  • Make sure the green app icon for Assets always shows on the first tab

Magnolia Assets

  • Rename tab name from JCR assets to "Magnolia Assets"
  • Make sure all actions are available (as before)
    • Paste action is not available after cut
    • Copy and paste actions are not available when multiple assets are selected
  • Make sure all browser columns are available (as before)
  • When deleting an asset
    • rename action to "Publish deletion" instead of only "Publish" (as before)

3rd party DAMS naming

  • Use "<3rd party name> Assets“ for the tab name of sub apps that connect to a 3rd party tool

See also UX guidelines for migrated apps at https://wiki.magnolia-cms.com/display/DEV/Migration+of+Magnolia+stock+apps+to+M6

  • Set explicit app group to Edit (+ app position after Pages)
  • Fix app label ("Assets", not DAM)
  • Hide old app or even consider unbundling
  • Fix column captions and widths/expand ratios 


 Comments   
Comment by Roman Kovařík [ 09/Dec/19 ]

For the record, most of these issue might be solved by extracting JCR part as a separate app.

Comment by Roman Kovařík [ 17/Dec/19 ]

Add status column (activation state)

Only JCR has an activation state, other asset providers don't have such state for its items.

Add default actions to action bar (currently action bar is empty)

As this browser is read only, which actions it should have?

If there is only an internal DAM and no other provider,
1. don't show top level node
2. don't show single DAM view in 2nd tab (because it's the same
3. disable provider dropdown (column filter) (because there is nothing to choose)

Doesn't 2. solves 1. and 3.? And in the end it actually means that JCR assets app could be separated which would solve all the issues. For the assets chooser it would still use the dam-all app, just dam-all doesn't have to be in the app launcher.

The biggest problem when mixing multiple browsers is returning to the first tab after closing a provider specific detail.E.g
1. Go to JCR assets
2. Edit an asset
3. Save.
4. You're back to main Assets browser instead of JCR assets browser (this is intentionally implemented as the only browser is expected to be in the first tab and Magnolia apps usually don't have multiple browsers so this hasn't been a problem).

If there are multiple DAMs
open the single DAM views per default (is implemented already)
make tabs for single DAM views closable (add close button)
on double click on the DAM provider node (in main tab) open single DAM view (in a 2nd tab)

That is good idea (no matter if we decide to have separate apps or just subapps).
We just have to create connectors apps (subapps) names with certain pattern (e.g. assets-providerName).
Some connector doesn't have to have a custom browser (read only), that could be covered by availability rule (action to open provider would be grayed out)

Generated at Mon Feb 12 05:03:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.