Better handling of maintenance jobs with mass amount of records

Joris Wynendaele [Aprimo] 9 months ago in Digital Asset Management updated by petra.tant 9 months ago 3

As an administrator, I would like to have better support for maintenance jobs that include +100k assets. That includes:

- No timeouts when submitting a job that has a large number of records

- An easy way to find the "parent" maintenance job and follow up on it

- A good way to resave all assets in the DAM

- Ability to make changes to 100K assets via the "Edit Records" functionality

Content Types / Metadata Fields / Attributes Maintenance

Some of these remarks will be taken into account when redesigning bulk editing on the new DAM UI.

Metadata updates will always be critical to be done in bulk, whether it is to cleanup existing data issues for issues during activations/migrations, or adding new data that will need to apply to all or a large sum of our assets.  We need the ability to easily run bulk metadata updates and have confidence that all data has been applied and cached in the search index.