Difference between Archive and Local Storage

  • Hi


    I was reading the user manual yesterday and got a following query. I had setup a local storage and images are saved at the specified location. My question is how to define the ARCHIVE and when will images move to this archive. I mean what will trigger the images to move??


    --HM

  • Hi,


    MAG0 is the primary storage. You can move to MAG1..9 (to be defined in dicom.ini) etc. The two easy ways to move data are using the nightlymove option in the conquest GUI, or use command line tools.


    Marcel

  • Thanks for the feedback Marcel. Firstly, in nightlymove option do i have to define the MAG Storage limitation when studies will move or studies will move every night? Secondly, after the moves to the archive, can i zip the studies? and thirdly, the last can i some how increase the number of MAGs from 9 to n numbers. I have 87 projects and want to save initial data in MAG0 and then move them to separte MAGs. (guidance required in this step also.)


    --HM

  • Hi,


    1) If you have so many projects I would not use nightlymove, it is too limited. Use command line tools instead

    2) MAG stores remain live, so conquest reads them as well, zipping is therefore not possible

    You can zip individual patients for export from the command line or a script.

    3) The server core allows as many MAG devices as you like, but the GUI is limited to 10


    If you want that many storage locations, is MAG device the right mechanism? What do the projects represent?


    Marcel

  • HI Marcel


    Thanks for your prompt response. Please find my reply inline.


    1) If you have so many projects I would not use nightlymove, it is too limited. Use command line tools instead
    As i told you i have 87 sites at the moment that are connected with the Central PACS. If i configure NIGHTLYMOVE won't server move data to ARCHIVE?? If command line tools please guide.


    2) MAG stores remain live, so conquest reads them as well, zipping is therefore not possible

    You can zip individual patients for export from the command line or a script.

    3) The server core allows as many MAG devices as you like, but the GUI is limited to 10
    Server core??? Will you guide from where i can download this core based software? Will i be able to run Server Core option based on Windows. Guidelines required.


    If you want that many storage locations, is MAG device the right mechanism? What do the projects represent?

    Objective is to save each site data in a separate location. Project means sites that are sending data to us.



    --HM

  • Hi,


    you can manually edit to put as many MAGDevices in dicom.ini as you like for use of dgate.exe. But conquestdicomserver.exe will not display over MAGDevice 10. And beware not to save configuration from conquestdicomserver.exe, it will only keep the first 10.


    For your use I would make a list of AE titles to Magdevices translation. In dicom.ini:


    [lua]

    Association = list={AE1=0,AE2=1,AE3=2}

    ImportConverter0 = if list[Association.Calling] then script('storage MAG'..list[Association.Calling]) else script('storage MAG0') end


    This will allow mapping any sending system to a MAG device. So data it stored separate directly. For 87 systems though you may need to make a separate lua file, the 'Association' line would be too long. I.e.,


    Association = list={};dofile('loadlist.lua')


    Marcel

  • Thanks. I will give it a try but i think this will create a lua file that will be too hard for me to handle.


    I also asked about the conquestserver core can it be deployed on windows??? and from where to get it??


    --HM

  • Sorry I did not explain. The GUI is conquestdicomserver.exe (windows only), the core is dgate(64.exe) for windows and linux. Application dgatesrv.exe runs dgate64.exe as service on windows. So you can run fine on windows without GUI, using for instance the web interface to view data and manually editing dicom.ini for configuration.

  • Hi,

    sorry for possibly repetition question.

    How can I tell conquest to write new incoming oder new importing (for exampel via watchfolder) Images on anthoder MAG than MAG0 (because this will be full)?

    Is ther any way to chane the default MAG to store new images?


    with kind regard,

    jk

  • Hi,


    Try this:


    in dicom.ini make sure


    ImportExportDragAndDrop=1


    And add at the end:


    ImportConverter0 = ifequal "%u","CONQUESTSRV1";storage MAG2


    Explanation: %u is the calling AE, if it equals the name of the server the image comes in from the server itself.


    Marcel

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!