UC3 - Magic Mirror Admin CLI
The limited scope of the garments included in the pilot application for use case 3 meant that case for the back office application was much weaker than originally envisaged, so the project to decided to prepare the data manually through the Google Cloud interfaces and dispense with development of the CLI. This document is retained for future reference.
Scenario 1: Add Garment FBX file for a product in the catalogue
- Actor
- 3D Designer
- Overview
- The designer uploads an fbx file to add a garment so that end users can dress up in it. The metadata is looked up from the product feed data by product id.
- Preconditions
- The designer must have arranged the panel pieces for the garment on the standard avatar
- The fbx file must be named according to the Odlo file naming convention.
- Operation
Scenario 2: Add Garment FBX file for a product not in the catalogue
- Actor
- 3D Designer
- Overview
- The designer uploads a fbx file to add a garment so that end users can dress up in it. They must provide the metadata.
- Preconditions
- The designer must have arranged the panel pieces for the garment on the standard avatar
Metadata :
Field | Description |
---|---|
title | The garment title |
uid | A garment unique id (EAN code) |
group_id | This is the id that corresponds to the specific garment, regardless of color or size. |
gender | male or female |
size | s , m , l , xl , xxl |
color | A string that denotes the color of the garment |
photo | A url for a photo depicting the garment |
src.file | Firebase Storage url for the 3D file |
material | The garment material |
product_type.full_type | A string that has the full type (path) of a garment (e.g.: "Men>Sporting Activity>Running & Trail" ) |
product_type.extracted_type_0 | A string that features the first segment of a full_type string (if applicable) |
product_type.extracted_type_1 | A string that features the second segment of a full_type string (if applicable) |
product_type.extracted_type_2 | A string that features the third segment of a full_type string (if applicable) |
price | A price string in euro with two decimals (e.g.: 64.95 ) |
eshop_link | A link to the ODLO e-shop linking to the specific garment in order for the user to purchase it |
additional_information.custom_label_0 | Any additional metadata the garment has available (for filtering purposes). Taken from the custom_label fields that are inside the .csv file that ODLO provides |
additional_information.custom_label_1 | Any additional metadata the garment has available (for filtering purposes). Taken from the custom_label fields that are inside the .csv file that ODLO provides |
additional_information.custom_label_2 | Any additional metadata the garment has available (for filtering purposes). Taken from the custom_label fields that are inside the .csv file that ODLO provides |
additional_information.custom_label_3 | Any additional metadata the garment has available (for filtering purposes). Taken from the custom_label fields that are inside the .csv file that ODLO provides |
- Operation
Scenario 3: List Garments
- Actor
- 3D Designer
- Overview
- The designer can list all garments that are uploaded in FireStore. The listed entries contain all data fields.
- Preconditions
- There must be garment entries uploaded to FireStore.
- Operation
Scenario 4: Delete a Garment entry
- Actor
- 3D Designer
- Overview
- The designer can delete a garment entry by uid.
- Preconditions
- The garment entry to be deleted must exist.
Operation :
Scenario 5: Alter Garment entry
- Actor
- 3D Designer
- Overview
- The designer can alter fields in a garment entry.
- Preconditions
- The garment entry to be altered must exist.
Operation :