Uploaded image for project: 'External DAMs'
  1. External DAMs
  2. EXTDAM-350

PoC. DAM based on S3

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Neutral
    • None
    • None
    • None
    • AuthX 8
    • 5

    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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                yen.lactue Yen Lac Tue
                jalonso Jesus Alonso
                AuthorX
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Remaining Estimate - Not Specified
                      Not Specified
                      Logged:
                      Time Spent - 8d 1h 1m
                      8d 1h 1m