As stated in former posts, I cannot accept just burying terabytes of user generated content (which often was of high quality) in archive.sap.com and that should be it.

IMHO SCN was more than not about having kind of a "meta sticky note" to our professional work life. I often found me in the situation where someone commented on a blog I also commented on, providing a link to a solution. I would then get a notification and had the chance to participate from that solution, maybe weeks later, when my daily business long moved on to the next topic.

I know that this notification behavior might also be re instantiated with new blogs but for heaven's sake, please at least provide a more conditioned way to access our legacy content.

Cheers

Jens

I second that. While the old way was quite inflexible / static and I get the idea using tags to group content together the old communities / places provided a robust entry point. I know about topics, so a workaround might just be to redirect from the old community to the new topic, where applies (or show a selection to the user, where a 1:1 mapping would not make sense). But please don't just kill the links to the communities that were circling around for years and probably are in "muscle memory" for quite a few of your community users.

Cheers

Jens

I'm sorry but it should not be that hard for us. We contributed a lot. We asked questions, we gave answers, we commented on blogs.

Not only did you effectively kill all the notifications on questions, blogs, bookmarked sites where we participated in (it was great that you got a notification when e.g. a new comment to a blog came in you almost forgot by the time being), now you would even refrain from migrating over that content where we participated.

Please at least(!) provide that legacy content somewhere. Give us back our history! All the better revive notifications, too, where it makes sense (blogs, bookmarked sites, etc)

Cheers

Jens

Thanks, this is good news.