collective user

[SelinaKurtz]

Our team would like to create blogpost. Since we would like more than one person to be responsible for this, is it possible to get a collective user for the SAP Blogs Community? If so, how can we get a collective user?

[jerryjanda]

Hi, Selina:

I'm a member of the Community team. I accepted Jelena's answer because she's correct. What you're proposing would work best as a wiki page (where multiple owners can contribute). That's not how we would define a blog post. A blog post should come from an individual and carry the author's voice.

Please feel free to reach out to me. For now, if you haven't already, your colleagues and you should check out https://community.sap.com/resources/blogging and https://developers.sap.com/tutorials/community-blogging.html. I also recommend that you all join our internal group for SAP employees, which also has specific guidelines for employees seeking to contribute to SAP Community. If you can't find it, please contact me.

--Jerry

[Jelena_Perfiljeva · Accepted solution]

Selina, this question has been asked before and the answer was - this is not advised or supported on SCN. I believe that general idea is to represent just yourself, as a real person, on SCN. Even though the "collective accounts" existed before (not from SAP but usually from some consulting companies) these were always frowned upon.

Possible alternatives are: mentioning (using "@") other authors in the text and using Wiki instead of a blog or to organize blogs by multiple team members.

[TammyPowlas]

Selina - on the SAP side, I am not aware of a user, but I do like the way jelena.perfiljeva2 (or her alter ego) crowd-sourced this blog: https://blogs.sap.com/2013/10/25/sap-teched-day-four-where-my-blog-gets-crowdsourced/

[agentry_src]

Alternatively they could use the pre-packaged addon for WordPress that allows multi-author documents. Could have done this back in the early days before the SCN migrated to SC as it was brought to the attention of the system architect.

For some unknown reason, it was not even evaluated. And this was even though multi-author documents were on the requirements list for the new implementation. Wonder what the logic was behind that decision.