In the Open Event Server, there was a long standing request of the users to enable the event organisers to create a FAQ section.
The API of the FAQ section was implemented subsequently. The FAQ API allowed the user to specify the following request schema
But, what if the user wanted to group certain questions under a specific category. There was no solution in the FAQ API for that. So a new API, FAQ-Types was created.
Why make a separate API for it?
Another question that arose while designing the FAQ-Types API was whether it was necessary to add a separate API for it or not. Consider that a type attribute was simply added to the FAQ API itself. It would mean the client would have to specify the type of the FAQ record every time a new record is being created for the same. This would mean trusting that the user will always enter the same spelling for questions falling under the same type. The user cannot be trusted on this front. Thus the separate API made sure that the types remain controlled and multiple entries for the same type are not there.
Helps in handling large number of records:
Another concern was what if there were a large number of FAQ records under the same FAQ-Type. Entering the type for each of those questions would be cumbersome for the user. The FAQ-Type would also overcome this problem
Following is the request schema for the FAQ-Types API
- FAQ to FAQ-type is a many to one relation.
- A single FAQ can only belong to one Type
- The FAQ-type relationship will be optional, if the user wants different sections, he/she can add it ,if not, it’s the user’s choice.