You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was inevitable... now I'm finding a use case for adding a single employee id to jrc_author, namely, if the confidence score is so low that name_match.py rules them out, but I happen to know who it is. Example: 10.1101/2024.06.30.601394. It doesn't catch Miguel, but that is the desired behavior.
I could add this functionality to my name_match script, but it would probably make more sense to add it to your remove_jrc_author script, which would also need to be renamed.
If you need the user to specify the entire list with the new id included, to preserve order, that is very doable.
The text was updated successfully, but these errors were encountered:
Let's discuss this again. It may or may not be worth adding. My name match script does not add people to jrc_author if their location != Janelia. This leaves out some alumni we may wish to manually add.
This was inevitable... now I'm finding a use case for adding a single employee id to jrc_author, namely, if the confidence score is so low that name_match.py rules them out, but I happen to know who it is. Example: 10.1101/2024.06.30.601394. It doesn't catch Miguel, but that is the desired behavior.
I could add this functionality to my name_match script, but it would probably make more sense to add it to your remove_jrc_author script, which would also need to be renamed.
If you need the user to specify the entire list with the new id included, to preserve order, that is very doable.
The text was updated successfully, but these errors were encountered: