cancel
Showing results for 
Search instead for 
Did you mean: 

Migration of Collaborative Documents to Archive instead of Blog

engswee
Active Contributor
0 Kudos

Dear 1DX team


Thank you for sharing the updates of 1DX during yesterday's call.


I had a question yesterday regarding the content migration of what is called (Collaborative) Documents in the current SCN Jive platform. I couldn't hear the response clearly during the call, but I think Oliver mentioned something along the lines that these will be migrated to the archives since there is no Content Strategy for Documents.


I've checked and indeed found some of the Documents I wrote were in the Community Archive and do not appear in the list of contents under my profile.


I'm not sure about others, but this is a concern for me because I regular post content as Documents. Such content are normally How-To guides or posts that are technical in nature (instead of opinions and reviews which I post as blog). I do this in line with the following guide by Jason Lax as well as the "Knowledge Sharing"/Tutor missions which recommends using Documents knowledge sharing.


Additionally, I regularly maintain and update these posts, and having them as Documents in the current platform allows the updates to appear in the activity/notification stream. This "notification" element is useful because some of them are like Configuration guide to some of the open source solutions that I publish and regularly enhance. This allows community members following the space to be aware of new features or bug fixes, etc.


My concerns that these are migrated to the archive are:-

1. The archive contents are read only and no longer allow modifications/updates by myself or comments by other users on the content

2. They no longer appear under my list of contents so having them in archive might effectively relegate them to obscurity unless someone knows specifically the search terms needed to find them


I'm wondering if it's possible for these to be migrated into blog posts in the new platform instead. These will allow these documents to continue to be live documents and allow interactions on them.


Regards

Eng Swee

Accepted Solutions (1)

Accepted Solutions (1)

brianbernard
Community Manager
Community Manager
0 Kudos

Hi Eng Swee,


We plan to migrate externally-authored (non-SAP) Jive documents to WordPress as blogs. This will preserve the kind of editing and interaction you’re asking about.


Meanwhile, we have set up a task force for to deal with the internal use cases for Jive “collaborative” documents – it’s one of the highest priorities right now.


Brian

Matt_Fraser
Active Contributor
0 Kudos

Thanks for this clarification, Brian. Are we to understand, then, that at this point in the beta, not all of our content has been migrated? Right now in my profile I see a total of 10 blogs, nothing else, and none of my documents are among them, but on the Jive side I have significantly more than 10 blogs even without counting the documents.

And there are one or two old discussion threads I wouldn't mind preserving. I'm thinking Coffee Corner here, where blogs are currently not allowed, so all posts are discussions. I'd hate to lose the ABAPer's Holiday Carol! After all, it's referenced from my MoM post, and all....

Matt

brianbernard
Community Manager
Community Manager
0 Kudos

For sure the document archive is incomplete. At this point, I would just consider it a way to see what it will look like. It's going to be updated with the "actual" content.

I can't really speak to the blogs, but it's safe to assume the migration hasn't been perfected .

engswee
Active Contributor
0 Kudos

Hi Brian

Thanks for the update. I'm really glad to know that the externally authored documents will be migrated to blogs.

IMHO, I think there are also a fair deal of SAP employee authored documents that are worth migrating to blogs in WordPress. Some that come to mind is from Alexander Bundschuh in the SAP Process Orchestration space that deals with new features for the product. It will be unfortunate if these are relegated to the archives.

@Matt, regarding the list of contents, I too found that the profile only shows 10. But actually there are more that is already migrated to the blogs section. You can find them if you click any of your migrated blog, then click on the "more by this author" link next to your profile pic. It will bring you to a list of all your contents, with an "Older post" link included to see other contents.

Regards

Eng Swee

oliver
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Eng Swee,

this is currently a bug in SAP People profile, or call it a missing feature. we still don't have pagination implemented but have already started working on it.

Best,

  Oliver

brianbernard
Community Manager
Community Manager
0 Kudos

Regarding your statement, "I think there are also a fair deal of SAP employee authored documents that are worth migrating to blogs in WordPress."


No doubt. In fact I would say there are many important use cases for SAP-authored documents - and that's exactly why there is work going on behind the scenes to vet the use cases and find proper solutions for the different types of content produced by SAP.

engswee
Active Contributor
0 Kudos

Thanks for your reply, Brian. I'm really glad to hear the ongoing effort to preserve the existing wealth of information and knowledge (whether external or internal to SAP) as we move to the new platform. Keep up the good work and looking forward to the new platform

Answers (2)

Answers (2)

moshenaveh
Community Manager
Community Manager
0 Kudos

Let's loop-in

Matt_Fraser
Active Contributor
0 Kudos

I share this concern. I always felt the distinction between blogs and "documents" was rather arbitrary (and documents can suffer from unfavorable SEO compared to blogs), so I'm happy to see them combined in a single category. But meanwhile, there is valuable and active content that currently exists as documents that I think we'd want to maintain. I too have a mix of such content types.

Cheers,

Matt

steverumsby
Active Contributor
0 Kudos

The distinction for me was always that documents are collaborative - can have multiple contributors - while blogs are not. I know some documents are used that way, but maybe not all. Does this mean that in the new platform there's no option for collaborative documents? Or is that what the wiki is for? I was always more confused between wiki and documents that between documents and blogs .

I would think that how to migrate documents will depend on whether or not they are intended to be collaborative. Wiki if yes, blog if no. But a read-only, inactive archive doesn't appear to be right...