Spotfire Ideas Portal
I would like to be able to publish a version of an analysis file for my colleagues, so they can view it. but at the same time I want to continue developing the analysis file with the next improvement without having my colleagues see the intermediate status (which may be messy and incorrect). When I am done with the update, I'd like to be able to publish this version of the file for my colleagues so they can benefit from my improvement. Then the same cycle starts again.
THIS. This would solve a lot of issues with library clutter, because we would not need to make secondary copies for development and have to deal with potentially changing the library ID on overwrite of the next "official" version and breaking users' bookmarked URLs, etc.
Another way to look at this is a check-in/check-out model, where the last "checked-in" version of a file is what is served to the public, but a private "checked-out" version can continue to be developed by a single user without showing up in search. Even better would be the ability to turn on an approval step in the check-in of certain files, to ensure that changes to "Certified" reports are not published without governance review.