$(function () { pageContext.i18n.modTalk = 'moderation talk'; pageContext.i18n.replyToComment = 'Reply'; pageContext.i18n.modTalkEmpty = 'moderation talk is empty'; pageContext.url.getModTalk = "/comments/%25ID%25/listModTalk.json"; pageContext.url.possibleCommentRecipients = "/comments/%ID%/possibleRecipients.json"; pageContext.url.commentEdit = '/comments/%25ID%25/edit.html'; pageContext.url.commentView = '/comments/%ID%/view.html'; pageContext.i18n.commentVisibility = { 'full': 'Viewable by all users', 'op': 'Viewable by the original poster', 'mod': 'Viewable by moderators', 'opAndMod': 'Viewable by moderators and the original poster', 'other': 'Advanced visibility', 'dialogTitle': 'Comment visibility', 'selectGroups': 'Visible to groups', 'selectOther': 'Other recipients', 'selectOriginalPoster': 'Original poster', 'selectModerators': 'Moderators', 'selectAssignees': 'Asked to answer users' }; pageContext.i18n.commentMenuLabels = { 'comment-edit': 'comments.menu.edit', 'comment-delete': 'comments.menu.delete', 'comment-convert': 'comments.menu.convert' };pageContext.i18n.answer= { bestAnswer: 'Best Answer', controlBar : { accept: 'Accept', unaccept: 'Unaccept', acceptCommand: 'Accept this answer as correct', cancelAcceptedCommand: 'Remove this answers accepted status' } }; window.croles = { u: false, op: false, m: false, og: false, as: false, ag: false, dc: false, doc: false, eo: false, ea: false }; tools.init({ q: { e: false, ew: false, eo: false, r: false, ro: false, d: false, dow: false, fv: false, c: false, co: false, p: false, tm: false , ms: false, mos: false }, n: { f: false, vf: false, vfo: false, vr: false, vro: false, c: false, co: false, vu: false, vd: false, w: false, wo: false, l: false }, c: { e: false, eo: false, d: false, dow: false, ta: false, tao: false, l: false }, a: { e: false, ew: false, eo: false, d: false, dow: false, a: false, aoq: false, ao: false, tc: false, tco: false, p: false, tm: false }, pc: croles }, { tc: true, nsc: true }); commandUtils.initializeLabels(); }); Skip to Content
0

Member since date difference, post migration

Nov 11, 2016 at 06:18 PM

371

avatar image

Before SCN migrated, I asked a question about the "joined" date in my profile:

https://archive.sap.com/discussions/thread/3908597

That question is now marked as "answered" (despite the issue not being fixed), with a pointer to a document on "known issues". That pointer [ http://scn.sap.com/docs/DOC-72804 ] sends me to a page that says it does not exist,

We're sorry, but you're attempting to access SCN content that was not migrated to the new SAP Community experience.

[ https://archive.sap.com/content-not-migrated ]

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Audrey Stevenson
Nov 16, 2016 at 08:18 PM
2

Hi Jim,

So, Veselina was actually correct that the Known Bugs List from the old beta space on SCN has been replaced by the Beta Feedback recap and the Community Known Issues & FAQ page. Due to the large number of small feedback items received between the Known Bugs List and the replies in the Beta Mission post, the team consolidated all of it into bigger items in those two places instead of migrating the old document. In the process, it looks like the "Member Since" item may have gotten lost, so I've added it back in to the Beta Feedback recap.

Regarding the question of what "Member Since" currently represents (the date the account was created in SAP Cloud Identity, as discussed here and in previous discussions before launch) versus what it should represent, this is a bigger issue that we will need more time to address in our team and decide the right path forward.

The definition of "member" is part of the difficulty here, since membership with a cross-1DX, universal profile no longer just means a member of SAP Community. Also, the number of platforms and systems containing relevant date information for account creation and community participation is not small, so what may seem like a simple thing from the outside is actually more complex; just entering a ticket will not solve this--we need to address it more holistically.

The team definitely has this on the radar; we want to work on it, no Idea Place idea is needed. But other issues take precedence right now, functionality that you and other members need. So we need to ask for your patience.

The question is, in the meantime, whether we should consider simply removing or hiding "Member Since" until we can figure out a better way to display a more meaningful date. I will discuss that with the team as a potential interim "fix."

Regards,
Audrey

Show 2 Share
10 |10000 characters needed characters left characters exceeded

> Due to the large number of small feedback items received between the Known Bugs List and the replies in the Beta Mission post, the team consolidated all of it into bigger items in those two places instead of migrating the old document.

The old document should have a redirect in place to the new document. ( http://scn.sap.com/docs/DOC-72804 )

0

Good point. D'oh! Will put in a request.

0
Veselina Peykova
Nov 12, 2016 at 06:07 AM
1

The closest to Known issues list, which I can find, is Community Known Issues & FAQs and to the feedback list (also missing) - Beta Feedback Recap. I found information on your feedback in none of them, though.

I saw, that this was also mentioned in another forum several times (I cannot see from there an evidence that SAP plans to work on that in short/midterm):

http://sap.userecho.com/topics/444-wrong-member-since-date/

http://sap.userecho.com/topics/301-profile-information-is-incorrect/

http://sap.userecho.com/topics/50-wrong-member-since-information/

Maybe a SAP team member could check in their internal bug tracker (I really hope they have one) and explain if an additional post in Idea Place is required.

P.S. This is another time, where @mention functionality would be handy.

Share
10 |10000 characters needed characters left characters exceeded
Marssel Vilaça
Nov 15, 2016 at 06:24 PM
1

My profile remains since 2010 although has postings in 2007.

All that I see is many explanations and lack of solutions and my bug topic was maket as not a bug.

https://sap.userecho.com/topics/50-wrong-member-since-information/

My question is if there is the posibility in change source code in inconsistent profiles in front of evidencies?

Share
10 |10000 characters needed characters left characters exceeded
Gabriella Gogl-Gyorgy
Nov 15, 2016 at 09:52 AM
0

Hey All,

The Profile is not "community only" anymore, therefore the member since date shown is not the same as it was in Jive, but when the user was actually created in SAP Cloud Identity, which is for some users later than the Community member since date and earlier for others depending on when they created their accounts in SCN/SDN.

I think (my personal opinion) it would be inconsistent to show community member since date for people who were part of Jive and the other date for the ones who weren't.

Of course I'm open for a better idea, if there is one.

Best,

Gabi

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Show the earliest of these two dates maybe? Or show both, if available?

I think, most people are not interested how exactly the user was created, but if I see a blog from 2006 and user created in 2015, I would find that confusing... not that actually I look at these dates, but it seems, some people do that.

2
Jim Spath
Nov 15, 2016 at 03:57 PM
0

No one has replied to the question about the missing known issues/bug page. I was told my report was documented, for future action. That document link now forwards to a page with a message saying that content was lost. Why?

Please do not repeat technical explanations about why my personal data shows up incorrectly. Get a ticket working to fix it. If I joined the SAP Community in 2007, my reputation page should show that, no matter how many or what kind of platform changes occurred underneath. Think about it like this--my retirement pay depends on my seniority. A bookkeeping error altering my "start date" costs me.

Share
10 |10000 characters needed characters left characters exceeded