Populating the date in sources on CET
I am posting this for another person who is still having problems being a part of this group:
I am having a problem populating some source information when using a GEDCOM file into CET. The source date is uploaded into CET, but it is not being used to populate the date field for the individual sources. This date is important because it is used to sort sources in chronological order.
I have uploaded a GEDCOM file from both Roots Magic and Legacy Family Tree with the same results.
A source is created (including description, date, URL and other useful information) and attached to an individual in the software family tree. When all the sources are attached, a GEDCOM is created. The GEDCOM is able to capture these sources quite successfully and the upload takes place without a hitch. The problem comes how the data populates the fields in CET. Some of the source information, including the date, is used to create a Fact section on the Details Page. Some source information also creates a source on the "Sources" tab. Sources in Family Tree allow for a date to be entered along with some information about the record itself and an URL. Currently, that date has to be done manually after the fact.
It would be really helpful to populate the date field of the source with the same date used to create "Fact" since they really are the same event.
(Name removed)
Comments
-
@Cherie Gardner Rawlings Mod note: Your post was edited to maintain the privacy of a living person. Please see the Community Code of Conduct for more details.
0 -
I am posting this for another person who is still having problems being a part of this group:
I am having a problem populating some source information when using a GEDCOM file into CET. The source date is uploaded into CET, but it is not being used to populate the date field for the individual sources. This date is important because it is used to sort sources in chronological order.
I have uploaded a GEDCOM file from both Roots Magic and Legacy Family Tree with the same results.
A source is created (including description, date, URL and other useful information) and attached to an individual in the software family tree. When all the sources are attached, a GEDCOM is created. The GEDCOM is able to capture these sources quite successfully and the upload takes place without a hitch. The problem comes how the data populates the fields in CET. Some of the source information, including the date, is used to create a Fact section on the Details Page. Some source information also creates a source on the "Sources" tab. Sources in Family Tree allow for a date to be entered along with some information about the record itself and an URL. Currently, that date has to be done manually after the fact.
It would be really helpful to populate the date field of the source with the same date used to create "Fact" since they really are the same event.0 -
Thank you very much for your willingness to help test this new product.
I will bring this issue to the attention of the engineers and developers.
Currently, early access is very limited and persons are added. Keep in mind that we are gradually inviting testers based on the needs of the software development process. This phased approach ensures our engineers can refine the tool and handle the growing number of users effectively.
Please be patient as we continue to expand access. Thank you again for reaching out.
0 -
Cherie, The group is now public and this person you are helping should have no problems joining now.
Could you post a PID to one of the tree persons where you see this import problem manifest. It would be helpful to have clarity of which source on the person you are looking at, what the date on the vital event is and what it should be.-Robert
0 -
He will be in the NOB tomorrow, I will ask him to do so. But, it's the year on the top of each source that doesn't come over.
0 -
@Cherie Gardner Rawlings to help us better understand your question, are you referring to this date found when attached sources are listed? It is the same on FT, FGT, and CET
0 -
Yes, the "Add Date" is what is being referred to in the initial request. It is not being populated by the GEDCOM file.
0 -
@NCVAresearch thank you for sending additional information. This is being forwarded to our engineers for a response.
0 -
Can confirm. I am creating a gedcom using Family Historian 7.0.24.1 and the dates for my sources are not populating. Date references in other locations work as intended.
Not sure if this is a global issue or just for certain people. I'll leave this profile as is if someone needs to reference it.
0 -
Thank you all for testing and posting this issue. We are tracking this against issue RSTI-1873. Will keep you updated as we investigate.
0 -
I do not know where to check the current status of RST1-1873. Could you tell me where where to look to see what progress is being made on this problem? Thanks
0 -
@NCVAresearch I am sorry, but only the engineering team has access to the tickets that are assigned and currently being worked. But, I can tell you it is process and currently being looked at.
0 -
I hope this request has not fallen through the cracks. I submitted this request nine months ago and have heard nothing back about it.
As far as I can tell, the current method of extracting source information from the event without the date impacts multiple genealogy program uploads and possibly all GEDCOMs that are imported. The date exists in the event record. The current CET program seems to extract out only the source information from the event record.
In my case, I am uploading an ancestral tree starting with my grandfather. I am using CET so that a full and complete record of his ancestry is available to all who are interested. I have been working on it for almost 30 years. There are thousands of sources attached. It would be a Herculean task to go back and date each source.
Please take a look at bringing over the date for the source.
0 -
@NCVAresearch This is still on the prioritized list that the engineering team is working through. That list is by priority, not necessarily chronologically. Please bear in mind that this is an early-access product. This early testing and feedback are vital to improving and getting CET into full production. Each issue is assigned a priority by the team. Stay with us as we keep working on the product.
0
