-
Notifications
You must be signed in to change notification settings - Fork 163
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
[ENH] Microscopy: Add IntendedFor metadata field to photo files #1000
[ENH] Microscopy: Add IntendedFor metadata field to photo files #1000
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1000 +/- ##
==========================================
+ Coverage 70.16% 71.11% +0.94%
==========================================
Files 9 9
Lines 952 952
==========================================
+ Hits 668 677 +9
+ Misses 284 275 -9 ☔ View full report in Codecov by Sentry. |
while we are making changes to the json document, would there be some benefit to add the possibility of some field that describes details of acquisition. examples:
at the simplest level an optional |
This is kind of long-range, but it might be nice to place the photo in time with relation to the tissue protocol - somehow linking it to between two stages or after a stage. @satra is right about taking the photo before or after clearing - a huge difference in appearance and the intention of the photographer in picking the timing of the photo. I can imagine taking a picture of one of our slabs on the microscope stage would help us understand the orientation of the resulting image and other aspects. |
Great idea, thanks! I added a "PhotoDescription" field with example. |
I opened WIP PR for bids-examples (bids-standard/bids-examples#307) and bids-validator (https://github.com/bids-standard/bids-validator/pull/1415) associated with the changes. |
That's seems a good idea! indeed we usually take photos of the samples before and after clearing. These were also uploaded to DANDI |
Hi everyone, it's been a while! So this PR is ready for review again.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the other modalities where "_photo" is used as a suffix file apparently don't (yet?) allow .json sidecars, but I see no reason why it shouldn't be the case.
LGTM
@TheChymera I wanted to request you as a reviewer and then noticed that you are not yet part of the org, so I've sent you some invitations for that. Please check your inbox :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
closes #992
Dear BIDS community,
This PR address the issue in:
_photo
do not support a_run-
entity. #992... where there was no mechanism in microscopy to associated a photo of a sample to a specific run or modality (for example: a photo could be generated at each run). Our best option seems to be a JSON file associated to the photo with the
IntendedFor
metadata field, which I added in this PR.Link to the rendered doc: https://bids-specification--1000.org.readthedocs.build/en/1000/04-modality-specific-files/10-microscopy.html#photos-of-the-samples-_photoextension
Please let me know your thoughts and suggestions, thank you!
Note: If we go with this, we will need to update the bids-validator with the addition of the JSON file for photo and its associated rules.