[MGNLUI-6294] Sanitize metadata when executing actions Created: 08/Oct/20  Updated: 15/Dec/22  Resolved: 28/Jun/22

Status: Closed
Project: Magnolia UI
Component/s: actionbar
Affects Version/s: 6.2
Fix Version/s: None

Type: Epic Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
Template:
Epic Name: metadata-sanitization
Acceptance criteria:
Empty
Date of First Response:

 Description   

When using actions like copy, duplicate, import, ect. metadata should be removed or reset to reflect the actual state of the target node, not the source.

Metadata such as activation status and modification status should be removed. The target node should be treated like a new node.

Consider introducing new metadata like mgnl:copiedFrom or mgnl:duplicatedFrom to help track the history of a node. From a support perspective, it's getting really hard to understand what users are doing to end up in these obscure corner cases.



 Comments   
Comment by Luke Trueman [ 09/Mar/21 ]

Good morning rgange . H&B were asking about this one yesterday as a solution to SUPPORT-11897. Can we factor this into the prioritisation of the ticket?  

Comment by Richard Gange [ 27/Apr/21 ]

slutz fgrilli rkovarik

So it looks like something broke with create page (see SUPPORT-12985). Investigating further it seems like every app is behaving differently. I'm not sure what we should do or what is the correct way.

  • pages-app: create page does not have created or modified metadata.
  • stories-app: create story does have created and modified metadata.
  • dam-app: upload asset only has modified metadata on the mgnl:asset node. there is created data on the subnode which holds the binary.
  • config-app: create content node does not have created or modified metadata.

I guess what I am getting at is every app is behaving in a slightly different way. It seems to me that creating something whether is be a page, story, asset or generic node should be the same. Shouldn't it?

Comment by Roman Kovařík [ 28/Apr/21 ]

Is this question related to this epic or not (caused by recent changes)? I guess not (MAGNOLIA-8053: 6.2.8, the support ticket 6.2.7).

I though this epic is only about publication metadata, not about created or modified. Could we create a new ticket for the problem?

Btw. MGNLUI-6284 is closed as done with a fix version but bitbucket shows only one declined PR.

 

Comment by Richard Gange [ 28/Apr/21 ]

rkovarik I'm pretty sure that MAGNOLIA-8053 was also released with M6.2.7 SP1 which he could also be using. I'm not 100% sure.

Modified metadata is involved in 8053. So I assumed this was the root of it. I will for sure create a new ticket but what I am confused about is should modified metadata always be there? Even for create? It seems like it has to be because of the column in all apps. Or should the column be modified to fall back to created metadata.

Btw. MGNLUI-6284 is closed as done with a fix version but bitbucket shows only one declined PR.

Maybe the actual fix was not attached back to the ticket?

What I was getting at about pinging you guys is I am confused about how this should be working. It seems to me that modified has to be there even when a node is created initially. This is something I was overlooking before. I want to be sure I get the tickets correct so we don't have to keep revisiting it.

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