[MGNLCT-112] Augment external content in an app Created: 13/Feb/19  Updated: 02/Apr/19

Status: Open
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Release notes required:
Yes
Documentation update required:
Yes
Epic Link: External Content

 Description   

As a developer, I want to enable authors to augment external content in a Magnolia app.

As a content author, I want to augment external content in a Magnolia app so that I can tune the content for my specific use case.

An author should be able to use the standard Magnolia editing tools on external content, but the external content is not changed, rather the changes (the "augmentation") is stored locally (in JCR).

For example:

  • Author can change the price of an external item,  and that price is used only for the particular web project they are working on.
  • Author can change the marketing copy of an external item to work better for the customer of just this current web project.
  • Assets could be stored remotely (such as s3) and authors can still add metadata in a Magnolia app to these assets via augmentation.

It should be possible to add additional fields (not just to change existing fields) to external items. (A developer would need to configure that additional fields are available.)

For example:

  • An asset comes from an external DAM. The external DAM doesn't have all the metadata fields we need. Developer configures the fields: Caption, Copyright and Tags to the content type in Magnolia, and now an author can add values for them.
  • A product comes from an external PIM. In Magnolia we add a new field "Star Rating" to the content type (as mentioned above). 

 

Acceptance Criteria:

  • As a developer I can enable content augmentation on a content-type, or in an app. I have to provide the ct model and any app-ui tuning, I control which fields are available for authors to edit, just as with a normal app or jcr-based content type.
  • As an author I can see which items have been augmented in the browser view, probably via a dedicated column.
  • As an author I can easily remove augmentation of items in the browser view, probably with an action.
  • As an author I can access an edit dialog which allows me to augment the external content with local content.
  • As an author, I can tell which fields have been augmented, and which just show external content. (Maybe 2 fields for each property, remote & local?)
  • Works with light development.

Generated at Mon Feb 12 00:37:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.