Report required and optional features visible to users using comment boxes

[tramyn]

There are interests using comment boxes as an easy way for reporting to a user optional and required fields after the creation of a table template. The idea for using a comment box is to incorporate highlighting and linking comments together into a document for each optional field not detected within a desired table. Below is a list of obstacles that will need to be addressed in order to implement this feature:

• UI doesn’t allow highlighting and linking comments together into a document. Highlighting and linking comments act as separate features in a Google Doc. Comments manually inserted in a document from Google Doc's interface has the ability to jump to the range of text that the comment is referring to but it has been noted from Google's API that inserting comments that binds to a region in document with highlighting is a not a feature that can be programmatically inserted into their Google Doc. Users will need to manually insert their comment to access this feature. There are code here that was set up to address this issue but will need more time to implement a workaround solution.
• Avoid reporting duplicate information when inserting new comment boxes to a Google Doc. IP will need to understand what comments already exist before generating new comments that might be considered as duplicate information. This will be a high level of concern when deleting and editing a comment box because comments are restricted to the user that created them. If multiple users are calling IP to insert comments then comments will not be resolved unless the original author of the comment goes in to remove the comment. If an admin credential is used to insert these comments, then IP will need to handle quota limitations for each request made to a Google API.
• Comments can get lengthy (comments per table). Visually, it might not look easy to the eye for reading so be selective with the wording.