Meeting Minutes Feb 16 18

2018-02-16

Location	Time	Duration
CSC-262	12:00 - 14:00	2hr

Meeting with Diego

• Outlined progress thus far
• Showed demo's of the separate components
• Decided that Austin will switch from PDF scraping to front end

Meeting with Eleni

• Demo'ed progress to her, discussed the upcoming demo to Ann
• She's a bit stressed that we don't have visualizations
  • Austin will focus on creating visualizations
• Issue with potential for elastic search bad actor participation.
  • Will move to a private elastic search if possible

Meeting with Conner and Daniel

• Some notes about improving our github practices
  • Branching strategies brought up; they will send us links over Discord
  • Should differentiate master branch (production ready, polished product) and developing branches
  • Continuous integration - Travis brought up
  • Suggested locking branches (have to create pull request to merge - that way, can't approve self => someone else has to approve it; good for having more eyes on the code)
• Made into a note, will turn into issues.
• Elasticsearch authentication
  • Change configurations
    • Only allow GET requests, don't allow POST requests, etc.
  • Should have Apache/Nginx running in front of ES anyways
• ES vs. Relational Database: Denilson's recommendations
  • ES is fine (don't need to have a relational database)
  • Create multiple indices (data duplication is okay)
    • Multiple copies of same data in multiple indices is good
    • Keep ES flat
      • Try not to nest too much because of parent-child relationships in ES (just create one document, one big JSON doc)
  • Content of body (create multiple indexes, like trigrams to make autocompletion faster)
• Normalization/Tokenization
  • Let them know we make tokens out of named entities, probably no normalizing test planned
• They asked about cores in Vue
  • Let them know we're getting rid of it soon
  • Make sure not final version
  • We don't have proper API with backend yet
• Recommended browsershots.org
  • Allow to throw URL and load website on different OS and use as 'testing' on variety of browsers
  • May be other tools, but this one works!
• Brought up Postman
  • We are currently using Postman
  • Django REST has a view too by itself
• Heads up:
  • Look at architecture stuff