/
SDA Backend (Breithorn V2)

SDA Backend (Breithorn V2)

Jul 10, 2023

On the back-end side, we have introduced significant enhancements to improve efficiency and streamline operations.

The shift from operation-based models to a campaign-based system has necessitated updates to our CRUD operations, database schema, and functions.

As a part of this transition, we have deprecated operation endpoints, replacing them with campaign endpoints. Despite this change, we have ensured all previous operation-based CRUD features remain accessible via the new campaign endpoints, considering that an operation is essentially a campaign limited to a single event.

In a move to further improve back-end efficiency, we have ceased generating souvenir ticket images on the back-end, which reduces load and boosts performance. This modification, along with the broader architectural changes, signifies our commitment to providing a more scalable, efficient, and user-oriented platform.

Organizer Creation

  1. Ticket URL specification

Extending Operations to Campaigns :

  1. Campaign Creation

  2. Campaign Events Retrieval

  3. Campaign Events Update

  4. Campaigns Retrieval

  5. Campaign - Retrieve Campaign Information

  6. Campaign - General Information Update

  7. Campaign - Image Update

  8. Campaign Deletion/Cancellation

  9. Campaign TIXNGO Event Retrieval

  10. Updating the way we retrieve souvenir ticket

 

 

Product Features 

Product Features 

Organizer Creation - Ticket URL Specification

  • We've introduced a new feature that enables us to specify the URL of the TIXNGO backend we wish to connect with. This enhancement allows SDA to retrieve tickets from a particular TIXNGO backend, offering flexibility to interact with different backend instances as required (for example, switching between p5 and p25 backends).

  • We modified the endpoint to create an organizer, we should now specify the ticket provider backend URL

  • We also created a new endpoint to update this URL, the PROVIDER can modify the backend URL by calling the following endpoint :

Campaign - Creation

  • We transitioned to a campaign-based system from operations to enhance scalability and flexibility. Unlike operations that handle single events, campaigns manage multiple events simultaneously, promoting efficiency and better addressing diverse client needs.

     

  • We deprecated all operations related endpoints :

    • POST /organizer/operations

    • GET /organizer/operations/all

    • GET /organizer/operations/event/{event_id}

    • GET /organizer/operations/event/{operation_id}

    • GET /organizer/operations/status

    • PUT /organizer/operations/{operation_id}/image

    • PUT /organizer/operations/{operation_id}/cancel

    • DELETE /organizer/operations/{operation_id}

  • We provide a new endpoint for the Organizer to create a Campaign :

Campaign - Events Retrieval

  • We provide an endpoint to retrieve all events included in a campaign

 

Campaign - Events Update

  • We provide an endpoint to update the events incl

  • We provide an endpoint to remove events included in a campaign

  • We provide an endpoint to add events included in a campaign

Campaign - Retrieve all campaigns of an organizer

 

  • We provide an endpoint that list all campaigns of an organizer, the endpoint proposes pagination and filtering (status and name)

 

Campaign - Retrieve Campaign Information

  • We provide an endpoint to retrieve Campaigns information

Campaign - General Information Update

  • We provide an endpoint edit the campaign general information (creation time, fetching time, name)
    // TODO : add postman call when implemented

Campaign - Image Update

  • We provide an endpoint edit the campaign image

// TODO : add postman call when implemented

Campaign - Deletion and Cancellation

  • We provide an endpoint that update the status of the campaign to DELETED

// TODO : add postman call when implemented

Campaign - TIXNGO Event Retrieval

  • We provide an endpoint that list all of the organizer events with a field "used" set to true if the event is already part of a campaign. This way we can only show unused event at campaign creation.

Campaign - Updating the way we retrieve souvenir tickets

  • We provide an endpoint that list all souvenir ticket of an organizer. This endpoint proposes pagination and is filterable (ticketId,eventName,spectatorEmail,appId,campaignName)