[EXTDAM-350] PoC. DAM based on S3 Created: 05/Apr/22  Updated: 17/May/22  Resolved: 05/May/22

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Jesus Alonso Assignee: Yen Lac Tue
Resolution: Done Votes: 0
Labels: authx
Remaining Estimate: Not Specified
Time Spent: 8d 1h 1m
Original Estimate: Not Specified

Issue Links:
Relates
relates to EXTDAM-353 PoC. DAM based on S3 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: TPR SaaS Norsu Assets
Sprint: AuthX 8
Story Points: 5
Team: AuthorX

 Description   

The s3 connector has several limitations such as moving or renaming assets & handling metadata. Unfortunately, the S3 API prevents us to overcome these limitations. However, these functionalities are needed in SaaS. 

We want to use a new mixed connector which stores all the metadata in our datastore (JCR or Norsu) but the asset is stored in S3. Then, if an asset is moved or renamed, the S3 asset is not affected, only the metadata is affected.

We want to do a PoC implementing, extending the magnolia-dam-app-jcr to

  • A new asset is stored in S3 but the metadata is in JCR.
  • We use S3 links to render assets
  • When an asset is deleted, the S3 asset is deleted too.

Generated at Mon Feb 12 01:54:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.