Embed: Extend CeramicCache Model to Include Scorer ID for Stamps

[nutrina]

User Story:

As a data analyst, I want to better understand the context in which a stamp has been created, So that I can evaluate our integrating partners more effectively.

Acceptance Criteria

GIVEN that I am a user of the Passport XYZ embed component, WHEN I create any stamp using the embed component, THEN the stamps should store the scorer_id in the metadata of the stamps that have been created.

Product & Design Links:

N/A

Tech Details:

• Extend the CeramicCache database model to include a nullable field called scorer_id (also known as community_id).
• Whenever a stamp is created due to user interaction with the embed component, this field needs to be set to the active scorer_id used for that integration.

Open Questions:

• [ ] @NadjibBenlaldj: What should the scorer_id field be set to when stamps are created from the Passport App?
  • Should it be set to a default scorer id?
  • Or should it be left as null?

Notes/Assumptions:

• Storing the scorer_id provides valuable context that aids in the evaluation of partners and integrations.
• Clarification is needed on the default handling of scorer_id for stamps not created through the embed component.

[nutrina]

@NadjibBenlaldj another question: shall we store more data than just the scorer_id? Like for example:

• was the stamp created from a custom dashboard
• or from a passport embed setup?

[NadjibBenlaldj]

That would be great: a field with where was the stamp created: custom dashboard or embed + scorer_id and we can set to the default scorer when stamp is created via the Passport App