# Data model

1. **Entity type**

online identity A network identity is the highest level logical grouping of drives and files. All folders and files must be part of a network identity and reference that identity's Identity ID.&#x20;

Network entities enable file transfer, view query, linking and other functions. driver Drives are logical groupings of other files. The driver is automatically generated by the system, and the generation standards are Private Files and Public Files. document Files contain uploaded data such as documents, pictures, etc.&#x20;

In a decentralized file system, a file is divided into two parts - metadata and data. File data must be uploaded as a separate transaction. Metadata contains references to file data information so that it can retrieve the actual data.&#x20;

Metadata ensures that files can be encrypted so that no unauthorized person can see the file or its metadata.

2. **Entity Relationships**

High-level Connections between Network, Drive, Folder, and File Entities (with Visual Description) In the Drive3 system, there are distinct relationships between network, drive, folder, and file entities, each associated with its relevant metadata.&#x20;

Every file within Drive3 contains metadata that points to its corresponding drive. Drive Entity: A drive entity possesses its own metadata; however, it does not include information about its sub-content. As a result, customers need to establish the drive's status by starting from the bottom and gradually progressing upwards.&#x20;

Visual Description: Unfortunately, as a text-based AI model, I am unable to provide visual representations. For a more comprehensive understanding of the entity relationships within Drive3, please refer to the provided documentation or seek assistance from the Drive3 team.

3. **Data format**

Metadata stored in Drive3 will be defined as follows { "name": "Example-Tag", "value": "example-data" }
