Storage of identical instances

[Kirill K]

Hello.

I have a question. What dcm4chee-arc-light (5.16) do when it recieves same study (or instance) more than one time? And is there a way to influence its behavior?

Thank you.

[Kirill K]

Found some attribute "Overwrite Policy" but can't find the description how it works. I understand intuitively that this is somehow related to the rewriting of studies.

среда, 20 марта 2019 г., 12:10:20 UTC+3 пользователь Kirill K написал:

[Kirill K]

Still interested in additional information about this feature, can anyone suggest some documentation?

четверг, 21 марта 2019 г., 10:34:49 UTC+3 пользователь Kirill K написал:

[vrinda...@j4care.com]

There are 2 parts to your question here :
- Same object is sent to the archive again : With default configuration the Overwrite Policy on Archive Device level is set to SAME_SOURCE i.e if its from same source and MD5 sum is equal, then it is ignored. You can see this in the server.log as :
15:11:41,451 INFO  [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-7) DCM4CHEE<-STORESCU(4): Ignore received Instance[studyUID=1.2.276.0.24.438.38523304.4.0.1,seriesUID=1.3.46.670589.30.1.6.1.963335255131.1545983597001.1,objectUID=1.3.46.670589.30.1.6.1.963335255131.1545983596813.2] with equal digest

If you tried sending the same object from a different source, then also it is ignored with following message :
15:12:08,027 INFO  [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-9) DCM4CHEE<-STORESCU1(5): Ignore received Instance[studyUID=1.2.276.0.24.438.38523304.4.0.1,seriesUID=1.3.46.670589.30.1.6.1.963335255131.1545983597001.1,objectUID=1.3.46.670589.30.1.6.1.963335255131.1545983596813.2] from different source

- Additional instances of Study/Series sent to the archive : There are Attribute Filters (Child Object of Archive Device) defined for each entity (Patient/Study/Series) which have an Attribute Update Policy which specifies update policy for already extracted attributes of the entities in database.

[Kirill K]

My brain just melted. From same source is ignored and from different sources is also ignored. Looks like they ignored regardless of source. What is the meaning of the "same source" policy then?

Theres also SAME_SERIES and SAME_SOURCE_AND_SERIES, how do they work?

Do you have any indepth documenataion, so i can read it and not waste your time asking about all theese details?

вторник, 2 апреля 2019 г., 16:44:46 UTC+3 пользователь vrind...@j4care.com написал:

[Gunter Zeilinger]

If the MD5 sum matches with the previous received object, the object will be always ignored, independent of the configured Overwrite Policy. So there is currently no way to force to apply changed attribute filters by re-sending the objects. One workaround is to nullify `location.digest` by SQL for such objects, so there is no MD5SUM to compare.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.