The info is useful, but to actually manage storage usage it would be extremely helpful to have ready methods to replace existing images in Media Manager when doing updates to pages that include images. Otherwise, endless duplicates of files are generated with updates that involve importing images. Not good for storage management.
When importing content into a Collection, the _id field can be set and therefore that content can be replaced with subsequent updates by saving it with the same _id value. But with Media Manager, the importFile() function does not seem to enable that kind of replacement. The fileName value is a promising analog, but it isn’t clear that an image can be replaced by assigning the same fileName as part of the Meta Data. In fact, there is additional confusion about using the fileName because it is flagged as “deprecated” and the link to “learn more” is defunct.
If a unique fileName is designated in the metadata for importFile(), can that image file be replaced by assigning the same fileName to a subsequent image? With fileName deprecated, is there another way to uniquely identify an image when it is imported and then use that identifier when importing a new image so that it replaces the existing image?
Such capability really is needed to genuinely support efficient storage management.
Thanks for clarifications about this.