Mark_Hopkins
Boss
Joined 17 years ago
User Profile
User Widgets
Contributions
Re: 14.9 Release Notes
tdeboard, It does in a way. See my edit above - I have reverted to use of a pre-existing role, however that role provides unwanted permissions and I don't see how I can start over at this point as the admin metrics are no longer a line item. As I think about this, I do appreciate the delimma for Lithium as changes from new features necessitate recombinations of things to keep a reasonable number of controls and a desire to keep them grouped and well organized. I do think organizational / grouping progress has been made over time. How does lithium deal with legacy roles that were created when different combinations of permissions were available. That's a pickle. One I appreciate is challenging to solve.192Views0likes0CommentsRe: 14.9 Release Notes
John, We are now on 14.9. I like that Lithium has picked up the pace on releases and implementing changes / features quickly. Kudos Lithium. It may just be me, but a byproduct seems to be that the admin controls for users keeps changing as well and it becomes a bit of a head scratching moment to devine what switch now controls which feature. Case in point: There used to be permissions to get at admin metrics, and another to allow user reports, and another for CIC (sunset) and LSI. Today, I'm trying to give a non-admin permission to get at admin metrics and can no longer do this - at least not in a way I can figure out in 15 mins of trial and error. I can give LSI permissions easily - check. I see a setting to give user reports permission in admin, but even when checked that is not available to the person and neither are the admin metrics. I know there may be a strategic goal to move metrics all into LSI, and maybe that will be good, but there was a wealth of info available in advanced metrics and I'd really like to surface that for some people without making them admins. Thoughts? EDIT - Interestingly, I solved the problem by using a role that had been created some versions back and included the permissions for admin metrics. Giving this role enables what I want, but I doubt I could create the role anew based on the current set of selectable permissions. However, an unwanted (in this case) byproduct of that pre-existing role is that it may give some access to community structure which I don't want this user to have. I have edited the individual user settings and denied anything I can conceive of which would trigger access to community structure. Does the role override the individual settings for the user? If so, I would need to edit the role and remove them, but that would break things for others. Mark202Views1like0CommentsRe: Creating custom User Registration Form using REST API
Jake, Appreciate the wisdom of the Oracle as always! Could you also check with the elder Lithium gods to see if any cleverness that could otherwise get us around this exists on some arcane scroll tucked away on a shelf, or in a bottom drawer of someone's desk? SSO may be in the cards for us, but I want to leave no stone unturned. :manwink: Thanks Mark341Views0likes0CommentsRe: Activecast not showing
Kokasexton, I think as along as active case is enabled, it should work - you generate and place the code. The only snag I can remember that we hit at one point was needed to have the permission " Allow user to make REST API calls with read access" set to grant. You might check that one... Mark222Views2likes1CommentRe: Obtaining message attributes to use as filters for search results
Darren, Very cool! I've always wanted to see results pulled and displayed with priority for KB articles, then solved discussions... By the category and board ID information, we should be able to determine if it is a KB or not - that's great. I think I see that this can also be used to filter results by language if you have multiple languages within a single instance of community. Thanks for sharing what you are doing - awesome! JakeR, Maybe I've missed it, but is there a flag set that says a discussion thread has been solved - is an accepted solution? Perhaps no, that you stipulated what was available via rest api for search. I just wondered since active cast seems to have some solution oriented selections, and that is based on the rest api, right? Mark293Views0likes1CommentRe: Social Network Analysis 101
Dr. Wu, There are so many aspects of this one could discuss. One that I thought you might be getting at, when you modeled the facebook vs LinkedIn is the venue. In my world, I see some of my community members not only have relationships within our community, but they also interact on other communities, read each other's blogs, follow and RT on twitter, and share content on facebook and comment or like what each other say there. They do this in different combinations. No doubt there are several more networks that they are on in various combinations which I'm not following. I can only keep up with a tiny fraction of the community and greater social eco-system. What does it look like? Because I'm a simple kind of guy, I'm thinking about the social platform as a layer and seeing which members exist in each layer and how they interact (creating an edge?) and how those might stack up to form a 3 dimensional model. Quickly though, this gets beyond human ability to neatly diagram it out, or keep up with it in our head. One could imagine how the Lithium platform might evolve to support this kind of model, to be able to visualize interactions within the community, into facebook, twitter, linkedIn - adding layers to the model..... Mark43KViews0likes0CommentsRe: The 90-9-1 Rule in Reality
Dr. Wu, Yes, I meant 65% - thanks for catching that. Your points are well made - when I considered the 65% , it was the percentage of registered users who had posted at least once. I agree that if one were to consider all the unregistered user sessions in the whole of the community (which would greatly increase the denominator) then the percentage of contributors and hyper contributors would shrink significantly. I elected not to look at it that way for two reasons: 1) I wanted to restrict my consideration to those had taken the time to register an ID and log in - taking the first step to joining the community and in some way demonstrating their intent formally to do so. 2) As registered users (myself included) may visit and browse the community at times without logging in, I considered that I might be double counting these actions, and incorrectly attributing them to the pool of lurkers since there is no way to know without the person having logged in, or some complex IP address lookup, whether or not they were already a member in the community, and whether or not they had posted at least once. I did my "back of the envelope" analysis based on a long term cumulative view of the community - all users over time. I played a bit with the date function on the social graph tool and went back to the beginning of the community and browsed through at various points in time over several years. I could see some of the super contributors on the graph, and a few have fallen off if they left the community, having not contributed enough to make it into the all time top 20, as seen the cumulative view. So, through the aperture of a point in time, the percentage contributions could change quite a bit depending on the overall size of the community and the number and characteristics of those hyper-contributors. Both views - cumulative vs point in time have their own merits. I'm going with cumulative overall when discussing characteristics of our community. However the point in time view can help spot emerging talent / rising stars, so keeping a 30-60-90 day view is handy as well.. Mark72KViews0likes0Comments