[MAGNOLIA-8054] Consider adding copy metadata to copied JCR item Created: 09/Apr/21  Updated: 28/Jun/22  Resolved: 28/Jun/22

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

Type: Improvement Priority: Neutral
Reporter: Federico Grilli Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-8053 Copying JCR items should strip activa... 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)
Epic Link: metadata-sanitization

 Description   

Follow-up to MAGNOLIA-8053.
When copying/duplicating an item, consider adding some copy/duplicate metadata properties, so that we can track these things and solve issues that might occur from users performing certain sequences of actions.

Evaluate with architects use cases, benefits and costs of such additional properties. E.g.

'mgnl:copied: 'af4cd608-2dda-4535-a5e0-703ef92fd45a'
'mgnl:copyPath: '/travel/tour'
'mgnl:copyDate: '2020-10-09T13:06:18.916+02:00'

or

'mgnl:duplicatedFrom: 'af4cd608-2dda-4535-a5e0-703ef92fd45a'
...

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