Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEATURE monitoring of purchased asset expiration #169

Closed
tdausner opened this issue Jan 11, 2023 · 4 comments
Closed

FEATURE monitoring of purchased asset expiration #169

tdausner opened this issue Jan 11, 2023 · 4 comments

Comments

@tdausner
Copy link

Description

For management of purchased assets the IPTC ApplicationRecord tags 37 + 38 (ExpirationDate + ExpirationTime) should be monitored on asset delivery.

Steps to Reproduce

  1. [First Step]
  2. [Second Step]
  3. [and so on...]

Expected behavior

Monitoring of IPTC ApplicationRecord tags 37 + 38 (ExpirationDate + ExpirationTime)

  • on expiration the asset is not delivered. Instead a dummy asset is delivered.
  • on expiration an email is generated. Recipients (and message) are yaml configured
  • the mentioned IPTC tags are editable, if not set

Actual behavior

No asset expiration monitoring

Affected Versions

Neos: *

UI: *

Media Module: *

You can get this information by running composer show or using the package management module within Neos.

@Sebobo
Copy link
Member

Sebobo commented Jan 12, 2023

Thanks for the topic. I don't see this in the UI package as it related more to the media API and core functionality/extensibility.
The editable IPTC metadata is covered by #98 which you can comment with the specific requirements/fields.

Therefore I would move the issue to Neos itself if this is fine for you?

@tdausner
Copy link
Author

You're right concerning the functionality - it's not UI related. Please move to Neos.
I'll comment on #98 concerning IPTC editing.

@Sebobo
Copy link
Member

Sebobo commented Jan 16, 2023

Seems I cannot move the issue, would you copy the text and open it in the Neos development collection?

@tdausner
Copy link
Author

done. see flow-development-collection#2954

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants