Would like additional information about CET
The following post has been copied here from the General "Ask a Question" Category. By posting in this group, other CET Users will be able to interact with this user.
Comments
-
@dhirschi08 @Gordon Collett @JanW2 @MandyShaw1 The discussions above ha been reposted in this group to enable them to be considered more effectively by the users and the engineering team that is currently working on the CET Product.
0 -
@MandyShaw1 CET has been put into production and available to all FamilySearch users. If you encounter a specific "bug", please begin a new discussion about that "bug" only. Each discussion is reviewed by the product team.
There will no longer be "Pedigree Resource Files" created from a gedcom upload, but, instead a CET will be created from that upload.
0 -
https://community.familysearch.org/discussion/comment/610155#Comment_610155
Except it isn't available to "all FamilySearch users" as I've pointed out several times. I should still start a new discussion?
This is what mine looks like. No CET in site. When I click Tree in that menu, it takes me to my tree view.
1 -
@mynameistk as @JanW2 says this is not a functionality bug as such, it is a user interface issue where access to CETs (or indeed PRF upload/import) has varied/still varies depending on geographical region, leading to a lack of consistency/clarity. I have however flagged this matter as a bug via @Sam Sulser's new relevant flagging option.
1 -
Thank you sincerely for your engagement and willingness to contribute. While your perspective is appreciated, it’s important to note that this particular project follows a specific communication pathway. The CET Feedback Community group has been designated as the primary channel for dialogue between product users and the engineering team. This ensures that feedback is accurately received, reviewed, and acted upon in alignment with the project’s goals.
Flagging discussions as “bugs” may unintentionally divert them from the intended review process, potentially delaying resolution and communication with the user. To maintain clarity and unity in our efforts, we kindly ask that all feedback regarding CETs be shared within the CET Community, as outlined at the top of the CET page.
We’re grateful for everyone’s desire to help, and we encourage collaboration that supports the broader mission of FamilySearch and the Community. Thank you for helping us keep communication constructive and aligned with the established process.
2 -
I think where the confusion is happening is the 'absolute' statements that things are available to 'all users', while ignoring the fact that all users are not included. It's similar to the lack of attention to non-US users of the system generally, such as the difference in how the system works for landing pages and the function of things as simple as the home page search system [it's not the same as in the user training examples; I've spent hours trying to replicate something that I see, but don't experience from my own account]. I get how it's difficult for FS to be across all the system quirks, but if there are going to be differences, then those who are writing support information need to be conscious of those differences. It's frustrating to see something is supposed to be available and yet it's not. This may need to be a higher level discussion within FS and an awareness issue to include in internal development, testing, training and help/support writing.
1 -
@JanW2 thank you for that additional insight. I have submitted a request for the engineering team to review your particular circumstances. When I get a response from them, I will forward that to you. In the meantime, if you would like to "suggest an idea" that additional correlation should take place, please make a submission to the "Suggest and Idea" category so it can be handled through the appropriate FS channels. Thank you
1 -
@mynameistk do you still want me to post a bug report separately in this Group? It seems to me that your engineering request re @JanW2's situation, together with the Idea you've proposed Jan suggests, cover pretty much the same ground as my 'UI' comment above.
0 -
Thank you for sharing your thoughts and questions in this CET Feedback Group. When you post a concern or suggestion here regarding a CET, it will be thoughtfully reviewed and discussed with the engineering team. There's no need to submit a separate bug report—this group is designed to be the central place for feedback.
This same approach applies to many new tools and features. When a dedicated feedback group is created for a specific product, a team is assigned to monitor and respond to the discussions there.
Please note: Flagging a comment as a “bug” only alerts the moderators (not the specific product team) and may actually slow down the process. Sharing your feedback as a discussion in the "feedbacl group" directly helps ensure it reaches the right team more efficiently.
As always, we’re grateful for your participation and insights—your voice helps shape the tools that serve our community. Keep sharing, and thank you for being part of this work!
1 -
@dhirschi08 This discussion got a little side railed. Did you get an answer to your original post?
0 -
Here's an answer:
The CET feature is still under development and part way through its rollout. It is available to a growing base of users, but not yet to all users. As the development of essential features completes and the rollout progresses it will become available to more and more users. If the feature is not yet available for you, you can still upload your GEDCOM file to create a published tree in the Pedigree Resource File collection of the Genealogies feature.
-Robert Kehrer, Sr. Product Manager2 -
@Robert Kehrer Thank you, that is very clear.
Unfortunately this help article does not reflect the rollout position as you have described it, and has I think caused confusion as a result. Could you get it edited please?
2 -
I will bring it up to our support & documentation team who generated it. Thanks for the heads up.
2
