Hello, I would like to ask if these integrations are possible or will be possible. I list them here so it would be easier to track them at first and if it's needed new issues could be created with more information. Thanks.

-Relationships: User relationships or User relations API modules
-Birthdays: Birthdays module
-Location: Location or GEO modules
-Dates: Date & Calendar modules (I think is a better and more standard solution than Event Module)
-Integration with CCK and Views

Comments

Microbe’s picture

Microbe commented

Module integration is good except some become dependencies after they have been intergrated which we did not want.

I haven't seen the user relations modules and will have a look at them to see whether they are viable with the current 'which family individual is you' user field.

The location and calender module are definitely future integration but have been put of until after import and export GEDCOM scripts are created.

Both 5.x and 6.x modules have full views integration.

Not sure how you are thinking of integrating with CCK as you can add CCK fields to any content type.

Peter

daniorama’s picture

daniorama commented

The CCK integration meant if any of the data added by this module would act as a CCK field or not, so I could add its data to any content type.

About the relationships I think User relationships could be a good option, it gives gives a lot of features but it's also a bit database "heavy". With the User relations API I have no experience (that module is really new).

Location and calender would be awesome! (but if the module has already Views integration then to integrate with calendar would need just to create a new calendar View using it as argument, I will try it as soon as I finish my other pending issues)

PS: I have used PHPgedview for nearly a year, and I would like to have a Drupal solution.

pyutaros’s picture

pyutaros commented

I think I see where you're going with that DaniOrama. For instance, if I add a CCK field called MyField, I can then create a view that filters by my field with a selection of Text: MyField. We do not currently have those kinds of things defined for other modules like Views or CCK to use. For example again, the Audio module has 7 predefined fields that can be referenced by a View created by an enduser. I'm not sure what other specific uses there might be for this. I would create another issue for this if you are interested in seeing it. It may not make it in until the 7.x version.

User relationships is probably long down the line, but may come sooner if we end up focusing on the Privacy function. We likely would not use another module to do this.

Please let us know how the View creation went for a Calendar View. We may have to change our field structure for dates in order to integrate properly with Date Vies. Eventually I think I would integrate as a submodule with the date api. My only concern about the Date module is repeat events (anniversaries). I'm not certain, as I have not researched, if the date module is capable of this.

I'm going to update the project front page in the next few days to outline the module's current features and future goals.

Finally, phpGedView is the reason I took to this module and started dev back up. I too want a fully functional Drupal native solution for family tree viewing. Eventually, I'd like to see this program do everything phpGedView can do, and more. Thanks for your interest in Family Tree 2 DaniOrama.

Thanks,
Jonathan

daniorama’s picture

daniorama commented

Hello, regarding Calender in the last dev they have changed it a bit and it now works with any Date field. Well, in reality they have change the date module and date CCK fields are now listed together with the date fields form core. I'm not sure about the details but it seems that if the field could be used by views it can be use with calendar (things like Node creation date and Node update date work with it) The best thing is to ask Karen, she works very hard with Date and Calendar modules and offer an excellent support.

User relations does have a privacy system (well, it will have, I want to help Alex with that) The way it's going to be made is with the API that Mercmobily have started for CCK privacy and profile privacy for user friendlist on this isse: http://drupal.org/node/314170. Friendlist has already this made but I think that for this module User relationships has more sense.

Date can create repeating events. In fact it has a really powerful repeating system, it allows repeating each X days/moths/years, things like each 1st, 3rd and 15th of January, March and November and even exclusions. Right now there was an small bug with Views just showing the first one, but I'm sure this will be fixed soon (if not already)

The only thing I don't know about Family tree is how it works, I mean each person is a node, but when one person is also an user how is linked? I think all the privacy and the sort of relations could be easily included with User relationships, coding that inside Family tree is just duplicating work other had already made. (Family could use also Node hierarchy module but the node relations in Family are special enough to don't use any other module for that) I will try to contact Alex and Mercmobily (he's creating User relations API) I really think User Relationships and User Relations should try to merge and you should contact them to see which one could you use.

Creating the ancestry tree and all the other grpahics could be really easy with http://drupal.org/project/graphviz_filter. It needs some things but the power is incredible. There are also these for the chronology http://drupal.org/project/timeline and http://drupal.org/project/timemap I don't have any experience with them but they seem promising.

I know all my suggestions require a lot of reworking and the use of other modules, but hey! Drupal is a community thing :D I'm sure you will gain more benefits from using other modules that not doing so: you help the other mantainers and they help you, you avoid redoing things, at first needs rework but later you avoid creating many tables and code for your module, that will be a lot of time and effort that you can use on special features needed for your module or even doing other ones! :D

I think you find this information usable and reconsider creating a D6 with the help of these modules. Drupal 6 need modules like this to help the community upgrade. There is a loooooooong way until Drupal 7 becomes an standard, and I really think Drupal 6 will be the standard in 2009 and until the middle of 2010, think that many users say they stay in Drupal 5 because many modules are not ready for Drupal 6, but I'm sure that when ecommerce and ubercart have its final Drupal 6 release there will be a lot of newcomers (however the Ubercart 6 version is already pretty usable)

Thanks for reading and sorry for the long post, but I think you should know about those modules.

pyutaros’s picture

pyutaros commented

Thanks for all the information you provided. As was said before, we are likely going to try avoid too many dependencies as upgrades can be difficult and a change to one of the modules we depend on, could break our module. Dependencies will only be set to established modules such as Token, Views, possibly Date and others like those with an established API.

Family Privacy actually doesn't act on a per user basis. It's really for public access. The privacy option hides information for all family individuals who are not deceased, except to those who have special view permissions. A relationship based permission feature would be nice, but is not in the cards yet.

Family relations to user right now is a one way relationship. A user can select a node that represents them through a field in their profile. I don't believe there is any other functionality than that currently.

As far as Durpal 6 and Drupal 7 development, I'm going to stick to the plans to stick to Drupal's development schedule. I like this for two main reasons:
1) This provides stability on the standard versions you mention. By freezing new features on5.x now, and on 6.x when 7.x reaches the code freeze, we are providing a stable version for people who want to use this module on production systems.
2)For the more adventurous, we put new features on the development version to encourage quicker adoption and testing of the latest Drupal.

Thanks again for the info on the Date module. That is very useful and I will definitely be trying to integrate the Date API at some point.
Thanks again,
Jonathan

ajayg’s picture

ajayg commented

Here is a discussion just started in UR module to provide similar features that family tree already provides. I think here is an opportunity to collaborate (If it makes sense) rather than duplicate efforts.
#547228: Automatic Family Tree

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Status: Active » Closed (outdated)

I am closing this feature request, as it's for a not supported project version. If you want to see this feature implemented for a supported project version, please re-open this issue.