BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
art297
Opal | Level 21

Regardless of whether I've misinterpreted Peter C's latest post, the Forum NEEDs an FAQ that we can all edit and keep up to date.

In my experience that is the best way to let users know such things about not posting long threads (and why), why they should identify when their questions have been answered and who provided the correct and/or helpful answers, and other protocol matters.

1 ACCEPTED SOLUTION

Accepted Solutions
reneeharper
SAS Employee

Hi Guys.

We have the ability to post the FAQ and I do have a partial one started.  If I start a document will a few of you collaborate with me to get the basics down?  Then we can open it up to a larger crowd.

PeterC -- we do have announcements and they run from time-to-time.  Only administrators and forum owners can create an announcement for now.  I would love to hear what kinds of things you guys expect to see in announcements.  Does it vary by space?  For example, I put an announcement about the free ODS book in the SAS/GRAPH and ODS Reporting community.  For the login issues, I only put the announcement on the main page.

Another question -- I don't usually send the announcements as email, but decided that the login problem was worth it.  What do you think about receiving announcements in email?

-Renee

View solution in original post

13 REPLIES 13
FriedEgg
SAS Employee

Typically in the software used by this site a nice way to implement user managed FAQs is by allowing the posting of documents.  Another option is to have a moderated FAQ section that is not open to public posting but allows a user list to post and moderate content as needed.

reneeharper
SAS Employee

Which of Peter's posts are you referring to?  Can you provide the link?

art297
Opal | Level 21

I probably misinterpreted what he was saying, but I was referring to http://communities.sas.com/message/107121#107121

However, the point is still valid.  Long posts that really take up a lot of unnecessary band width should really be discouraged.  But, we don't have a place on the forum that users can refer to in order to see what is expected, what is frowned upon, etc.  One isn't going to read the entire forum archives to discover posting guidelines and advice.

DLing
Obsidian | Level 7

Slightly different from the rules of how to post, I would really like to see people search for question and answers before they feel the need to post a question yet again.  Perhaps this should be the first rule in the FAQ (search before post).

WIthin the relatively short period of time I've been here, I have noticed many re-posts of essentially the same question by different people, thus a well managed FAQ section would go a long ways to helping new people find answers/content, and freeing up contributors to work on new questions instead of re-hashing the same answer to the same questions over and over and over...

art297
Opal | Level 21

While I only pointed out one example for the need, DLing has pointed out another.  We have a user modifiable one for SAS-L which covers both our points as well as a number of others: http://www.sascommunity.org/wiki/SAS-L

That could be an option.  We create and maintain a similar one for the Forums on sasCommunity.org. However, its existence and suggestion to read would have to be on the Forum's main page.

Brings up an interesting technicality.  Where SAS-L is "owned" by the users, the Forums are owned by SAS. However, both venues have extremely similar needs.

Peter_C
Rhodochrosite | Level 12

Art

since I was not making points outside the thread, your comment surprises me.

Please could you expand your interpretation of my (so brief) posts in that thread - in particular how FAQ might make a difference.

I would like to understand the inference I created.

best wishes

Peter

art297
Opal | Level 21

Peter, I had misinterpreted your comment about lines of code thinking, at the time, that you were implying that some of the posts included too many lines.  However, I didn't retract my post, as some posts do contain too many irrelevant lines of code or output that I am sure are not welcomed by those who receive the posts in aggregate forms.

My only point is that I think a FAQ summarizing such protocol issues, and useful tips, would be a welcome addition.  And, as I mentioned in a subsequent post (but don't recall anyone commenting on it), putting such a FAQ on sasCommunity.org but linking to it on the Forum's main page, seems (to me) like a good idea.

Peter_C
Rhodochrosite | Level 12

Art

thanks for clarification

I agree - since Communities.sas.com seem dis-inclined to host FAQ, our public space seems appropriate.

 

And since I have received posting from sasforum admins saying there is an announcement about the Logon troubles over the last 48 hours, it seems a pity communities.sas.com has no Announcements area

peter

reneeharper
SAS Employee

Hi Guys.

We have the ability to post the FAQ and I do have a partial one started.  If I start a document will a few of you collaborate with me to get the basics down?  Then we can open it up to a larger crowd.

PeterC -- we do have announcements and they run from time-to-time.  Only administrators and forum owners can create an announcement for now.  I would love to hear what kinds of things you guys expect to see in announcements.  Does it vary by space?  For example, I put an announcement about the free ODS book in the SAS/GRAPH and ODS Reporting community.  For the login issues, I only put the announcement on the main page.

Another question -- I don't usually send the announcements as email, but decided that the login problem was worth it.  What do you think about receiving announcements in email?

-Renee

Peter_C
Rhodochrosite | Level 12

that login failure was a "killer".

A banner indicating that the problem was acknowledged would reduce the undoubted flood of messages to ForumAdmin. (might be handy to have a box ready to acknowledge such a problem on the login page).

Forecasting when resolution was hoped for is worthy of posting "somewhere" on the Communities home page

Ending such loss of service should (, must imho) be notified by email (at least to recently-active-users - because some people will have stopped looking) 

I thought the Announcement link in the email would/should link to the explanation that belongs with the announcement of resumption of normal service.

The announcement in my email linked only to the Communities home page, where I could see no announcement!

Maybe I was too late to see it, but I guess it is still somewhere and that page could have been linked in the resumption email.

A document about the issue could have been created - perhaps in an "forum admin" type area.

I would place any Announcement service solely in the hands of Forum Administration

just my $0.02

Glad to hear a FAQ will be established.

I'm happy to add my "penny-worth"

it should be reasonably simple to define "recently-active-users" as having posted within the last NN days.

peterC

art297
Opal | Level 21

Renee,

I'd be glad to help.

Art

DLing
Obsidian | Level 7

My time is rather limited, but I am willing to help out on occasion.

art297
Opal | Level 21

Renee, In answer to your question about announcemnts I, for one, very much appreciated getting the notifications via email.

sas-innovate-2024.png

Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.

Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.

 

Register now!

How to Concatenate Values

Learn how use the CAT functions in SAS to join values from multiple variables into a single value.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 13 replies
  • 1267 views
  • 2 likes
  • 5 in conversation