-
Notifications
You must be signed in to change notification settings - Fork 32
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
populate metadata links file ann #152
populate metadata links file ann #152
Conversation
|
It looks like |
I was surprised by this at first it looks consistent to the introduction of the |
Does that commit need reverting, or some other fix? |
Reverting the commit will only apply to newly deployed devspace environment. In the case of the existing merge-ci devspace, I think you want to modify the default value of |
I do not remember why we added the |
For what it's worth, we will very soon no longer have a submodule in |
Coming back to the content of the PR:
We might need to discuss how this type of coupling should affect the semver of these two components. |
Certainly we shouldn't release the change in the script dialog ome/openmicroscopy#6096 before the script changes in this PR. There are a few places where we have a 'convention' on the naming of script Parameters. E.g. "Data_Type" and "IDs" for data input. These are quite simple convention so we haven't felt the need to define this API anywhere. The "File_Annotation" parameter is also understood by the webclient and can be auto-populated. I assumed File_Annotation would simply use the ID of a File_Annotation, but it has an additional requirement that the Annotation is linked to the Project/Screen for populate_metadata script. Perhaps we can test and merge this PR first, then consider ome/openmicroscopy#6096 Will that be enough to ensure that user don't get the webclient dialog changes before they get the script changes? cc @chris-allan |
Uploaded the script here manually onto merge-ci. The functionality works as described. |
Closing until #159 is merged to avoid conflicts... |
All works fine here. Tried the suggested table as well as my own, with double columns -> parade The unattached File is found via the ID as expected, and when one is attached there already, the script still runs as expected. Ready to merge FMPOV |
Maybe we should test on py3-ci though ? All the tests above were run on merge-ci |
Uploaded and tested on py3-ci today. Will list for testing there tomorrow (will need to upload script again first). Use https://py3-ci.openmicroscopy.org/web/webclient/?show=dataset-3120 (user-3). |
Tested on py3-ci, user-3 https://py3-ci.openmicroscopy.org/web/webclient/?show=dataset-2270 All good. Ready to merge. |
But that PR is excluded. Can you explain? |
ome/openmicroscopy#6096 requires this PR, so it is probably excluded until this one is merged, released etc. However, this PR doesn't require that one. |
This change is needed to allow populate_metadata script to work with the File-picker from ome/openmicroscopy#6096
That PR passes the uploaded FileAnnotation ID to populate-metadata script, but the script expects the FileAnnotation to be linked to the selected object.
This PR links the FileAnnotation to the object, which also has the benefit of not 'losing' the new FileAnnotation with it being unlinked.
To test: