<aside> 💡

The moving interface is preferred to update the Digeiz database when a moving event happens (e.g., Zara is moving into the wall currently occupied by H&M in one month’s time). In this documentation, the manual moving procedure is described. It can be then automated using the moving API : https://api.digeiz.fr/malls-metadata/docs#/Moving

</aside>

Moving record structure

The structure of a moving record is first introduced to understand which key information are saved inside digeiz database.

Wall vs block

Digeiz identifies brands at the wall level, the smallest entity inside the mall. A wall is the physical space corresponding to one store on a given floor. When a store is spread on multiple floors, this is a block, so that multiple walls can be linked to a block.

Wall infos - moving record

A moving record in the digeiz database corresponds to the link between a wall and a brand for a given time range. And since a brand can have multiple categories associated with it depending on the items sold inside these specific stores (ex: H&M can be family clothing, or only women's clothing), a moving record contains the following information:

• wall_id
• brand_id
• category_id
• from_date
• to_date (can be null if still active)

Moving record process

<aside> ➡️

A series of moving events can be completed by uploading a CSV to our platform.

</aside>

Automatically matching IDs

Step 1: To start off a moving event, go to app.digeiz.com and look for the button in the left tool bar called - Map wall changes.