Skip to content

[BI-2751] - Germplasm entry number weirdness#494

Open
HMS17 wants to merge 4 commits intodevelopfrom
bug/BI-2751
Open

[BI-2751] - Germplasm entry number weirdness#494
HMS17 wants to merge 4 commits intodevelopfrom
bug/BI-2751

Conversation

@HMS17
Copy link
Contributor

@HMS17 HMS17 commented Feb 3, 2026

Description

Story: BI-2751 - Germplasm entry number weirdness

Changes to processing germplasm import to match user expectations of behavior.

  • Updated error message re parental entry numbers for clarity
  • Parental entry numbers will not be saved to additional info on germplasm creation, and not show up when importing the same germplasm in future imports
  • Change in behavior where if a germplasm already has a pedigree in the database, any file pedigree information should be ignored rather than validated and potentially return errors

NOTE that the import preview not containing entry numbers will only work for germplasm created after this change, a migration would be needed to remove parental entry numbers from additional info of existing germplasm

NOTE germplasm name in the upload file must be correct for error behavior to work properly, making logic solely dependent on accession no will be work of future card

Dependencies

bi-web:develop

Testing

Create new program, ensure test cases in linked card now pass

Checklist:

  • I have performed a self-review of my own code
  • I have tested my code and ensured it meets the acceptance criteria of the story
  • I have tested that my code works with both the brapi-java-server and BreedBase
  • I have create/modified unit tests to cover this change
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to documentation
  • I have run TAF: <please include a link to TAF run>

@github-actions github-actions bot added the bug Something isn't working label Feb 3, 2026
@HMS17 HMS17 requested review from a team, davedrp, mlm483 and nickpalladino and removed request for a team, davedrp and mlm483 February 9, 2026 16:58
@HMS17 HMS17 marked this pull request as ready for review February 9, 2026 16:59
return false;
}

// Error conditions:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing this to silently ignore pedigree conflicts instead of rejecting conflicting updates seems like it could be misleading to the user. Was there a reason for removing this?

if (femaleParentFound) {
brAPIGermplasm.putAdditionalInfoItem(BrAPIAdditionalInfoFields.GERMPLASM_FEMALE_PARENT_GID, femaleParent.getAccessionNumber());
//entry number no longer needed for figuring out parentage, can remove (since same germplasm can have different entry numbers across multiple lists)
brAPIGermplasm.putAdditionalInfoItem(BrAPIAdditionalInfoFields.GERMPLASM_FEMALE_PARENT_ENTRY_NO, null);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw the comment in the PR description about these still showing up without a migration for old records. Is that something we need a card for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants