Possible Uses of this module

There are many possible relations, so I think it would be best to refrain from it's movie concentration.
It should become something like a "media database" or so - and it is important, that you are able to create your own content type (and no predefined content types).

Each node represents something: a movie, a song, an album, a book etc. - and all these things might be connected somehow.

A little bit tricky might be the person content type: a director might be an actor as well, and so on.
Instead of creating an "actor content type" and a "director content type", a good solution might be to use a "person content type". And at nodes of this person content type, you get node referenced lists like "is actor in:" and "is director of:".

The main function I would need is the possibility of creating relations easily.
If I want to connect a movie to a director, I want to be able to create this relations either at the movie node or at the director node. And it should - of course - appear at both nodes. And it would be perfect if you could name this relations in both sides: "X is directed by Y" and "Y is director of X".

There are many possible relations, so I think it would be best to refrain from it's movie concentration.
It should become something like a "media database" or so - and it is important, that you are able to create your own content type (and no predefined content types).

This is a nice idea, and one that I've been thinking of, but not quite sure how best it would work.

A little bit tricky might be the person content type: a director might be an actor as well, and so on.
Instead of creating an "actor content type" and a "director content type", a good solution might be to use a "person content type". And at nodes of this person content type, you get node referenced lists like "is actor in:" and "is director of:"

The main function I would need is the possibility of creating relations easily.
If I want to connect a movie to a director, I want to be able to create this relations either at the movie node or at the director node. And it should - of course - appear at both nodes. And it would be perfect if you could name this relations in both sides: "X is directed by Y" and "Y is director of X".

This functionality is available in the 6.x.dev release, if I understand it correctly? There is a Movie node created and associated "job" nodes (which can simultaneously adapt to actor, director, etc). Each job can be defined in admin/settings/moviedb/jobs area.
There is also the added functionality in the 6.x branch that allows a film to be created through the actor field, so a full filmography can be created for any actor, director, producer, etc. All of this can be adapted for any other type of database.

Hello,

Congratulations by the great module you are creating.

I am planning a tv/movies site using Drupal and this module is what I needed...

I also see that it could be used to other contents. and really liked the above suggestion; but I'd like to remember you that it is a good option to design it to do one thing, and do it well.

I am NOT saying that you should not consider to future options, I am just remembering you that you can have the risk of trying to do a universal module and see that things will start to get over complicated.

Thanks again... se you later, since I plan to use your module and I will be reading all about it.