|
|
| (6 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
|
| |
|
| The GetSatisfaction FamilySearch Users' Forum and discussion group is also used as "Feedback" for the FamilySearch website, | | The GetSatisfaction FamilySearch Users' Forum was changed on Sept. 28, 2020 to FamilySearch Community Ideas. After numerous years of using the GetSatisfaction platform, it was discontinued by the company and no longer available for use by FamilySearch. The replacement for GetSatisfaction is [https://community.familysearch.org/s/idea/Idea/Default FamilySearch Community Ideas] and allows users to give suggestions and feedback on their experience on the [https://www.familysearch.org/ FamilySearch website]. |
| | |
| The forum currently has over 18,000 users and many FamilySearch Employees actively participating. Questions are generally responded to within hours of posting. The forum is now being used as the official FS Tree through the "Feedback" link at the bottom of most pages.
| |
| | |
| [https://www.familysearch.org/ask/salesforce/viewArticle?urlname=Patron-feedback-or-requests-for-product-enhancements&lang=en This GetHelp article provides steps] to share a suggestion or compliment, or to ask a question for which a patron cannot find an answer by clicking Feedback.
| |
| | |
| The Forum can also be [https://getsatisfaction.com/familysearch/topics accessed directly]
| |
| == Etiquette ==
| |
| [[File:FAMILYTREE ETIQUETTE.jpg|thumb]]
| |
| As FamilySearch promotes collaboration in its use, the forum encourages the promotion and use of the FS [Wiki Etiquette]https://www.familysearch.org/wiki/en/FamilySearch_Wiki:Etiquette_Guidelines Guidelines: A new Draft Etiquette suggestion had been proposed:
| |
| == Using the Forum ==
| |
| Reporting Problems in [GetSat forum]https://getsatisfaction.com/familysearch/topics/how-to-report-a-problem-with-familysearch-in-this-forum
| |
| | |
| Editing your [GetSatisfaction Profile]
| |
| https://getsatisfaction.com/familysearch/topics/please-explain-and-fix-forwarded-forum-feedback-from-familysearch
| |
| | |
| ===Posting to the Forum===
| |
| ====New Discussions====
| |
| To get the best response, limit a new discussion to just one topic, concern, or issue. Where possible provide screen shots, URLs (internet addresses), and Person ID numbers (called PIDs) if dealing with Family Tree issue.
| |
| | |
| Keep in mind that while FamilySearch personnel read each discussion, their time is very limited. It takes a lot of time to respond to a discussion, especially if something needs to be looked at or if an article needs to be located and FamilySearch personnel have a lot of duties, including supporting the entire site, helping to design new features, and so on. Many will respond as they feel is absolutely necessary,
| |
| | |
| Most of the responses will come from FamilySearch patrons with varying levels of experience. New changes may render some of their advice obsolete and in the vast majority of cases, they may present their view on a topic, making it look like they are "shooting" down what otherwise would be a good idea. They are often doing no more than trying to help.
| |
| | |
| Patron responses are often the only ones that a discussion will receive.
| |
| | |
| ====Emphasis====
| |
| Good "netiquette" frowns on the use of all capitals, as it implies that a person is shouting, but there are ways to emphasize text by using a limited number of html style codes. Placed between angle brackets "<" and ">" letters can be used to underline (u) the text, make it bold (b), or make it italic (i). The beginning point places just the letter between the brackets, followed by the text. The ending point uses the slash "/" before the letter.
| |
| | |
| Examples:
| |
| | |
| Typing: <b>This is bold text.</b> gives: '''This is bold text.'''
| |
| | |
| Typing: <i>This is italic text.</i> gives: ''This is italic text.''
| |
| | |
| Typing: <u>This is underlined text.</u> gives: <u>This is underlined text.</u>
| |
| | |
| ==== Quoting Other Users ====
| |
| When quoting other entries in long topics, it can be useful to quote a section of an earlier comment in the post. To clearly indicate the quoted text, the HTML command BLOCKQUOTE can be used.
| |
| | |
| Example:
| |
| | |
| Typing:
| |
| | |
| <blockquote>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.</blockquote>
| |
| | |
| Gives:<blockquote><span style="background-color: #E5E4E4">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.</span></blockquote>
| |
| | |
| == Some Recent Questions Answered & Discussions ==
| |
| A few questions answered in 'recent' posts (March 2019):
| |
| * Using the the [https://getsatisfaction.com/familysearch/topics/incorrect-family-search-automatic-linking person's PID "Latest Changes" list] to reverse, or correct changes.
| |
| * Downloading & using [spreadsheets in FamilySearch]https://getsatisfaction.com/familysearch/topics/spreadsheet-questions
| |
| * Translating standardized [https://getsatisfaction.com/familysearch/topics/translating-standardized-place-names Place Names in FSTree]
| |
| * A [https://getsatisfaction.com/familysearch/topics/merging-impediment-for-deleting-relationships recent "well liked" proposal]: "Would it be possible to have warnings pop up (like are used when editing relationships) that would say something like: "If you continue with this merge the following relationship(s) will be deleted."
| |
| * Web [https://getsatisfaction.com/familysearch/topics/indexing-update-feb-2018 Indexing Update 2018]
| |
| * An extended discussion: MyHeritage [https://getsatisfaction.com/familysearch/topics/myheritage-destructive-sync-feature Destructive Sync Feature]· 36 replies
| |
| * Adding a Stepchild with Source Linker (or generally using the [Source Linker “Change” function]https://getsatisfaction.com/familysearch/topics/adding-a-related-step-child-by-id-when-attaching-records-listing-a-step-parent )
| |
| * How to get [https://getsatisfaction.com/familysearch/topics/the-tree-information-is-not-correct-how-can-i-edit help when starting in FamilySearch Tree]
| |
| * '''Using [https://getsatisfaction.com/familysearch/topics/ordinances-ready-ss-doesnt-follow-my-temples-church-rule-for-sealing-to-spouse Ordinances Ready]'''
| |
| ** FamilySearch Guru, Gordon Collett, has provided the flow chart to fully complete the [https://www.familysearch.org/wiki/en/Analyzing_Ordinances_Ready Ordinances Ready analysis].
| |
|
| |
|
| [[Category:FamilySearch]] | | [[Category:FamilySearch]] |