<commit_before># Agenda

* Ask Maia if she can take minutes

* Need to finalize Requirements Doc. Due this Thursday.
    * There is a doc on google drive with the sections that need to be in there
    * Any other sections that might need to be there(?)
         * check the slides for requirements; outline for what should be included is written there

* Stephen and I should start working on the database and set our goals for the week.

* Anushka and Shrey should start working on some of the front-end pages and set goals for the week.

* Maia would probably need to work everyone to figure out what front-end functions are required and what back-end functions are required.

* Lets aim to do our respective tasks by next Wednesday.

* Ask TA for feedback on Piazza about previous milestone and ask any follow-up questions that we had thought of for the Coast Capital people.

* We could use Tableau instead of d3.js

# Minutes

<table>
	<tr>
  	<th>TOPIC</th>
    <th>DISCUSSION</th>
  </tr>
  <tr>
  	<td>Finalizing requirements for the next deliverable</td>
    <td>
      We will have to wait for our professor to go through his requirements in full.
      His slides were posted on Saturday and he will go into details on Tuesday; if not, we will have to ask him our questions.
      More is better than less so if anything, we should write as much as possible.
      We should do both business and technical requirements.
      Technical requirements would be more specific as to what systems we will be using, what we will be supporting, etc.
      We can copy the revision history from the TOR sheet for this purpose.
      We should use the same format but not the same headings.
      Should we involve business diagrams?
      [Shrey]
      Assumed to be the same things being done in CPSC 355.
      Business Process Flow Charting
    </td>
  </tr>
  <tr>
  	<td>Implementing the system</td>
    <td>
      We should start implementing the system. Stephen and Vaastav will start designing the database, Shrey and Anushka should start designing and implementing the UI while Maia will be the middle-man, who should start implementing functionalities that are being brought in by UI and asking for the backend implementation from Vaastav and Stephen.

      [Vaastav]
      Different layers:
      <ul>
        <li>Database</li>
        <li>Backend</li>
        <li>Communication between back and UI/front end</li>
      </ul>
      [Shrey, Maia]
      Should decide what framework to bring in for front end
    </td>
  </tr>
  <tr>
  	<td>Grades and feedback from last deliverables</td>
    <td>
      Can try asking for feedback but there is little chance it will be of any good. We should apply the feedback if they give it to us but if not we can’t do anything about it.
    </td>
  </tr>
  <tr>
  	<td>Using Tableau?</td>
    <td>
      [Shrey]
      Can be integrated into JS, and the good thing about it is that you can edit the graph after making it.
      Should make sure the token is not too restrictive and is free for us.

      [Vaastav]
      If did not work should just go for d3. With any packages that we are looking at, we should make sure it’s usable for us and it will be scalable by the company after we’re done.

      [Stephen]
      There are so many packages to use for graph envisioning, and one of the good ones out there is chart.js. Should definitely make sure the package we use are compatible with IE11.
    </td>
  </tr>
  <tr>
  	<td>For Wednesday's Meeting</td>
    <td>
      Should have majority of the things done around Wednesday since a lot of us will be offline/away during the weekend.

      <ul>
        <li>Priority #1: Requirements</li>
        <li>
          Next priorities:
          <ul>
            <li>Database schema</li>
            <li>Front end environment setup (make sure you’re aware of licenses, browser compatibility, etc)</li>
          </ul>
        </li>
      </ul>      
    </td>
  </tr>
  <tr>
  	<td>Admin Privileges</td>
    <td>
      Discussions around Admins vs. Super Admins vs. Users
      <ul>
        <li>Should admins be able to add other admins?</li><commit_msg>fix the formatting of the document<commit_after># Agenda

* Ask Maia if she can take minutes

* Need to finalize Requirements Doc. Due this Thursday.
    * There is a doc on google drive with the sections that need to be in there
    * Any other sections that might need to be there(?)
         * check the slides for requirements; outline for what should be included is written there

* Stephen and I should start working on the database and set our goals for the week.

* Anushka and Shrey should start working on some of the front-end pages and set goals for the week.

* Maia would probably need to work everyone to figure out what front-end functions are required and what back-end functions are required.

* Lets aim to do our respective tasks by next Wednesday.

* Ask TA for feedback on Piazza about previous milestone and ask any follow-up questions that we had thought of for the Coast Capital people.

* We could use Tableau instead of d3.js

# Minutes

<table>
	<tr>
  	<th>TOPIC</th>
    <th>DISCUSSION</th>
  </tr>
  <tr>
  	<td>Finalizing requirements for the next deliverable</td>
    <td>
      We will have to wait for our professor to go through his requirements in full.
      His slides were posted on Saturday and he will go into details on Tuesday; if not, we will have to ask him our questions.
      More is better than less so if anything, we should write as much as possible.
      We should do both business and technical requirements.
      Technical requirements would be more specific as to what systems we will be using, what we will be supporting, etc.
      We can copy the revision history from the TOR sheet for this purpose.
      We should use the same format but not the same headings.
      Should we involve business diagrams?
      [Shrey]
      Assumed to be the same things being done in CPSC 355.
      Business Process Flow Charting
    </td>
  </tr>
  <tr>
  	<td>Implementing the system</td>
    <td>
      We should start implementing the system. Stephen and Vaastav will start designing the database, Shrey and Anushka should start designing and implementing the UI while Maia will be the middle-man, who should start implementing functionalities that are being brought in by UI and asking for the backend implementation from Vaastav and Stephen.

      [Vaastav]
      Different layers:

      <ul>
        <li>Database</li>
        <li>Backend</li>
        <li>Communication between back and UI/front end</li>
      </ul>

      [Shrey, Maia]
      Should decide what framework to bring in for front end

    </td>
  </tr>
  <tr>
  	<td>Grades and feedback from last deliverables</td>
    <td>
      Can try asking for feedback but there is little chance it will be of any good. We should apply the feedback if they give it to us but if not we can’t do anything about it.
    </td>
  </tr>
  <tr>
  	<td>Using Tableau?</td>
    <td>
      [Shrey]
      Can be integrated into JS, and the good thing about it is that you can edit the graph after making it.
      Should make sure the token is not too restrictive and is free for us.

      [Vaastav]
      If did not work should just go for d3. With any packages that we are looking at, we should make sure it’s usable for us and it will be scalable by the company after we’re done.

      [Stephen]
      There are so many packages to use for graph envisioning, and one of the good ones out there is chart.js. Should definitely make sure the package we use are compatible with IE11.
    </td>
  </tr>
  <tr>
  	<td>For Wednesday's Meeting</td>
    <td>
      Should have majority of the things done around Wednesday since a lot of us will be offline/away during the weekend.

      <ul>
        <li>Priority #1: Requirements</li>
        <li>
          Next priorities:

          <ul>
            <li>Database schema</li>
            <li>Front end environment setup (make sure you’re aware of licenses, browser compatibility, etc)</li>
          </ul>

        </li>
      </ul>

    </td>
  </tr>
  <tr>
  	<td>Admin Privileges</td>
    <td>
      Discussions around Admins vs. Super Admins vs. Users
      <ul>
        <li>Should admins be able to add other admins?</li>
{'fraction_non_alphanumeric': 0.06099171569215992, 'fraction_numerical': 0.0019209989194381078, 'mean_word_length': 2.7220732797140306, 'pattern_counts': {'":': 0, '<': 131, '<?xml version=': 0, '>': 131, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4695168', 'n_tokens_mistral': 2301, 'n_tokens_neox': 2245, 'n_words': 1226}