I have entered a situation–okay, nightmare–where a “SharePoint consultant/expert” before me created a “system” for a set of document libraries with critical artifacts (that can be demanded by government agency-regulating auditors) which is set up with doc lib metadata having multiple year values (in one Choice column) to reflect different annual versions of the documents apparently stored with the same file name. But the previous year files do not exist as separate items in the doc libs, but rather refer to that document of the same name in the version history of each item (!!).
I am trying to explain that this is not how content management is done in SharePoint, and that when my REST API-based search form interface pulls out a link to the document with a Years column with value set to “2015,2016,2017,2018,2019”, that the user will only see the most recent “version” or the 2019 document, and ask “where’s the 2016 document?”
So I want to confirm that it is in the interest of the enterprise for me to write a script to pull out all the versions of every item, programmatically try to rename the file, and painstakingly upload them as separate items with the proper metadata set and only for one year. Much of this is actually manual. There are about 7 or 8 doc libs. One of them has over 5000 items. Or should I look at the existing mass (mess?) of items and script with it?