🗃️User Collections

User Collections Overview

A "User Collection" is essentially an inventory for interoperable objects. Each MSquared user has a user collection. Objects in a user collection come in many forms. Some examples of how object can be used would be: representing currency within a game, conveying ownership of an NFT and acting as containers for media content.

Object Definitions Overview

In order to give an object to a user, we need the object to be defined first. This means configuring the base object. We may for example want to create a user collection currency for our MSquared project. We would first have to make sure an object is defined for our currency. This object definition might include a name for our currency, an image and any other additional data we might need.

Datasources Overview

We add object definitions to datasources. In other words, datasources are containers for object definitions. You can have any number of datasources associated with your project. This helps to

Private Datasources: These are typically where you will want to define most of the objects relevant to your project. Public Datasources: All object defined in the datasources will be automatically added to each user's user collection. You could define some wearable objects hear that all of your users can access. NFT Datasources: These datasources are not directly controlled by an organisation. They can not be created or destroyed. They are concerned with providing data regarding block chain assets.

Diagram outlining the relationship between objects, datasources and user collections. You can see how the object definitions in the datasources have been populated with metadata. You can see all objects in the public datasource are added to the user collection. You can also so that this user collection also contains 10 "pasta" objects but no "soup" objects.