Peerly APIS functionality testing doubts

[thanekarpooja27]

1] If it is helpful can we add created_by, created_at, modified_by, and modified_at details while creating and updating organization and user details
2] for organization related API URLs we are using "organizations" and for core_value API's we are using "organisations". I thought it must be consistent for all modules
3 ]Organization operations can be handled by admin only? If it is then how we validate that?
4] What is the use of parent_core_value id, we are using core_value_id in recognition table, I am not able to understand for this 2 different attributes
5] For a few modules we are using int64 for time-related attributes and in some other module Time. time I thought it must be consistent
6] We are allowing duplicate core values as a text
7] Duplicate recognition can be allowed?
8] In recognition module 'getRecognitionHandler' API key for ID 'id' is used but in API URL recognition_id is defined, it returns error so need to use the same
9] Users can update or delete given recognitions ?
10] For show and update user I added my code with a new branch and some attribute changes also there in struct, but there is another one branch for the user module is exist. So is it need to modify and add into the existing one?