Delete old version of notelife3/25/2023 ![]() you can put this in a simple script to look for editions under branch/EDITION, check creation date of an edition and if it matches your condition then delete it using iwrmed CLT.From _future_ import absolute_import, print_function, unicode_literals import boto3 # This script removes all versions except $LATEST and the newest version # If this script tries to delete a version any alias is using, # boto3 will throw an exception and the script will exit def clean_old_lambda_versions():įunctions = client. this can not be done for a specific file or folder, it is a branch level operation so any content changes versioned in the deleted editions will be gone. Let me try out with scripts.ġ) if you have data/editions from many years ago and your organization doesn't need frequent access to content history, then it is time for some archiving and cleaning up? split your content store to archive store and active/default store or just delete portion of it assuming you have backup some where in case of you need to go back.Ģ) again if your organization doesn't need immediate or frequent access to content history, then you can just start deleting editions that are older than certain date (a week, a month.). We have large number of file versions and editions since years.We want to automate this, which can save time and space in the future. It's something to build into the logic of you application, if you expect a lot of unnecessary file versions being submitted. but it will always happen in a way that wipes out entire editions (so all versions of all files in those editions, unless the file version is still needed for a remaining edition). So to the original poster: yes, you can delete (to some extent) old versions. That cleans up a lot of DCR (news item) file version and news overview file versions. I believe it's after 1 month that all editions except 1 per week, are deleted. ![]() ![]() We have added a daily/weekly maintenance process that deletes old editions. Disk space may be cheap, but total cost and inconvenience is not) and then you add SAN mirroring, and backup durations going up, etc etc. This adds up significantly in disk space (not tera's, but giga's. All those overviews get submitted, editions published & deployed to front-end. The overviews exist in 70 variations (different audience get a different mix of news items and language combos)Įvery 15 minutes of the day, we have a perl process looking at the news items, and building new overviews. This effectively removes it from system knowledge without actually deleting the files. Perhaps rename application to application-readytodelete so you can tell later why you renamed it. It sounds like you’ve already done this since you’ve identified that they’re taking up space. There are news items, and news overviews. Locate the folder containing the old version. Perhaps it might help if you explain the rationale for this? What are you trying to actually do? Why are you trying to do it? If you can manage to get search in the forums to work - you can find some rather detailed explanations of all of this buried within the forums - otherwise you need to do some reading of the manuals and/or get some basic training in TeamSite fundamentals - because you're basing your notions on false premises. I am searching for an automated way of doing it, instead of manually deleting the versions and editions. Even if I delete all the 19 editions, I dont think the versions of the dcrs will be deleted.Īdding to it, I want to apply the same logic to the editions too.īecause, we have larger number of editions, we need to delete the older editions, keeping only the latest. And the rest 19 may or may not have all the versions. ![]() So my 20th edition will have all the 10 versions. For example, Consider there is one dcr with 10 versions. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |