Loris
Loris copied to clipboard
[API] Add Project endpoint "Dicoms"
Brief summary of changes
This Pull Request adds an endpoint at /projects/<project>/dicoms. It returns a complete list of DICOM files contained in a project (and other pertinent informations)
Testing instructions
Go to https://<hostname>/api/v0.0.3/projects/rye/dicoms in a browser. The page should return a JSON in a string with information on all DICOM contained in the project
Link(s) to related issue(s)
- Resolves #6774
@spell00 Is this PR up to date?
If so, @xlecours do you have time to review this? if not let me know and I'll find someone perhaps Cecile.
now I get {"Dicoms":{}}
when trying to access <host>/api/v0.0.3/projects/rye/dicoms
it is now working again, including the changes requested
@xlecours and @kongtiaowang - would you have a few minutes to (re)review this PR this week?
@spell00 this seems like a minor change request -- can you address it and move this forward today?
ok @christinerogers , I'll take care of it today
This new endpoint is not in the specs for v0.0.3, so the changes suggested in this PR need to be added to the API v0.0.4 initiated in PR #6944, which is in progress.
@spell00 is this ready for re-review? it's not clear if you're still working on resolving the comment you added.
@christinerogers It is ready for review.
Earlier, I was trying to point out that in the changed files, there is indications that I removed the last line in some files. I did not remove the last line and I can't get rid of the indication there is a change. I was trying to get things faster, I am expecting having a comment about these.
blocked by #7101
@xlecours @driusan It is now passing Travis and ready for final review
@xlecours can you take this PR over please? Thank you :)
@cmadjar it seems like @xlecours 's next to latest review approved the changes and asked you to take a second look at it. I think this one is also in your court in that case
from @xlecours
I wouldn't mind having @cmadjar backing on this. Are the properties of the Dicoms items ok?
@xlecours @cmadjar just rebased the PR
@xlecours this one is back in your court
@xlecours this one is in your court. Should be straightforward though?
This still needs work.
- The property names in the response should be case-consistent
- I think we should hide : CenterID, tarchiveid and Source since they are only meaningful from within the database of on the filesystem.
- There should be a link to the resource (where it can be downloaded)
- Documentation should be add in the api specification of the api module (schema.yml)
On a side note: could this be done using /dicom_archive instead?
@cmadjar assigning to you to bring up at Imaging meeting see if this is still needed
Discussed during the imaging call of Jul 4th. It is stale and needs work that will not be done in the short term.