Vanessasaurus

It's a totally different bootstrap table style for the viewer, and it affords the nice buttons and such that define the viewer. This is sort of inherent in the viewer...

Just a quick update on this - I've tried a few responsive frameworks, and can't get it working so far. I'm going to try [this one](https://callmecavs.github.io/layzr.js/) for whenever my next...

I can give a suggestion for a strategy to take - if you have very specific, scoped fields you want to keep, you can use the `KEEP` directive. If it's...

That sounds good to me. One question - is this something that should be implemented in upstream pydicom/pydicom? Akin to [remove private tags](https://github.com/pydicom/pydicom/blob/893609e1763044032ebee83d9fe563d8c9525012/src/pydicom/dataset.py#L2544) there might be a second function to...

My suggestion would be to turn the [tags.py module](https://github.com/pydicom/deid/blob/master/deid/dicom/tags.py) into a directory proper, e.g., tags.py to `tags/__init__.py` and then have a `private.py` with that explicit listing and function.

If you want to just create a deid recipe to keep the specific tags, no development is needed here. The first example you provided would be a way to achieve...

I've never used deid for private tags like that - going to ask @wetzelj for help on that one.

You'd want to put logic in the custom function, which will receive the item being parsed, the value, field and the entire dicom. A development tip is to write it...

Could you just not look at the VR in your custom function? The entire DICOM is passed in.

I would interact through python and put an IPython.embed() here and walk through the logic to understand what is going on (that is what I would try). https://github.com/pydicom/deid/blob/fa4731f79d7002d51e31cbec6f2586d87afb479d/deid/dicom/parser.py#L205 Also remember...