I'd rather see webtrees develop a database that supports the data that professional and commited genealogist need to record their information, be it an Evidence-Based or a Conclusion-Based schem, then output that data to whatever "newfangled data transfer schem" the world needs. XML can do this but I don't see the design of the NEW standards (their are several contenders) doing this yet. Support languages that use various character sets, allow for time and place centric variations in data. This standard must support constructs that go beyond "Western" usages for name, dates, places. It is not the issue of "version" differences as you noted but the misunderstanding of the version that they claim to support.īefore webtrees supports any other "new" GEDCOM standard a real standard must be created that all software companies must follow. Many programs don't perceve a need for understanding or supporting the standard as written, and forge their own "dialect" of the standard. However, the current issues with GEDCOM are primarily the fault of software companies not following the standard from the get go. Data typing and schema control are some of the first that come to mind. Moving to an XML based data transfer platform has some very important advantages. If you want to use GEDCOMX, the developers over there have a conversion tool you can look at. In contrast with Gedcomx that uses xml and json which makes it much easier data exchange between applications, not just genealogical but otherwise as may be cms (joomla, drupal, etc).Ĭonnexion ou Créer un compte pour participer à la conversation. You say it is a de-facto standard but from what little I've seen of the gedcom format, it has many compatibility issues between versions and compliance with the standard ( ).įor example, I made a demo webtrees with standard elements but when I import in Gramps the gedcom file generated with webtrees, Gramps throw a lot of errors. If somehow GedcomX gets very popular, that would only increase chances it will be incorporated into webtrees. The main reason to stick with traditional GEDCOM is it's the de-facto standard to transfer data inbetween genealogical editing & representation software. Likewise, a Drupal 7 version is on the roadmap but nothing pending at this time.Ĭonnexion ou Créer un compte pour participer à la conversation.Bertkoor écrit: I don't think there are currently any plans, bu who knows the future. I have not had a chance to look at webtrees 2.x to see how this support might be managed with the new platform. I have not had a chance to upgrade to 1.7.10 to test that but it should work. The system has been tested with webtrees 1.7.9. This means you can set up the Drupal site with just the administrator and the Webtree users will be added to the Drupal side as they log in using the password from the webtrees site. The system is designed to work when user accounts are initially on one site or the other. Limited mapping between roles is provided. Likewise, the logout links reverse the process. The Drupal login will also log into the webtrees site. My implementation has Drupal as the root and webtrees under the /webtrees directory. I recommend backing up your system before deploying (generally a good idea). The system works and is essentially a beta release at this point. Of course, webtrees provides the genealogy support that would not be easily added to Drupal. For example, Drupal's forum and gallery modules may prove useful to many users. This allows the Drupal site to provide features that are not available with webtrees that may be useful for family sites. This allows a Drupal 8 site and a webtrees site to coexist with users logging on to both at the same time. I have a create a that provides single sign on integration with the Drupal 8 content management system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |