Stream Storage in SharePoint and Versioning

%3CLINGO-SUB%20id%3D%22lingo-sub-1750758%22%20slang%3D%22en-US%22%3EStream%20Storage%20in%20SharePoint%20and%20Versioning%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1750758%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20Stream%20moves%20to%20store%20content%20in%20SharePoint%2C%20will%20anything%20be%20done%20to%20address%20versioning%20and%20storage%3F%20We%20have%20document%20libraries%20with%20videos%20in%20them%20where%20users%20have%20updated%20the%20metadata.%20In%20one%20case%2C%20a%201.6GB%20file%20had%205%20metadata%20changes%2C%20each%20resulting%20in%20an%20additional%201.6GB%20of%20storage%20consumed.%26nbsp%3B%20With%20versioning%20being%20defaulted%20to%20100%20versions%20and%20no%20option%20to%20not%20have%20versioning%2C%20this%20will%20be%20an%20issue%20for%20numerous%20companies.%26nbsp%3B%20A%20video%20library%20without%20versioning%20would%20be%20a%20workaround%2C%20but%20losing%20context%20of%20the%20related%20content%20isn't%20great.%20Any%20updates%20on%20this%20moving%20forward%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1750758%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Contributor

As Stream moves to store content in SharePoint, will anything be done to address versioning and storage? We have document libraries with videos in them where users have updated the metadata. In one case, a 1.6GB file had 5 metadata changes, each resulting in an additional 1.6GB of storage consumed.  With versioning being defaulted to 100 versions and no option to not have versioning, this will be an issue for numerous companies.  A video library without versioning would be a workaround, but losing context of the related content isn't great. Any updates on this moving forward would be appreciated.

0 Replies