Suggestion: split up the concept of a "Mentor" and a "Mentor visit"

[tomduggan85]

This is just a suggestion, and it might be too early in the project's life to worry about this (though, on the other hand, since it relates to how data is stored in the database, it might be too late to make this change later):

I noticed that a "Mentor" model currently has data for both a person (name, bio) and data for that person's visit (entry date, permit request status, flight info, etc.). It might make more sense to separate these into two models: A mentor, and a mentor-visit. Mentors could then have a reference to their mentor-visits, and the data model would then let you have one mentor with multiple visits (without having to overwrite their past visit information).

What do you think?
Hope all is well with all of you, and that you're safe.