Open Tickets

IssueCommentsPRStatusProposal

DM-24283 - Getting issue details... STATUS

Jeremy McCormick tagged with component "sdm_schemas" as it was missing and there is an active PR.

openin review

DM-26858 - Getting issue details... STATUS

This is a general concern that has been incorporated into the roadmap and will be addressed when the Pydantic changes are merged and the validation enabled. The Team is "Data Access and Database" which looks outdated. The ticket is also old. It can probably be closed in lieu of tickets addressing more specific issues.
to dodone (question)

DM-27451 - Getting issue details... STATUS

Probably some/all changes were already incorporated given the age of the ticket (Nov 2020).
to dodone (question)

DM-31049 - Getting issue details... STATUS

This ticket is tagged with a number of sprints but was never resolved. There is a reference in the comments to an external project from Simon Krughoff.


to do

DM-34685 - Getting issue details... STATUS

Comment from Colin Slater says, "I can't remember if there was something this review was waiting on, but it's certainly done now."

openrevieweddone (question)

DM-34814 - Getting issue details... STATUS

Gregory Dubois-Felsmann indicates additional revisions can be covered by another ticket.

mergedin progressreview (question)

DM-35125 - Getting issue details... STATUS

Work still ongoing? Is this covered by other tickets?mergedin progressreview (question)

DM-35174 - Getting issue details... STATUS

Needs summary of remaining work requested by Gregory Dubois-Felsmann . (Why is review completed if the PR is still open?)

openreviewed

DM-35184 - Getting issue details... STATUS



to do

DM-35667 - Getting issue details... STATUS

There is an open PR but the changes largely look outdated/superseded.openin progress

DM-35846 - Getting issue details... STATUS

No assignee
to do

DM-35950 - Getting issue details... STATUS

Eric Bellm says, "Looks good to me."


revieweddone (question)

DM-35956 - Getting issue details... STATUS


mergedrevieweddone (question)

DM-35983 - Getting issue details... STATUS

Should this be marked as a "story" rather than a "bug?"
to do

DM-35984 - Getting issue details... STATUS

Blocked by issue about adding multiple FKs.
in progress

DM-35985 - Getting issue details... STATUS



to do

DM-36077 - Getting issue details... STATUS


mergedin reviewreview (question)

DM-36082 - Getting issue details... STATUS

Waiting for deployment on data-intmergedrevieweddone (question)

DM-37503 - Getting issue details... STATUS

In discussion
to do

DM-39203 - Getting issue details... STATUS

Jeremy McCormick tagged with component "sdm_schemas" as it was missing and there is an active PR.

openin progress

DM-39309 - Getting issue details... STATUS


mergedin progressreview (question)

DM-39540 - Getting issue details... STATUS

No assignee
to do

DM-40542 - Getting issue details... STATUS



to do

DM-40544 - Getting issue details... STATUS



to do

DM-41029 - Getting issue details... STATUS

This should actually be marked as "in progress" rather than "to do" given that there is open PR and it is seemingly being actively developed by Andy Salnikov.opento do

DM-41290 - Getting issue details... STATUS

Development on this issue should be preceded by a tech note.
to do

DM-41310 - Getting issue details... STATUS

No assignee
to do

DM-41347 - Getting issue details... STATUS

This seems to be effectively blocked until the mess with JSON-LD "@id" references is resolved when processing FKs in the felis visitor class(es).
to do

DM-41530 - Getting issue details... STATUS

No assignee
to do

DM-41532 - Getting issue details... STATUS

No assignee
to do

DM-41652 - Getting issue details... STATUS


mergedin progress

DM-41867 - Getting issue details... STATUS

No assignee
to do

DM-41890 - Getting issue details... STATUS

This is a big blocker for adding FKs to multiple schemas and needs to be resolved ASAP. (The open PR is just a sample schema and not a fix for this issue.)openin progress

DM-41922 - Getting issue details... STATUS



to do

DM-42003 - Getting issue details... STATUS

This can be reviewed and marked as done after deployment on data-int is checked.mergedin review

DM-42069 - Getting issue details... STATUS


mergedin reviewdone (question)

DM-42082 - Getting issue details... STATUS



to do

DM-42083 - Getting issue details... STATUS



to do

DM-42084 - Getting issue details... STATUS



to do

DM-42085 - Getting issue details... STATUS



to do

DM-42128 - Getting issue details... STATUS

Eric Bellm has proposed some changes to CSV file from Gregory Dubois-Felsmann. This is in reviewed state but that doesn't seem right (should be in progress instead?).


reviewed


Notes

  • Full list of open Jira issues on sdm_schemas component as of December 13th, 2023
  • Filter in Jira to reproduce the above set of issues
  • After a ticket is closed, it should be removed manually from the table.

To Do

  • Assign all issues to PREOPS-3928 - Getting issue details... STATUS and "Data Engineering" team, where applicable?
    Some (mostly) older issues don't have these assigned.
  • New issue: Felis should throw an error rather than just print a warning message when IDs are duplicated. A duplicate ID could result in incorrect column assignment when defining an index or FK and should be completely disallowed when loading/validating. (This should be added to the Pydantic validation. Ideally, the duplicated key value should be printed out.)
  • Proposed improvements/updates to DP0.2 and DP0.3 should be better organized under umbrella issues covering the entire schema, so that they can be found easily and it can be determined if all active issues have been resolved. Right now these can only be found easily by looking for "DP0.x" in the title of the ticket. This could also be done with labels ("DP0.2," etc.).
  • Review several of the older, inactive tickets (>1 year) and determine if they should be closed as "won't fix," especially if there is no GH branch or PR.
  • There are many usages of blank "fits:tunit" and other annotations. It is unclear what is the purpose of doing this. Make a ticket to request clarification.
  • In yml/dp02_dc2.yaml, the MatchesTruth.index and MatchesTruth.match_row columns are commented out. Need to track down whether this means they should be removed from the schema entirely (e.g., delete the commented out lines).