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

additions we will probably need to storage api endpoint #18

Open
1 of 2 tasks
vsoch opened this issue Jun 20, 2017 · 0 comments
Open
1 of 2 tasks

additions we will probably need to storage api endpoint #18

vsoch opened this issue Jun 20, 2017 · 0 comments

Comments

@vsoch
Copy link
Owner

vsoch commented Jun 20, 2017

  • We need to decide on default permissions for objects, and have functions to define/ change, etc.
  • We also need an easy way to add metadata per image. This (functionally) is implemented, I'm just not sure about what is the best user flow. The goals would be:
  1. still use batch processing for uploads as much as possibl
  2. have the image metadata added at the same time created
  3. Not be (too annoying) for usage.

Option 1 is to have the user create the image, and then essentially do an image.update(fields=fields) for each. This is how it would be done, given coming back at a later date and updating the metadata. I don't like this for creation because, what if the user forgets? Mixes up stuff?

Option 2 is to let the user specify image / text fields based on another argument to the function for a dictionary lookup, eg:

images_fields = { "image1.dcm": [  {'Modality':"CT"}  ] }
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

No branches or pull requests

1 participant