CETs Feedback
Here are some things I noticed while testing the three CETs.
1. Three GEDcoms were loaded. It took some time for all the CETS to appear.
2. Two errors were listed on FamilySearch after the GEDcom was loaded. While good, it did not give me enough information to tell me why they are errors or how to correct them.
3. A person ID number was assigned but this number is also being used by another person in the Family Tree. The ID number from my CET is 9MM4-13X for William Frederich Longhenry. The other person with the same ID number on the Family Tree is Maria Amable La Rue. On another person (P9QM-CSL) the ID worked, as it should and matched the one in my CETS upload
4. My CETs contained one person with numerous newspaper articles. These came across well. Some of the data is truncated, which happened during the GEDcom export because of my character limit.
5. The hints that were offered worked just like any other hint would. They seemed to be appropriate to my people.
6. After reviewing a hint, it was nice to see that the user could either return to the record or the CET. This is a nice navigation feature.
7. The timeline function worked out for me. It took my notes and displayed them accurately.
8. The user can go into the citation and correct typos, information, etc. to make edits after the import, which is quite nice.
9. The screen notations of CETs were quite nice because I had several tabs open. So, it offered clarification, which is appreciated.
10. Items I have entered in my software program as sources for a person are for newspapers, censuses, etc. The import misses the dates that are included from my program GEDcom export.
11. In my software when entering an item with a source, I add the date and location, followed by the source details. When exporting to the GEDcom the locations are removed because of the way FamilySearch treats a source. The dates while present in the GEDcom, do not show up on the CET screen. So, in the CET I have a series of sources without dates and location, which are important to me and because I have used the same entry type (newspapers or census) for multiple entries. This requires the user to open each entry to assemble the information. I have no way to know if these sources are in event date order. I understand that this is how I choose to use sources and that others may do it differently.
12. When an event in my file had multiple sources, the CETs tied them together nicely.
13. Overall, I liked the ease of uploading a GEDcom. But, because the data I feel is important, does not display fully, it would be difficult for me to use the CET upload. Because my sources are entered differently than you treat them in FamilySearch, the idea of editing each source for those people is overwhelming and likely would never happen.
14. That being said, this improvement is outstanding and I believe users will appreciate the upgrade.
Comments
-
Eileen,
Thank you for documenting your observations so thoroughly. A few comments.
(Item2): Imported Differences: We are working on trying to provide more data about what wasn't imported completely.
(Item3): Same Person ID Used: That would be a fairly serious error and there should be no way for any two people in the system to ever get the same PID. I was unable to validate it. When I search the system for PID=9MM4-13X I only get back Maria Amable La Rue in the Family Tree. When I search for "William Frederich Longhenry" in all trees I see one in a tree called "Lead Mining Longhenry" (P93B-545) & I see a second one in a tree called "Lead Mining" (P931-MML). Can you provide a screen shot of your William Fredrich Longhenry with the PID 9MM4-13X.
(Item 10 & 11): Missing Dates: Our teams are going to need file a bug for this one so the engineers can investigate it. It shouldn't be missing dates if they are properly annotated as dates in the Gedcom file.
(Item 13): Gedcom Upload: I'm glad the Gedcom upload generally worked for you, with the exception of handling dates the way you wish. Shortly most leading genealogy software will be able to create a CET, copy all data into it and keep it in sync with the remote tree. When these integrated products release to users, it will be interesting to see if they can move the dates in the way you desire directly, rather than relying on a Gedcom file export.0 -
@Eileen Lund-Johnson Thank you very much for testing early access CET and offering such detailed feedback. As @Robert Kehrer asked, please attach a screenshot showing the entire screen for each person with a duplicate number. It is important that the screenshot show the tree that you are using, the name of the person and the PID for that person. I will ensure that each of these issues is brought to the attention of the engineering team and will follow up on the progress. Thank you, again for helping make the early access CET a wonderful product.
0 -
Unfortunately, I could not reproduce the error. My only thought is that I was in the CET's test system and the production systems at the same time. The technical staff would need to determine if that is a realistic conclusion.
0 -
@Eileen Lund-Johnson thank you for continuing to test early access CET. If you encounter another issue or bug, please begin another discussion and include screenshots whenever possible. Thank you, again, for your feedback.
0 -
Thank you for bringing this to our attention. We’re committed to resolving as many issues as possible, and we’re closing this discussion for now. If you or others encounter this issue again, please start a new discussion and include relevant information such as your operating system, browser, URLs, and screenshots if available.
We appreciate your support and engagement. Please don’t hesitate to reach out with any future questions or concerns.
Thank you for using CET.
0
