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

Additional curation features to facilitate imports into the Curation Workflow #34

Merged
merged 13 commits into from
May 8, 2018

Conversation

gaurav
Copy link
Member

@gaurav gaurav commented Apr 5, 2018

This pull request changes some aspects of the PHYX model in order to facilitate curation and to keep the Curation Tool in sync with the Curation Workflow. These changes includes:

This pull request is ready to be merged.

@gaurav gaurav force-pushed the improved_curation branch from 32425e1 to 05e9908 Compare April 5, 2018 21:35
@gaurav gaurav force-pushed the improved_curation branch from 05e9908 to d205300 Compare April 9, 2018 21:41
@gaurav gaurav changed the base branch from renaming_nodes to master April 9, 2018 21:42
@gaurav gaurav force-pushed the improved_curation branch from be8682e to 8709ef7 Compare April 10, 2018 21:32
@gaurav gaurav changed the title Improved curation through testing and creating new PHYX files Improved curation UI through testing and creating new PHYX files Apr 11, 2018
@gaurav gaurav force-pushed the improved_curation branch from 33dbd8f to 934f124 Compare April 11, 2018 00:55
@gaurav gaurav self-assigned this Apr 11, 2018
@gaurav gaurav changed the base branch from master to improved_user_interface April 16, 2018 23:34
@gaurav gaurav force-pushed the improved_curation branch from 32e1325 to 56dba01 Compare April 16, 2018 23:37
@gaurav gaurav changed the title Improved curation UI through testing and creating new PHYX files Updated PHYX model to improve curation Apr 16, 2018
@gaurav gaurav force-pushed the improved_curation branch from 56dba01 to 5b447ee Compare April 17, 2018 00:06
@gaurav gaurav force-pushed the improved_curation branch 2 times, most recently from 28300bf to 9aacd52 Compare April 17, 2018 21:09
@gaurav gaurav changed the title Updated PHYX model to improve curation Additional curation features to facilitate imports into the Curation Workflow Apr 17, 2018
@gaurav gaurav requested a review from hlapp April 18, 2018 01:22
Copy link
Member

@hlapp hlapp left a comment

Choose a reason for hiding this comment

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

Only two comments. The one about including a record that identifies the curator should I suppose best be handled by breaking the issue out from here.

The second is about an inconsistency, and even if it's only fixing the HTML-commented text (in case I'm missing something in my comment), something should be done about it.

@@ -810,14 +810,17 @@
{
"label": "Laurasiarana",
"cladeDefinition": "Laurasiarana, new clade name. Definition: The clade stemming from the most recent common ancestor of Rana temporaria Linne 1758 and Rana aurora Baird and Girard 1852.",
"curatorComments": "The Laurasiarana expected node is not found in the TreeBase tree, so I've placed it where I think it should go.",
Copy link
Member

Choose a reason for hiding this comment

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

I don't think we currently have fields for identifying the curator (remind me if this is not true), but this comment reminds me that we do need to add this, at least in the form of name and ID, the latter presumably being an ORCID.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point! I've added this as issue #59.

index.html Outdated
manually added to the PHYX file using the "Display as JSON"
option.
-->
<label for="testcase-id" class="col-md-1 control-label">Testcase IRI</label>
Copy link
Member

Choose a reason for hiding this comment

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

So it seems that we have a whole code block here to deal with a property we don't actually want to be used. If we had a large legacy of PHYX files, this may well be justified, but we don't. If this property is present in some files previously created, can't we just fix those files, especially given that nothing is in production yet anyway?

@gaurav
Copy link
Member Author

gaurav commented May 8, 2018

Thanks for the comments, Hilmar! In removing the @id field, I cleaned up and modernized the example PHYX files a little. Would you like to review these minor changes, or should I go ahead and merge this PR?

Copy link
Member

@hlapp hlapp left a comment

Choose a reason for hiding this comment

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

Looks good!

@gaurav gaurav merged commit fd7d39b into improved_user_interface May 8, 2018
@gaurav gaurav deleted the improved_curation branch May 8, 2018 21:13
gaurav added a commit that referenced this pull request Jan 29, 2019
This pull request changes some aspects of the PHYX model in order to facilitate curation and to keep the Curation Tool in sync with the Curation Workflow. These changes includes:
- Removed `@id` field (closes #2).
- Added a verbatim specifier field for all specifiers (closes #17).
- Added a curator comments field for all phyloreferences (closes #24).
- Allows the curator to document that they expect a single node to resolve to multiple phyloreferences by selecting a matching labeled node from the phyloreferencing panel (#32).
- Added a simple system for marking specifiers that could not be matched (#49).
- Improved display of scientific names and specimens as specifiers.
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

Successfully merging this pull request may close these issues.

2 participants