ABDERRAHMANE ELFANNIR aelfannir

MyMate API — Entity Identifier Prefixes

What are identifiers?

Every entity in the system gets a unique identifier (ID) used in URLs, QR codes, and API calls. For example, when a guest shares their booking reference or scans a QR code for a restaurant, they see this identifier.

Format: {prefix}_{random suffix} → e.g. act_a1b2c3

Prefix identifies the type of entity (rm = room, gst = guest, etc.)
Suffix is a random string that makes each ID unique

Identity Redesign: Impact Assessment

Document: "Identity, Profiles & Authentication — Final System Design" Date: 2026-03-25

What's Being Proposed

Today, every guest in MyMate is a single record: one person, one email, one profile. Simple.

Booking Recommendations — Required Changes

Context

We have a proper API contract for BookingRecommendation as a Hydra resource:

Contract: booking-recommendations.yaml

Currently the AI service streams recommendations directly to the frontend via SSE (POST /recommendations), returning flat objects like:

Chat AI — Structured Data Format (SSE)

When the AI presents entities to the guest in chat, it streams JSON-LD objects from our API as SSE events. The frontend renders cards as they arrive using @type to pick the component.

Why This Approach

No custom format: standard API Platform JSON-LD responses — same shape the frontend already handles
Progressive rendering: cards appear one by one as the AI streams them
Scalable: any entity from our API works. New entity types or fields are picked up automatically.
Conversation storage: structured data is stored as-is. Old conversations keep the original data as a snapshot.

UC: Booking Details — Personalised Recommendations

Domain: Smart Features Status: Draft

Description: When the guest opens a booking details screen, the frontend triggers a recommendation request to the AI service. The AI fetches guest data and booking history from MyMate API, enriches it with external data sources (weather, local events, etc.), and streams back personalised recommendations for the remaining stay.

Conversation Example:

Guest opens booking details for their Grand Plaza stay (3 nights left).

Requirement

typeahead.js
Bloodhound.js
Handlebars.js

	<?php

	namespace App\Doctrine;

	use Doctrine\ORM\Query\AST\ASTException;
	use Doctrine\ORM\Query\AST\Functions\FunctionNode;
	use Doctrine\ORM\Query\AST\Subselect;
	use Doctrine\ORM\Query\Parser;
	use Doctrine\ORM\Query\QueryException;
	use Doctrine\ORM\Query\SqlWalker;

	<?php
	declare(strict_types=1);

	namespace App\Entity;

	use ApiPlatform\Core\Annotation\ApiFilter;
	use ApiPlatform\Core\Annotation\ApiResource;
	use ApiPlatform\Core\Bridge\Doctrine\Orm\Filter\SearchFilter;
	use App\Entity\Classes\Group;
	use App\Entity\Traits\HasId;

	<?php
	//...
	class Dci
	{
	/**
	* @Groups("dcis:read", "dcis:write", "medicaments:write")
	* @ORM\ManyToMany(targetEntity=Medicament::class, inversedBy="dcis", cascade={"persist"})
	*
	*/
	private $dci;

	<?php

	namespace App;

	use Illuminate\Foundation\Auth\User as Authenticatable;

	/**
	* Class User
	* @package App
	*/