Forum Discussion
Image Tags SharePoint Online
Saw the addition of Image Tags coming to SharePoint online Roadmap ID 68902. Currently, when a user updates an attribute associated to an image or pdf, the space utilized by the image is reserved for the new version. A 20 MB image, with updated attributes now takes 40 MB of space. Will image tags have the same impact? We need an option to retain only one version (like the old picture lib).
I waited about 3 weeks after uploading the image for the image tag column to appear automatically.
- I've discovered another issue with the Image tags 'column'. When trying to migrate content using a migration tool I'm getting an error indicating an issue with the column in the destination site. The key problem I have is that I can't find a column labelled Image Tags, pr Tags in site columns of the site or the central content type site which underpins SharePoint admin content services. I've found a work around, but the issue means I'm not migrating sites as efficiently as I could be.
- Hi Aaron,
My work around is simply to download any images and upload into destination library. Version history and other metadata for images not that important for my organisation. The point of the migration tool is to allow you to retain version history and is intended to be more efficient. Within the tool itself, you can usually set rules about what to terms to use in columns to get around missing terms at the destination, but because the 'Tags' or Image tags column doesn't show up anywhere, this approach can't be used.
This issue is also preventing me from copying an entire site and its structure, so I'm forced to just copy the content, which is a lot slower.
First of all, it is quite "remarkable" that the roadmap ID 68902 no longer exists.
At the end of the day you have several options but none offer a silver bullet.
a. Status quo
i.e. do nothing and watch quota being consumed by the versions. You may end up purchasing extra storage if you exceed your quota.
b. Use tools (link) or scripts to manage document versions
Metafore: you have a leaking tap and instead of fixing the tap you mop up the spill.
c. Use tools that allow users to modify properties without adding a new versions
If the tools use e.g. validateupdatelistitem via REST API (link) properties can be changed without adding new version. I am not aware of any tools offering this capability for existing SharePoint documents.
(we develop tools for SharePoint and this seems to be a useful feature. Something to put on our roadmap 🙂 )
d. Disable versioning in the library
e. Wait for a feature to be included into the SharePoint roadmap.- Deployed on commerical tenant. The "No Versions" option is apparently only on libraries on communication sites and I just had not noticed that before. The Team site libraries do not have a "No Versions" option and therefore a tool or an automated process will be the path forward rather than the brute force option. when the image tags are initially established, there is no new version created. When a user applied tag is added, a new version is created and the space allocation that goes with it. I assume that's so that Microsoft Viva can add tags without blowing up the storage. Image Tags does show in the library as managed metadata.
- Thanks Paul.
At this point, we're taking multiple approaches as you mention. While we are monitoring to see how Microsoft will deploy the Image Tags, we are also pursuing a flow to eliminate previous versions. Also, Image Tags have appeared (not fully implemented but enough to get some insights. They're showing up on Communication sites. Tags have not been removed, but Image Tags have been added. The ability to set the library to "No Versions" does exist on the libraries on the impacted communication sites, but nothing has yet appeared on Teams sites. On the Teams sites, there are no Image Tags and the libraries have no option to turn off versioning. I did add a tag on the communication site but need to verify the space utilization. Thanks!- Update. Team Site libraries still do not have an option to turn off versioning so the flow will be key for us moving forward to reduce the storage impact.
MElkinsKG no reaction at all? It's getting more and more a problem. We work with bigger files (like 300MB or bigger) If someone edits 5 metadata fields, there are 6 versions and eacht version is 300MB.
- One thing I noticed. Communications sites have the option for "No Versions" while Team sites apparently do not (default to 500 but can be set to 100 as the minimum). Otherwise, we're looking at Power Automate to remove old versions. There are some samples out there to make that process a bit easier. Image Tags are on my tenant now so getting to do some testing. The initial Image Tags do not cause a new version. User-added tags do.
- Nothing yet!
Nothing yet on how to turn it off?
