0

I have a content type "events" and all the node created under this content type will have further node.

enter image description here

The red boxes in the above pictures are node links which are associated to the "event node".

Every node created under "Event Content Type" will have relative information nodes as shown in boxes below.

How i should be doing this association? Should i create content types for all red boxes and then make entity/node references ?

any clue? thanks

  • what is the purpose of the association? will you be referencing fields from one node to another? is it simply a hierarchical setup you are trying to achieve? more information on the intention will help with a suitable answer. – Geoff Sep 7 '14 at 15:56
  • Every node created under "Event Content Type" will have relevant content nodes with more information but all will be related to a specific node-type-event . does it makes sense now ? – brainHax Sep 7 '14 at 16:19
  • possible duplicate of Multiple nodes within a node – Bulat - Reinstate Monica Sep 7 '14 at 16:25
  • 1
    It seems that you already know the solution, so not clear what is being asked. – Bulat - Reinstate Monica Sep 7 '14 at 16:26
  • @Bulat I think it is clear what he is asking for? Which approach to use? Create separate content types and use references or embed everything into one content type? I don't think this is a duplicate of the question you flagged. – Raf Sep 7 '14 at 16:55
1

I recommend that you model this from an object oriented perspective. I would create the following content types:

  1. Event content type (composed of event, overview, agenda, live broadcast maybe)
  2. Speakers
  3. Resources
  4. Venue
  5. Sponsorship
  6. Registration

The reason for embedding overview, agenda and live broadcast to the event is because they are closely related to to specific event and creating separate content type for them would be expensive (because there is a very less probability that two event have the same agenda or overview).

Whereas other content types such as Speakers, Resources, Venue, Sponsorship, Registration can be regarded as separate content types, because:

  1. To allow referencing the same content type by multiple event nodes i.e. for example, you will have a speaker who would speak in several events, or a resource that would be useful in several events hence, you will be avoid loads of duplication/inconsistency etc.

  2. The other reason to create separate content type is to achieve low coupling and high cohesion. Speakers are different than events, the best way would be to reference than to embed a a list of speaker into event content type. Fields of a Speaker content type, does not directly relate to an Event (i.e. Database normalization perspective)

This would give you a clean set of content types that are linked with each other using references and can be queries very easily using views, contextual filters and relationship.

Good luck.

  • Here is a very good tutorial on how to setup an event registration system (I recommend Entity Reference over Node Reference) - might give you more ideas torontowebsitedeveloper.com/drupal-video-tutorials/… – Raf Sep 7 '14 at 17:22
  • thank you so much @Raf , i believe this will be the perfect scenario for this kind of case. :) – brainHax Sep 8 '14 at 7:35
0

You could create separate content types and use a custom module to handle the node/entity reference links, but for a smoother more self-contained approach, I might suggest:

  • use a single content type that contains all of the information for all of the sub-nodes
  • use a bit of jquery to handle showing/hiding certain elements on the screen

One drawback to this approach is the amount of work required when add/removing fields since the javascript would also need to be changed, but it would allow for a single page load instead of multiple page loads for a single "event", and keeps all the data in one place.

  • as I think about it more, using field collection would reduce or eliminate the issue of making changes, since then it could work of the collection and not the individual fields – Geoff Sep 7 '14 at 16:36
  • Yes single content type is a simpler solution but i am still not sure how complicated the linked nodes can be. So i better go with separate content types as mentioned in below answer. – brainHax Sep 8 '14 at 7:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.