RetroBBS - comp.protocols.dicom - Leniency on storing?

Leniency on storing?

<c078c094-51bc-4cad-9ff8-d6b2e6cef2e4n@googlegroups.com>

https://www.rocksolidbbs.com/devel/article-flat.php?id=569&group=comp.protocols.dicom#569

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a37:a4e:0:b0:6ee:e739:965b with SMTP id 75-20020a370a4e000000b006eee739965bmr3022124qkk.612.1668714160495;
Thu, 17 Nov 2022 11:42:40 -0800 (PST)
X-Received: by 2002:a05:6808:f03:b0:359:e9f6:e379 with SMTP id
m3-20020a0568080f0300b00359e9f6e379mr1916082oiw.162.1668714160214; Thu, 17
Nov 2022 11:42:40 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Thu, 17 Nov 2022 11:42:39 -0800 (PST)
Injection-Info: google-groups.googlegroups.com; posting-host=71.212.161.138; posting-account=tXvHCgoAAACLy74BW0aiElHJRG_buLxY
NNTP-Posting-Host: 71.212.161.138
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c078c094-51bc-4cad-9ff8-d6b2e6cef2e4n@googlegroups.com>
Subject: Leniency on storing?
From: msesmada@gmail.com (Esmada Da)
Injection-Date: Thu, 17 Nov 2022 19:42:40 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2106

by: Esmada Da - Thu, 17 Nov 2022 19:42 UTC

Hello all,

The context on this is storing Dicom files already written by other devices..

I'm trying to store a Dicom binary along with its metadata extracted as JSON. We'll always store the binary as is, even if it has invalid data.
However, there are times when some attributes in the dictionary/ metadata won't parse based on a VR (example: invalid date format) or it won't parse as valid JSON at all. It may have unexpected escape characters, for example.

In such a case, is it better to omit the attribute and not store it at all and warn users? Or is it better to attempt to force storing even with invalid VR, as long as it has some semblance of JSON? Should we drop invalid characters to "force" JSON parsing and storage?

Bonus points if you know of other tools out there and how they handle these things.
I've seen conversations on here and, so far, it seems like it is best to be strict on write (for the originating device) and lenient on read/ further storing like for archival purposes.

Thank you for reading this far :)

Re: Leniency on storing?

<6c8caf6c-2c24-4cf2-97e8-7b76040e60a3n@googlegroups.com>

copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=570&group=comp.protocols.dicom#570

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:620a:10a2:b0:6e7:1224:7940 with SMTP id h2-20020a05620a10a200b006e712247940mr2742140qkk.35.1668714270632;
Thu, 17 Nov 2022 11:44:30 -0800 (PST)
X-Received: by 2002:a05:6808:20a2:b0:35b:740:7598 with SMTP id
s34-20020a05680820a200b0035b07407598mr4796946oiw.216.1668714270361; Thu, 17
Nov 2022 11:44:30 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Thu, 17 Nov 2022 11:44:30 -0800 (PST)
In-Reply-To: <c078c094-51bc-4cad-9ff8-d6b2e6cef2e4n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=71.212.161.138; posting-account=tXvHCgoAAACLy74BW0aiElHJRG_buLxY
NNTP-Posting-Host: 71.212.161.138
References: <c078c094-51bc-4cad-9ff8-d6b2e6cef2e4n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <6c8caf6c-2c24-4cf2-97e8-7b76040e60a3n@googlegroups.com>
Subject: Re: Leniency on storing?
From: msesmada@gmail.com (Esmada Da)
Injection-Date: Thu, 17 Nov 2022 19:44:30 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2447

by: Esmada Da - Thu, 17 Nov 2022 19:44 UTC

On Thursday, November 17, 2022 at 11:42:41 AM UTC-8, Esmada Da wrote:
> Hello all,
>
> The context on this is storing Dicom files already written by other devices.
>
> I'm trying to store a Dicom binary along with its metadata extracted as JSON. We'll always store the binary as is, even if it has invalid data.
> However, there are times when some attributes in the dictionary/ metadata won't parse based on a VR (example: invalid date format) or it won't parse as valid JSON at all. It may have unexpected escape characters, for example.
>
> In such a case, is it better to omit the attribute and not store it at all and warn users? Or is it better to attempt to force storing even with invalid VR, as long as it has some semblance of JSON? Should we drop invalid characters to "force" JSON parsing and storage?
>
> Bonus points if you know of other tools out there and how they handle these things.
> I've seen conversations on here and, so far, it seems like it is best to be strict on write (for the originating device) and lenient on read/ further storing like for archival purposes.
>
> Thank you for reading this far :)

In case it wasn't clear - I'm trying to enable STOW using DICOMWeb.

Beam me up, Scotty!

devel / comp.protocols.dicom / Leniency on storing?

Subject	Author
Leniency on storing?	Esmada Da
Re: Leniency on storing?	Esmada Da