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

Allow Consuming Tags in the Apply Rules Tool #6545

Merged
merged 5 commits into from
Aug 26, 2018

Conversation

jmchilton
Copy link
Member

@jmchilton jmchilton commented Jul 26, 2018

A few small polish, bug fix commits and then two primary commits to allow using tags more effectively in the Apply Rules tool.

The previously merged PR #6500 allowed setting tags from metadata when importing new collections using the rule builder. 4d83746 included in this PR then lets dataset tags already present to be loaded in when modifying the collection with the "Apply Rules" tool (added in 18.05 as part of #5819). This allows filtering a collection based on tags and re-organizing the nesting structure of a collection based on tags.

18.09 will introduce a new kind of tags - group tags (added in #6491) that like name tags will be auto-propagated but won't be used for naming but instead of categorizing datasets in a factorial analysis. #6500 added support for populating datasets with such tags when importing them using the rule builder and #5457 will add support for tools to effectively consume these group tags. 5807230 included in this PR now lets the user very easily use these tags with the "Apply Rules" tool. This allows certain kinds of filtering and re-organization using group tags specifically that are technically possible after the previous commit be implemented by users in one step instead of several. For instance, if datasets in a collection have different group tags such as group:type:single and group:type:paired-end - a single rule can now be used to populate a column containing either single or paired-end. This will likely be the most common tagging operation with the Apply Rules tool and would require 3 rules without this change.

Drop use of startsWith in favor of indexOf for PhantomJS testing.
This should allow nesting and filtering from tags - including group tags.
Should make it a lot easier to nested and filter on group tag values.
Copy link
Member

@mvdbeek mvdbeek left a comment

Choose a reason for hiding this comment

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

Very nice, I like it!

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

Successfully merging this pull request may close these issues.

3 participants