Wouldn't it then be better to retire the entire blog, it usually has not more than just the link, so it has no value to the community and causes more confusion than it is good
Hi, It was decided that the old repository needs to be reritred. As a result we asked the content owners to plan ahead and audit their content and decide what needs to be migrated. We had close to 20k documents from the last 10 years so not all of them were equaly important. The content the Subject matter Experts thought is important was migrated and if you click on them you get redirected. Those that weren't migrated and goes to a 404 error page can be revived this gives both the community and the owners the grace period to ask for it in case content didn't had an owner or was missed.
To my mind it's an incorrect approach in general! 20k documents is not a huge number and the storage is not very expensive today 🙂
You decided that document author has to review the document with pdf attachment and perform some action. But in many cases the authors are not available or lost interest etc... And the community now has little chance to tell that some document is useful - no way to see the content.
And for the documents without pdf - you decided to migrate all, even for useless documents... No logic...
To my mind it's a strange idea not to migrate all links to pdf content automatically. Why do you need to contact document author? If the old document was created without pdf - it was migrated automatically...
So, I must assume that all archive documents with links to pdf content are not available any more or you are working in a possible solution?. That's a pity because there was very useful material.
If the pdfs got retired then why didn't get the documents removed from the archive?
Such a empty document (https://archive.sap.com/documents/docs/DOC-5628) with a non-working link does not add any value to the community. Contrary it just elevates the frustration of the users who were happy to find something relevant and finally can't get to the content.
Yes the repository was retired and the content that wasn't migrated is going to a broken link, the content that you found was migrated but should have been redirected as well.
We fixed the redirect and when you click on it it goes to the right place.
The strategy was decided elsewhere and the decisions were implemented accordingly.
There were a lot of reasions to do what we did in the way we did it. we migrated a big portion and we are proud of what was migrated.
When it comes to content there is aways a dilema how far back it is realy needed and where do you draw the line. whatever was mentioned i will try to help with if and when possible.
I'm kind of curious about the reasons. I deal with data migration all the time but I don't recall a decision ever made not to migrate, say, a customer account because it was created 4 years ago and we didn't hear back from the sales rep. We'd look for the recent transaction history instead. So I can't really understand why the content that had likes and views in 2016 is now just puff, gone.
Based on at least a dozen of similar questions (and I only scrolled the top 2 pages) about the missing content I gather the strategy was a bit off...
The stategy was based on a lot of moving parts and i like to think that every decision was made by the best people who thought long and hard about every aspect of this migration.
Having said that we had system and platform restrictions and guidelines and worked accordingly.
Exactly the same issue for me as well. Had earlier published an article in SDN.
Recently I was trying to access it and found it was moved to archives.
Even while I reached the archive link https://archive.sap.com/documents/docs/DOC-11457,
I see that the actual post accessible through "View Document" link is invalid.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.