---
# System prepended metadata

title: Notes from CAB meeting on April 30

---

# Notes from CAB meeting on April 30

### Advitiya 
- Accuracy is most important. Need to know the source from where the summary text was quoted.

### Nilesh 

- In summaries, the problem statement should be very clear.
- In some cases, summary creator may miss important terms described in the patent. How can we prevent that?
- It's important to define clearly why this patent was filed and what does it protect. Possibly show key invention with a hotspot of different color.
- All the patent related to a product can be summarised in a single summary. Or the summaries can be grouped together. Including the prior art.
- Login through SSO should be implemented.
- Due diligence by IT department will be conducted before deploying.
- Transparent policy needed for cloud security.
- User/engineer comments can have legal implications. How do we ensure privacy/ allow collaboration while avoiding legal issues?



### Henal

- Product can be used by engineers, researchers and litigation people. Categorisation of literature is important. 
- All the raw unsummarised patents should be shown in the interface so that users can order summaries of them.
- If the users are providing feedback to improve summaries, how are content right shared?
