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

[BUG]: Renaming trait breaks linkage to existing phenotypes #981

Open
tatesircin opened this issue Jun 7, 2024 · 4 comments
Open

[BUG]: Renaming trait breaks linkage to existing phenotypes #981

tatesircin opened this issue Jun 7, 2024 · 4 comments
Labels

Comments

@tatesircin
Copy link

Description

When exporting trait data, one set of data was exported only partially. It was categorical data and only 15 entries of about 100 was present in the csv file. Within the app the data is recorded.

Expected behavior

No response

Field Book version

5.5.24

@tatesircin tatesircin added the bug label Jun 7, 2024
@trife
Copy link
Member

trife commented Jun 8, 2024

I have a feeling I know what the issue is, but can you email me your exported database zip (Settings > Database > Export)?

You can also try updating to the version available on GitHub (soon to be on Google Play).

@tatesircin
Copy link
Author

tatesircin commented Jun 9, 2024 via email

@trife
Copy link
Member

trife commented Jun 10, 2024

@tatesircin I don't think GitHub forwards email attachments to the issue replies. You'll have to either manually attach it or email it to my main email it directly to me (twrife@clemson.edu).

@trife trife changed the title Data not exported properly[BUG]: [BUG]: Renaming trait breaks linkage to existing phenotypes Jun 10, 2024
@trife
Copy link
Member

trife commented Jun 10, 2024

From the database you sent, it looks like the trait was renamed midway through collection (Stipule vs Stipple) which broke the linkage between the data. The fastest way to fix this is going to be to "recollect" the phenotypes (unmark/remark the category). We'll work on getting this fixed in v6, but it's not going to change your current situation.

Related to #471

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

2 participants