Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a new field named "version" to the Embeddings model #4438

Open
akolson opened this issue Feb 12, 2024 · 3 comments
Open

Add a new field named "version" to the Embeddings model #4438

akolson opened this issue Feb 12, 2024 · 3 comments
Labels
DEV: backend P1 - important Priority: High impact on UX

Comments

@akolson
Copy link
Member

akolson commented Feb 12, 2024

Overview

This task involves adding a new field named version to the already existing Embeddings model in Studio. This field will be used to track changes between different versions of the embeddings generated by our recommendation models.

Description and outcomes

  • Add the version field to Embeddings in contentcuration/contentcuration/models.py
  • version should be a str with a null default value, and also set as a database index
  • Run the necessary migration commands
  • Add tests that confirm that version has been added correctly

Acceptance Criteria

  • version field is added to the Embeddings schema
  • Tests are written to verify correctness of added field

Assumptions and Dependencies

Scope

The scope of this task is limited to;

  • Adding the “version” field
  • Updating existing schema tests

Accessibility Requirements

NA

Resources

@akolson akolson changed the title [WIP - DO NOT ASSIGN]: Add "version" field to the Embeddings schema [WIP - DO NOT ASSIGN]: Add a new field named "version" to the Embeddings model Feb 20, 2024
@akolson akolson changed the title [WIP - DO NOT ASSIGN]: Add a new field named "version" to the Embeddings model Add a new field named "version" to the Embeddings model Feb 27, 2024
@akolson akolson added P1 - important Priority: High impact on UX and removed work-in-progress TODO: needs updates labels Feb 27, 2024
@thesujai
Copy link

Hello @akolson
Implementing this seems straightforward, is this open for community contribution?

@bjester
Copy link
Member

bjester commented Apr 17, 2024

Hi @thesujai,

Thank you for your interest. This isn't open to community contribution. In fact, we'll most likely close this issue as we pivot the approach soon

@thesujai
Copy link

Alright no issues. Will find something else to work on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DEV: backend P1 - important Priority: High impact on UX
Projects
None yet
Development

No branches or pull requests

3 participants