SubAssetExpiry blocks move operation for editors and librarians. | Community
Skip to main content
Adilos-Cantuerk
Community Advisor
Adilos-CantuerkCommunity Advisor
Community Advisor
May 7, 2024
Question

SubAssetExpiry blocks move operation for editors and librarians.

  • May 7, 2024
  • 2 replies
  • 636 views

Hi dear community!
I am looking at something that just been brought to my attention.
We all know that an asset that is expired by prism:ExpirationDate will lose some of its functions (as it should).
The asset will no longer be downloadable, it gets depublished, AssetLink will not longer find the asset etc. pp.
All good stuff.

BUT now the same behavior comes up with InDesign Files that simply contain an expired asset.
isSubassetIsExpired seems to trigger the same behavior - at least regarding the "move" functionality.
*Edit: Even Download is blocked ;(

 

This behavior will make an librarian out of our administrators... they will move a lot of files.

Imagine a single picture that renders 500 InDesign files as SubAssetExpired.

Does anybody know what acls are responsible for this behavior / if it is possible to grant rights to "move"?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    February 26, 2025

    @khamat_bn @monalikakapoor @erika_antkowiak @gkalyan @rahulmohan @tethich This question could use some expert insight—would love to hear your thoughts if you can take a look!

    Kautuk Sahni
    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    April 2, 2025

    @abhishekanand_, @losharma, @digarg17, @sukumar, @raja_reddy Your expertise would be really valuable here! Please have a look at this question when you get a chance.

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...