On 24 October 2012 17:08, Kevin McCaughey <li...@ruby-forum.com> wrote: > Hi, > > I am new to rails and am making a meeting manager that manages meetings > for people at different locations. So it should be able to keep track of > meetings of people at different places and also know what a place is > being used for. > > Here is a link to the model (I have also attached as a file): > http://www.kevinmccaughey.org/relationships/relationships.html > > And here is an explanation for the diagram: > > NOTES: > > Person: Just a person in the organisation.
If the person is going to log on to the system then it would be more usual to call him/her a user. Then it will better fit with one of the authentication gems. > > Meeting: A collection of attendees meeting at place and particular time. > > Place: A physical building somewhere, with rooms (or a single room) that > can be used as a venue for a meeting. > > Attendee: A person attending a unique meeting. A person could be an > attendee at multiple meetings during the week. I would call this attendance, not attendee as this record is not the actual attendee but is a link to the person who is the attendee. Then you can say meeting has_many attendances and has_many people through attendances. > > Booking: A time and place for a meeting. There can be more than one > meeting within the same booking, or the booking can be in a different > room. This is because there may be lots of places within a building to > meet, and lots of meetings going on at the same time. Not quite sure I understand this. A booking contains fields with room and time, yet it has_many meetings. This only makes sense if there are several meetings in the same room at the same time. Then you also have a time in the meeting, which can presumably be different to the time in the booking. Clarification required I think. > > Check: Please ignore this for the time being. I am attaching it to > attendees for future use in a queue system (I do not want to poll the > attendees for events, I will create checks). Don't worry about building in stuff for future possible requirements. It is usually a waste of time as the requirements will change or you will think of a better way of doing it. Just design what you need at the moment, make sure you have good coverage with automated tests (that you write as or before you write the code) and then re-factor as necessary as requirements evolve. Not at all a bad start for beginner however. :) Colin > > Many thanks for any comments you have on this. It is my first time > creating the model and I have already removed many<->many by design in > case someone is wondering why there are no many<->many links. > > Kevin > > Attachments: > http://www.ruby-forum.com/attachment/7826/Base_Classes.jpg > > > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-talk@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
