Releases: slicebox/slicebox
Manual series types
This release adds API calls for manually adding and removing series types for a series. UI controls for managing series types have been added to the home screen.
Forwarding bug fixed
This patch fixes a bug that caused the forwarding service to forward the wrong set of images (referencing the primary key of the table for ForwardingTransactionImage
s instead of the column of image ids).
A simpler API for the storage of data is also included which relies on exception handling instead of Option
s for communicating errors and which is slightly faster than the old version.
SCU decompression bug fixed
This patch fixes an issue where compressed (jpg) DICOM images were not decompressed when sending to a destination that only handles uncompressed data.
Better cleanup of temporary files
This patch fixes an issue where DICOM bulk data temporary files were accumulating over time in the system temp folder. We introduce a scheduled task for cleaning up such files every 6th hour.
DICOM conformance
This patch introduces a more strict policy for DICOM conformance. As before, slicebox is only accepting the basic imaging modalities when importing from PACS, directories or files, and also accepting secondary capture files when adding single images using the API (at /api/images
). In this release, we are also restricting the number associated transfer syntaxes, typically allowing the following four:
- Implicit VR little endian
- Explicit VR little endian
- Explicit VR big endian
- JPEG baseline process 1 (standard lossy JPEG)
Slicebox may allow further transfer syntaxes in the near future such as lossless JPEG, run-length encoded images and deflated datasets provided we find sample images and codec libraries with compatible licensing.
Box online status bug fix
Patch release that fixes a bug that made the online status of box connections to a public box not update properly.
Transaction error reporting
This release contains a number of minor bugfixes and adds more complete reporting of transaction errors when transferring images between boxes. If the transaction is reported as failed on one end, the failing box will now always attempt to report that error to the other box.
This release adds two new routes for reporting transactions errors, but is fully compatible with earlier 1.x releases.
Production-ready release 1.0
This is version 1.0
, the first production-ready release of slicebox. It packs a number of new features along with performance and UX enhancements. Among the major changes are
- A new system for importing images where imports are divided into sessions and each import session is identifiable as a series source
- Support for deployment on Amazon Web Services, using the Amazon Simple Storage Service (S3) for high-availability and capacity storage and the Amazon Relational Database Service as database
- Reworked RPM packaging
- Better traceability of how images move through the application from incoming to outgoing
- Better error handling when sending and receiving images.
- Faster handling of commands concerning many images, such as deleting and sending
- Increased test coverage
- An extensive user manual available through the project wiki
Enjoy!
Patch of release 0.12
This patch fixes a bug in the storage service where the ImageAdded event was not emitted when storing a jpeg image. This prevented forwarding from working correctly in such cases.
Upgraded anonymization service
This release adds a number of features to the anonymization service. Each anonymization key is now connected to the list of images it applies to. Anonymization keys can also be queried using a query API similar to that for DICOM meta data. Similar to the transactions view, the list of anonymization keys can be used to tag the corresponding series.