Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Authentication (Auth): This pivotal module is responsible for user management and access control within TraceConnect. It empowers administrators to define and manage user roles and permissions, ensuring that users have the appropriate level of access to the system's features. In addition to handling internal user authentication, the Auth module plays a crucial role in managing OAuth connections for external services. This includes the secure integration of external applications and services, enhancing the overall security and functionality of TraceConnect.

  2. Supply Chain: The Supply Chain module serves as the backbone of the system, encompassing the comprehensive management of the supply chain structure. This includes the tracking of companies, farmers, products, and their interconnected relationships. Within this module, the crucial task of managing farmer cards is executed, providing a seamless means of validation during transactions and interactions within the supply chain. The Supply Chain module ensures that all stakeholders are effectively interconnected, contributing to the streamlined flow of goods and information.

  3. Transactions: At the heart of TraceConnect's functionality lies the Transactions module, where all transactions between companies and farmers are meticulously recorded and managed. This encompasses a wide range of activities, including product transactions and the tracking of farmer payments.

  4. Configurations (Configs): The Configurations module is dedicated to tailoring the TraceConnect experience to suit specific requirements. It offers administrators the ability to customize various aspects of the app's functionality. This includes configuring premium settings, allowing for the fine-tuning of features, and controlling user access privileges. Importantly, administrators can make on-the-fly adjustments, such as enabling or disabling the "Buy" feature for specific collectors, ensuring that the system remains agile and adaptable to evolving needs.

  5. Forms: Within the Forms module, administrators can configure custom forms to collect additional data relevant to their specific workflows. These forms provide flexibility and versatility, allowing TraceConnect to capture and process a wide array of data types. Whether it's capturing unique data points or adapting to changing data requirements, this module empowers users to enhance their data-capturing capabilities, ultimately improving the precision and completeness of their records.

...

Database Architecture

...

Our database architecture has been thoughtfully designed to prioritise simplicity and minimalism while maintaining efficient data management. Central to this architecture is the "company" table, which serves as the core entity around which all data structures revolve. This approach ensures clean separation and allows multiple companies to utilise the same server without data overlap.

In the provided high-level database architecture diagram, the following key elements are illustrated:

  1. Company-Centric Structure: Each company has the autonomy to onboard its own collectors as app users, thereby establishing a dedicated user base within the system.

  2. Customisable Preferences: Companies have the flexibility to define their app preferences, such as specifying premium requirements, configuring app functionality, and setting their preferred products for collection.

  3. External Connections: Companies can tailor their external connections and define the scope of their interactions within the system, granting them control over data flow and integration.

  4. Farmers: All farmers are onboarded or connected to specific companies, fostering a well-organised and efficient ecosystem.

  5. Product Transactions: The flow of product transactions occurs from farmers to the company table, creating a clear linkage between the products collected and the associated payment transactions.

  6. Payment Transactions: Payment transactions, vital for compensation to farmers, flow from the company to the farmer. The verification process is conducted seamlessly through the use of farmer cards.

User flow

Data fields

APIs

User flowMobile app Configurations

Roadmap

  1. November 2023: initial deployment and like it to the mobile app. Also, enable sync services 

  2. December 2023: publishing the apis APIs and first open-source release 

  3. Jan 2024: publishing apis Publishing APIs and external server connection

  4. Feb 2024: enable Trace SSO

  5. May 2024: First Python SDK release 

...

In the connect database structure we focus mainly on two main components, companies and it’s their farmers and their transactiontransactions. Additionally, there are database table tables to configure and customise the app, set permium premium payment to farmers and some access control details

In On the farmer side, we are collecting the following fields

Transaction fileds files are like this

Permium Premium table

Concept

  • Stand-alone module to handle all the incoming and outgoing data to Trace

  • It will get connected to the mobile app via APIs and fetch data then sync it to trace

  • It will also be connected to a system like PTCAN and then send and receive data

  • It has its own DB and a fronted and possible to self-host

  • There will be a Python lib to manage all the interactions to the standalone module

  • This python ThisPythonn lib is installed on installedon thee trace server and other systems to push and pull data

  • Users can also do mobile app customizations in the module like custom forms

  • It handles the transactions and connections from a single company perspective.

...