[EXTDAM-182] Support S3 metadata using 'S3 Tags' Created: 23/Oct/20  Updated: 03/Feb/23

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

Type: Improvement Priority: Minor
Reporter: Ilgun Ilgun Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
causality
relation
is related to EXTDAM-331 In S3, fix the delivery endpoint remo... Closed
is related to EXTDAM-326 S3 Provider Asset Reference Resolver ... Open
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)
Documentation update required:
Yes
Date of First Response:
Epic Link: AuthorX Support
Team: AuthorX

 Description   

Currently, we can only add a 'name' to S3 asset. It is how S3 usually works since it is not a primary DAM solution. However, we can work this around using S3 Tags to add metadata.

 

AC

  • Integrate with S3 tags to offer customers add arbitrary information to their assets
  • Name of 'tags' 'fields' can come from App configuration.
    • So that it is generic for any customer out there.
    • Have meaningful defaults which are aligned with other DAM systems e.g. description

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