Skip to Content

Incorrect links to Jive Documents migrated to Wordpress Blogs

Hi 1DX team

In the latest blog migrations, the Jive Documents have been converted to Wordpress blogs. That is brilliant and very much needed.

However, other blog posts that refer to these "converted blogs" are still refering to the Jive Documents migrated to the Archive.

Refer to the following examples of a blog which has links to Jive documents:-

Old SCN (current)

FormatConversionBean - One Bean to rule them all!

New SCN (Beta)

FormatConversionBean - One Bean to rule them all! - SAP Blogs

In the above blogs, there is a table which contains a link to other Jive documents under the column Reference.

After the migration, the Jive document has been converted to the following Wordpress blog.

ExcelTransformBean Part 1: Convert various Excel formats to simple XML easily - SAP Blogs

However, the links still point to the following document in the Archive area

ExcelTransformBean Part 1: Convert various Excel formats to simple XML easily

Regards

Eng Swee

links.PNG (22.4 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    Posted on Sep 08, 2016 at 08:01 PM

    Hi All,

    Regarding Eng Swee Yeoh's original questions (@Jeremy Good: you hijacked! not nice ;-) )

    Thank you for pointing out the redirect issue you found in the beta. I'm happy to report that this is just a temporary situation due to the fact that these are test iterations of migrations and not the actual final migration of items. We should not have this issue once we launch, since everything should at that point have a redirect one way or another.

    Regarding the question of migration to blogs for all Jive documents regardless of who posted them, we have two different approaches because of the fact that SAP employees and contractors have used the native Jive document format very differently from externals. While it may seem on the surface like we're migrating differently whether you work for SAP or not, it's actually the case that we are migrating differently based on what kind of content has been posted in native Jive documents.

    I hope that clarifies.

    Regards,

    Audrey

    Add a comment
    10|10000 characters needed characters exceeded

    • I do agree that the redirect-based solution will allow more flexibility post go live, the only thing is we will only be able to test/experience it after go live.

      I'm not sure if this redirect solution was mentioned anywhere else, so it wasn't entirely clear what was happening, but thanks for the explanation, Michael.

      Just to confirm, this redirect is only applicable for Jive Documents, so we will expect links to those to remain as DOC-XXX links, while Jive Blog links will still be converted to blogs.sap.com links.

      Looping in @Jitendra Kansal since he had an issue with one of the Jive document links too.

  • Posted on Sep 07, 2016 at 05:16 PM

    Hi Eng Swee,

    Your comment caught my attention: "In the latest blog migrations, the Jive Documents have been converted to Wordpress blogs. That is brilliant and very much needed."

    Do you think this should be the case for all relevant Jive DOC-XXX objects, including SAP employee contributions, or only customers and partners in the community?

    Best Regards,

    Jeremy Good

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 06, 2016 at 06:24 AM

    Let's ping @Audrey Stevenson

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 07, 2016 at 03:23 PM

    Thanks for pointing this out. I'll circle back with the team to understand what should be happening.

    --Adurey

    Add a comment
    10|10000 characters needed characters exceeded