Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-1969

Make initial plans for Quickload Builder site

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Story Points:
      5
    • Sprint:
      Fall 8 : 25 Nov to 6 Dec, Fall 9 : 9 Dec to 20 Dec, Spring 1 : 25 Dec to 17 Jan

      Description

      Task: Determine how the Quickload Builder site will be implemented. What frameworks, databases, and single-sign on will be used.

        Attachments

          Activity

          Hide
          stiwari8 Srishti Tiwari (Inactive) added a comment -

          The user perspective is in the following location in the google drive:
          IGB Project Documentation and Plans > Quickload Automation > User Perspective

          Show
          stiwari8 Srishti Tiwari (Inactive) added a comment - The user perspective is in the following location in the google drive: IGB Project Documentation and Plans > Quickload Automation > User Perspective
          Hide
          stiwari8 Srishti Tiwari (Inactive) added a comment -

          When IGB requests for contents.txt, annots.xml, species.txt etc, we will need to create rest endpoints which return a stream response on the fly from the database. This way we do not need to store anything other than the database on the server.

          Show
          stiwari8 Srishti Tiwari (Inactive) added a comment - When IGB requests for contents.txt, annots.xml, species.txt etc, we will need to create rest endpoints which return a stream response on the fly from the database. This way we do not need to store anything other than the database on the server.
          Hide
          stiwari8 Srishti Tiwari (Inactive) added a comment -

          I suggest the above tooling based on the team's familiarity with above tools and technologies. As we want to keep the database relational along with Django framework, PostgreSQL 11 seems to be an obvious choice. Please let me know if you have any suggestions.

          Show
          stiwari8 Srishti Tiwari (Inactive) added a comment - I suggest the above tooling based on the team's familiarity with above tools and technologies. As we want to keep the database relational along with Django framework, PostgreSQL 11 seems to be an obvious choice. Please let me know if you have any suggestions.
          Hide
          stiwari8 Srishti Tiwari (Inactive) added a comment -

          Backend - Django framework
          Frontend - HTML5, JS, Bootstrap4
          Database - Postgresql
          Single sign-on - Google

          Show
          stiwari8 Srishti Tiwari (Inactive) added a comment - Backend - Django framework Frontend - HTML5, JS, Bootstrap4 Database - Postgresql Single sign-on - Google

            People

            • Assignee:
              stiwari8 Srishti Tiwari (Inactive)
              Reporter:
              nfreese Nowlan Freese
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: