Working with INDDs in SaaS is still challenging, even though there are new tools available to manage them (package uploader, CC Connector). We still have clients that are not going to be able to rely on these tool for all their use cases that involve working with INDD. Therefore it would be useful to allow managing publication items on INDD assets manually - in other words have a UI option to link assets in Contains section as dependencies to the INDD (or course providing a way to link to select file version to link) or any alternative OOTB way. Consequently, the dependencies would automatically show where they are linked without additional manual intervention.
Here is a use case: a client is not working with CC Connector because of performance issues (working with large assets with many links is still very slow), they are using package uploader to upload new assets via task or via My Uploads area. However, for certain INDDs where a dependency changes but the filename stays the same (CRC checksum for dependency is changed, but the dependency is essentially the same, just had some minor changes), this client doesn't want package uploader to add a new asset for that dependency, the intention is to add a version to existing asset instead and establish linking between dependency and INDD. There is no way to configure package uploader in this way since it detects duplicates based on checksum. So the only alternative would be for users to manage publication items themselves as they want - manually add a new version for dependency asset, add an new version for INDD and establish linking manually.
In general, even historically speaking, managing links for INDDs has been a problem and we often had to resort to re-ingesting whole packages to fix broken links, when in fact it would've been useful to have an option to manage links manually and make small corrections.
Since this can be a sensitive thing to change, it would be useful to have a functional permission for allowing management of publication items, to make a distinction between users who are able to modify assets and users who are considered power users/librarians that would potentially also be able to manage publication items.
Customer support service by UserEcho