I think I would also create a document type for Author and Genre.
On the movie document type I would then create content pickers as the property on the author and genre fields.
You can then have a branch of authors and genres, which you can reference using the content picker, which should give you some very flexible opportunities in order to present your content.
I am thinking of the following recipe to solve the problem:
3 outer document types are needed: Movies, Authors, Genres. Doing so, it is straightforward to list all the child items they contain.
3 inner document types are needed: Movie, Author, Genre for the sake of encapsulation.
The outer document types have a content picker OR a ultimate content picker (which provides more flexibility when traversing a hierarchy of document types).
The content picker/ultimate picker refers to a inner document type, such as Movie, Genre, Author.
How can I meet the last 2 requirements? Actually I think that Relation (or XPath) may come in handy.
Yes the ultimate picker has some nice benefits. If you are using uComponents there's an even better node picker datatype in that package.
What do you think of by the relation? As I read your first post you should be able to extract the needed information by using the GetXmlNodeById extension so you can fetch the data from the selected nodes?
Case study: need advices
I have been pondering on a solution to the following problem:
Let's suppose I have 3 movies:
I'd want to have a page:
Moreover, I'd want to have:
I can create a Movies document type and a SingleMovie document type along with 3 fields: MovieName, Author, Genre.
Doing so listing all the Movies is straightforward. But what about the other requirements?
Thanks for your help.
R.
Hi Phenryll
I think I would also create a document type for Author and Genre.
On the movie document type I would then create content pickers as the property on the author and genre fields.
You can then have a branch of authors and genres, which you can reference using the content picker, which should give you some very flexible opportunities in order to present your content.
Does this make sense?
/Jan
Hi Jan,
I think you are right :D
I am thinking of the following recipe to solve the problem:
3 outer document types are needed: Movies, Authors, Genres. Doing so, it is straightforward to list all the child items they contain.
3 inner document types are needed: Movie, Author, Genre for the sake of encapsulation.
The outer document types have a content picker OR a ultimate content picker (which provides more flexibility when traversing a hierarchy of document types).
The content picker/ultimate picker refers to a inner document type, such as Movie, Genre, Author.
How can I meet the last 2 requirements? Actually I think that Relation (or XPath) may come in handy.
What do you think about it?
Yes the ultimate picker has some nice benefits. If you are using uComponents there's an even better node picker datatype in that package.
What do you think of by the relation? As I read your first post you should be able to extract the needed information by using the GetXmlNodeById extension so you can fetch the data from the selected nodes?
/Jan
You are right.
Thanks a lot for your help :p
is working on a reply...