I'm looking for some advice on REST best practices for providing two different views that update the same resource. I'm working on a hotel registration system and there are two different views that edit the guest model.
The first one is used to take/update reservations and enter all the basic guest information. The second one is used to check-in guest by providing a quick update from a list of search results. The clerk can enter room number, etc in the table and update the guest right there; it then takes the guest back to the search page.
The problem is that both of these should do a PUT on the guest to update the information. My question is where should those two actions reside, and how should I handle two different redirections from the update action?
I've thought about creating another model called registration that the second case updates, but that seems a little overkill. What about a second controller and routes with name_prefix?
Are there best practices for this situation? Any thoughts or recommendations would be appreciated.