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

Inconsistency in pfid in tables/plant/import table #89

Open
petermr opened this issue Aug 2, 2019 · 2 comments
Open

Inconsistency in pfid in tables/plant/import table #89

petermr opened this issue Aug 2, 2019 · 2 comments
Assignees

Comments

@petermr
Copy link
Collaborator

petermr commented Aug 2, 2019

No description provided.

@petermr petermr changed the title Inconsistency in pfid in `importa Inconsistency in pfid in tables/plant/import table Aug 2, 2019
@petermr
Copy link
Collaborator Author

petermr commented Aug 2, 2019

pid	pname	scientificName (gbif)	Normalized name	Details	pfid	phid	Error	kingdom	phylum	class	order	family	genus	species		Synonym 

...

4	Abies sachalinensis	Abies sachalinensis Mast.	Abies sachalinensis	Mast.	71	1		Plantae	Tracheophyta	Pinopsida	Pinales	Pinaceae	Abies	Abies sachalinensis		#N/A
5	Acacia caven	Acacia caven (Molina) Molina	Acacia caven	(Molina) Molina	19	1		Plantae	Tracheophyta	Magnoliopsida	Fabales	Fabaceae	Vachellia	Vachellia caven		Vachellia caven GBIF 2685484

What is pfid? Is it documented anywhere? We need documentation attached to this table.
If it means "plant family id" then the rows above have inconsistent values for pfid and family

ACTION do we need pfid at all? It can be deduced from the species

@petermr petermr assigned petermr and Shruthi-M and unassigned petermr Aug 2, 2019
@Shruthi-M
Copy link
Collaborator

Greetings Sir!
pfid is a foreign key to the previous family table. According to me, pfid does not have to be included in the table as the family is specifically mentioned.

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

No branches or pull requests

2 participants