Posted by ultimatedruid on February 24, 2009 at 12:01am
Jump to:
| Project: | Movie database |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | major |
| Assigned: | ultimatedruid |
| Status: | needs work |
Issue Summary
I've been wondering whether this module would be best served if we broadened its outlook? I think the new features in the 6.x branch mean that it is easier than ever to create any type of cross referencing data site with only a little bit of simple editing of hard script.
By this I mean the node types and fields can easily be changed from:
Movie ---- Person to:
Artist/Band ---- Record/Album (add CKK = Song)
Book ----- Author
Recipe ----- Chef
Basically - anything where a field is linked somehow?
What are your thoughts?
Comments
#1
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".
#2
This is a nice idea, and one that I've been thinking of, but not quite sure how best it would work.
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.
#3
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.
#4
please explain me well. im beginer so i really dont know. how it work. i put every info in moviedb and then it show it to me the cover picture so i put image url i didnt show but my page got wider but i cant see any pics. thanks
#5
#6
+1. I am all for a broader view that can trigger interest from a much larger audience towards what should be mostly the same basic features, just done in a flexible manner. Would help attract developers and also potential bounties.
To show any seriousness, however, I suggest opening a D7 branch for this.
BUT: if this should indeed be the path forward, then this module needs a new NAME, a new namespace, and thus the D7 branch should not go in here, but in the new namespace. "Movie Database" would be misleading within a broader scope.
Therefore, I suggest we discuss a new name and clearly defines the scope for this before doing anything else.
#7
Sorry for the delay. I agree with your comment. I was anticipating CCK having more cross relational aspects in D7 than it does. I've got to admit, I'm fairly pressed for time, and it's always nice to bounce ideas off others, do you think this is something you'd like to work with me on?
#8
#9
I am not a PHP programmer, but I have experience with database application development and web application development, and can read/understand PHP code somewhat. I would like to take part in discussing the functionality/specs and perspectives/possibilities, for example through IRC or the like.