Skip to content

Normalize#75

Open
cbizon wants to merge 7 commits intomainfrom
normalize
Open

Normalize#75
cbizon wants to merge 7 commits intomainfrom
normalize

Conversation

@cbizon
Copy link
Collaborator

@cbizon cbizon commented Sep 6, 2022

Define the normalize nodes operation

@cbizon cbizon requested review from dkoslicki and finnagin September 6, 2022 16:48
@@ -0,0 +1,170 @@
{
Copy link
Member

Choose a reason for hiding this comment

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

Should this file be names something like 01_prenormalized_message.json instead of premerged?

@@ -0,0 +1,245 @@
{ "workflow": null,
Copy link
Member

Choose a reason for hiding this comment

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

Same with the name of this file

Copy link
Member

Choose a reason for hiding this comment

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

Should there be a hyphen here?

@@ -0,0 +1,15 @@
id: normalize_nodes
Copy link
Member

Choose a reason for hiding this comment

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

Let's make this a non-unique operation (so there is only one way to do the normalization)

@cbizon
Copy link
Collaborator Author

cbizon commented Sep 8, 2022

Thanks @dkoslicki . I've updated the filenames / dash.

I'm not sure how to designate unique/nonunique. I took a look at sort and some others that I thought should be nonunique and didn't see any kind of annotation there. Can you point me in the right direction?

@dkoslicki dkoslicki removed the request for review from finnagin September 8, 2022 16:34
@dkoslicki
Copy link
Member

Here's an example of the unique flag: https://github.com/NCATSTranslator/OperationsAndWorkflows/blob/main/operations/fill.yml#L4
I assume we should set this to unique=False, but @uhbrar can check me on that

@uhbrar
Copy link
Collaborator

uhbrar commented Sep 8, 2022

@dkoslicki is right. This should be tagged as unique=False, although it actually doesn't need to be tagged at all, since the default is False. The current operations schema dictates that only unique operations need to be tagged as unique. Non-unique operations can be tagged as non-unique, or can be left un-tagged.

Here's an example: https://github.com/NCATSTranslator/OperationsAndWorkflows/blob/main/operations/bind.yml

@cbizon
Copy link
Collaborator Author

cbizon commented Sep 8, 2022

Aha, explains why I didn't see unique in the places I was looking. I went ahead and added it explicitly to this one.

@uhbrar
Copy link
Collaborator

uhbrar commented Sep 8, 2022

That shouldn't be a problem. However, before this is merged, the schema needs to be rebuilt first. This is done through schema/build/generate_schema.py

@cbizon
Copy link
Collaborator Author

cbizon commented Sep 8, 2022

Oh right. I've also updated the README with a reminder on the process.

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.

3 participants

Comments