Dear Rodovidians, please, help us cover the costs of Rodovid.org web hosting until the end of 2025.
User talk:Genasap
From Rodovid EN
Welcome
Thank you for your first contributions, and for using our list of places and our templates!
If you want, you also have the possibility to add direct links to Wikipedia pages, like it has been done for John Seymour (in the "Notes" tab).
As for Awan and her couple with Cain, extra descendants like Beth have been added in the Russian interface by user Gorvzavodru just by following contents from geni.com. I have been able to identify the Pseudo-Philo as the source for some records, but not for the line of Cain. If you have informations about that branch, we could decide to keep these records or to delete them.
(I added some details about Rodovid at the end of the first steps page.) --Dn Gov (d) (France) 07:00, 8 April 2025 (EEST)
- Thank you very much for your suggestions and for sharing the information about possibility to add direct links to Wikipedia pages.
- Regarding Awan, the sources I have consulted, such as the Book of Jubilees, Cave of Treasures, Golden Legend, and others where she is mentioned under various names including Awan, Kalmana, or Aclima, consistently describe her as both Cain's sister and wife. To explore the descendants of Cain, I would need to undertake a more detailed research. As far as I know, Beth was a daughter according to some traditions, which also claim that, in addition to Enoch and Beth, there were other children of Cain and Awan, that are Bart, Una and a daughter with unknown name. In any case, my primary intention when adding Awan (Person:79462) to the English version of Rodovid was to highlight the need to merge Person:79462 with Person:32398, as my account does not allow me to perform merges directly.
- Although I have requested this merge on English-language Rodovid wiki, it would also be necessary to apply it across all other language versions. For now, I believe that proceeding with this merge is the most appropriate course of action. However, if you feel that a different approach would be more suitable, please feel free to take whichever steps you consider best.--Genasap 20:41, 16 April 2025 (EEST)
- I disconnected the duplicate from the tree.
- Rodovid uses an old version of Wikimedia, so all accounts are equal (except for administrators) and it is not possible to merge the history of duplicate records. Contents are transfered "manually" from one page to the other, with the possibility to use the comment field to mention the original authors, dates and pages. The duplicate (the most recent page) is usually deleted (authors almost never complain). Dn Gov (d) 09:00, 17 April 2025 (EEST)
- Thank you very much for your attention to this matter. I believe your approach was appropriate, as it resolved the issue of Awan being listed twice in the family tree. Thank you for the explanation regarding the manual transfer of content from one record to another. Now, the Person:79462 record highlights the need to merge duplicates of Awan across Rodovid's different language versions. That was my original intention; however, maybe it would be more convenient to remove the record and manage duplicates within each language version individually.--Genasap 21:40, 17 April 2025 (EEST)
With the special system of Rodovid working in several languages, merging has one part that can be done globally (gender, family links, dates, main picture) and another part that must be done in each language version (names, places, notes). It does not matter whether it is done before the duplicate is separated from the tree or after.
That is what i did, and in this case it was easy because the data to transfer was limited : a link to Wikipedia in Spanish, and some sources in Russian.
One detail about Rodovid :
* When you start translating a record into English, the interface and the dates will be in that language, but the original contents (names, places, notes) will be those of the linguistic version that was edited the most recently (sometimes the Russian or the Hebrew one). Dn Gov (d) 02:00, 18 April 2025 (EEST)