http://mircwiki.rsna.org/api.php?action=feedcontributions&user=209.242.55.41&feedformat=atomMircWiki - User contributions [en]2024-03-19T03:11:09ZUser contributionsMediaWiki 1.35.5http://mircwiki.rsna.org/index.php?title=User_Role_Manager&diff=2275User Role Manager2006-09-20T11:23:49Z<p>209.242.55.41: </p>
<hr />
<div>The User Role Manager is an administrative tool for creating user accounts and assigning administrative roles. The intended audience for this article is MIRC system administrators.<br />
<br />
The User Role Manager (URM) is a simple page that allows you to create users and roles without having to directly edit the Tomcat/conf/tomcat-users.xml file.<br />
<br />
To access the URM, click the <b>User Role Manager</b> button on the admin page of any storage service on the server. All storage services on a server (e.g., a specific Tomcat instance) link to the same URM, and the URM manages all the users on the server. The URM page looks like this:<br />
<br />
[[Image:URM1.JPG]]<br />
<br />
* The left column is the username.<br />
* The right column is the user's password. The column is not listed because the page is sent in clear text and there is no sense drawing a hacker's attention. In a future release, the URM can be changed to use SSL.<br />
* The users listed are those that are currently in the tomcat-users.xml file.<br />
* The roles listed are those that are possessed by a current user or ones that appear in the entity definitions in the web.xml files of any of the storage services on the server.<br />
<br />
Roles and users are listed in alphabetical order, so when you add one, it won't necessarily appear at the bottom or on the right after you click the <b>Update</b> button.<br />
<br />
When the URM receives a post of the form, it updates the tomcat-users.xml file.<br />
* If there is any user with no assigned roles, the user is deleted from the list.<br />
* If there is any role with no assigned users, the role is deleted from the list (unless the role appears in a web.xml file of a storage service).<br />
* If any username is blank, the line in the form is not processed.<br />
<br />
You can use the URM to edit the spelling or change the password of any user.<br />
<br />
When you create a user, make sure to assign the user at least one role by clicking a checkbox in the row with the user’s name and password, and when you create a role, make sure it is assigned to at least one user; otherwise, when you click <b>Update</b>, the addition will not be processed.<br />
<br />
You can add one user and one role per click of the <b>Update</b> button.<br />
<br />
In sites running the Smart Memory Realm (all sites after MIRC release T28), the changes become effective within one minute.<br />
<br />
Parenthetical note to avoid confusion: When Tomcat is installed, it comes with several users and roles in the tomcat-users.xml file. They are examples to demonstrate the use of the Manager webapp. You can delete them, if you want, using the URM.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=MIRC_TCE_Export_Manager&diff=2273MIRC TCE Export Manager2006-09-18T14:00:23Z<p>209.242.55.41: </p>
<hr />
<div>ExportManager is an implementation of the [http://www.ihe.net IHE] Teaching Files and Clinical Trials (TCE) integration profile Export Manager actor. This article provides links to the ExportManager and ManifestGenerator programs. <br />
<br />
==ExportManager==<br />
<br />
The [http://mirc.rsna.org/ExportManager/ExportManager-installer.jar ExportManager installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. On a Windows platform, you can simply double-click the program. On other platforms, you can use the command: <b>java -jar ExportManager-installer.jar</b>. <br />
<br />
The installer will create a directory called <b>ExportManager</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ExportManager, run the <b>ExportManager.jar</b> file, using a command similar to the one you used to run the installer. <br />
<br />
When ExportManager first runs, its export function is disabled. The <b>Help</b> tab provides information for configuring the destination URL, all the other program parameters, and the anonymization scripts. <br />
<br />
In normal operation, the program runs unattended; however, for IHE Connectaton testing, it may be useful to monitor the Event Log and Queue Status, both of which can be viewed either by clicking the corresponding tab or by accessing the built-in HTTP server with a browser.<br />
<br />
If objects are received which cannot be anonymized or transmitted, they are moved to quarantine directories with corresponding names. For convenience, there is a DICOM file dump utility included in the Quarantine tab that displays the contents of any DICOM file. <br />
<br />
==ManifestGenerator==<br />
ManifestGenerator is a minimal test utility for constructing IHE TCE manifests referencing DICOM instances. ManifestGenerator does <b>not</b> create complete TCE manifests, however. It constructs manifests which contain only the necessary elements for an Export Manager that does not have to query for the instances. All the elements which are included are correct as defined by the TCE integration profile, but elements unnecessary for the purpose of testing the Export Manager are omitted. These manifests, therefore, will fail when tested by almost any validation program. <br />
<br />
The [http://mirc.rsna.org/ExportManager/ManifestGenerator-installer.jar ManifestGenerator installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. The installer will create a directory called <b>ManifestGenerator</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ManifestGenerator, run the <b>ManifestGenerator.jar</b> file. <br />
<br />
The program provides two tabs, one for selecting instances for inclusion in the manifest, and one for entering textual information. <br />
<br />
In the <b>Instance Selector</b> tab, click the <b>Open Directory</b> button to get a file chooser. Navigate to the directory containing the desired instances. Check or uncheck files to select or deselect instances for the manifest. All the instances must be in the same directory. As instances are selected, the right pane displays their DICOM elements. <br />
<br />
In the <b>Manifest Constructor</b> tab, enter whatever information you wish in the fields provided. The text pane at the bottom allows you to enter text data for the manifest. No testing of the entered information is done. Make certain that you insert a UID. No automatic UID generation is provided. <br />
<br />
When the <b>Save</b> button is clicked at the bottom of the <b>Manifest Constructor</b> tab, the program constructs a manifest and saves it in the same directory with the instances. Any selected instance files that do not parse are not included in the manifest. The manifest file is named <b>[UID].kos</b>. After the manifest is saved, the program then constructs a zip file containing the manifest and all the referenced instances. The zip file is named <b>[UID].kos.zip</b> and is stored in the same directory with the instances and the manifest. This zip file is a convenient way to package test sets, especially when combined with the use of the FileSender program.<br />
<br />
==FileSender==<br />
FileSender is a MIRC utility program that can transmit files using the DICOM, HTTP, and HTTPS protocols. For more information and access to the program, see [[FileSender]]. <br />
<br />
In the context of the ExportManager and ManifestGenerator programs, FileSender can transmit manifests and instances for testing. <br />
<br />
The program includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together all the zip files for individual manifests and their instances. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=Downloads&diff=2272Downloads2006-09-18T13:56:19Z<p>209.242.55.41: /* Other Components */</p>
<hr />
<div>=== Release Versions ===<br />
''These are the more stable releases of MIRC, recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCdocument.xml T28 Installation Instructions]''' - This document will guide you through the installation process.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer.jar T28 Full Installer]''' - This installer is required for new installations or for upgrades from releases before T27.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer-lite.jar T28 Lite Installer]''' - This can be used only if you are upgrading from T27 to T28. It is smaller than the full installer.<br />
<br />
* '''[[T28 Release Notes]]''' - New Features Added to this release<br />
<br />
=== Non-Release Versions ===<br />
''These versions contain all of the latest features, but have not been tested as heavily.''<br />
<br />
=== Other Components ===<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - A Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.<br />
* '''[[MIRC TCE Export Manager]]''' - The MIRC implementation of the IHE Teaching Files and Clinical Trials Export integration profile Export Manager actor.<br />
* '''[[DicomEditor]]''' - A utility program for viewing, anonymizing and editing DICOM image files.<br />
* '''[[FileSender]]''' - A file transmission utility that supports DICOM, HTTP, and HTTPS.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=DicomEditor&diff=2271DicomEditor2006-09-18T13:54:25Z<p>209.242.55.41: /* The Directory Tab */</p>
<hr />
<div>DicomEditor is a utility program for viewing, editing, and de-identifying DICOM images. It is written in Java and requires Java 1.5 and the JAI ImageIO tools to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used generally to modify DICOM images. <br />
<br />
==Installation==<br />
To use the program, download the [http://mirc.rsna.org/DicomEditor/DicomEditor-installer.jar installer] and run it. It will create a folder called <b>DicomEditor</b> and put the required files inside it. To launch the program, double-click the <b>DicomEditor.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
==The Directory Tab==<br />
The <b>Directory</b> tab displays a split pane with a <b>Director</b> pane on the left and a <b>Results</b> pane on the right. The <b>Directory</b> pane is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
Once a file or folder is selected in the left pane, clicking the <b>Anonymize</b> button in the footer bar of the right pane starts the de-identification process. The progress is shown in the <b>Results</b> pane. <br />
* If an individual file is selected in the <b>Directory</b> pane, that is the only file that is processed. <br />
* If a folder is selected and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then all the files in the folder are processed. <br />
* If a folder is selected and the checkbox is also checked, then the program processes the files in the folder and all its subfolders, walking the directory tree below the selected folder. Only files matching the specified extensions are processed. <br />
* If the <b>Change names of anonymized files</b> box is checked in the footer of the <b>Results</b> pane, the anonymized files are created with names ending in <b>-no-phi</b>. If the box is not checked, the files are overwritten with the processed results. When processing with the box checked, the anonymizer will not anonymize any file whose name ends in <b>-no-phi</b>.<br />
* If the <b>Use SOPIUID for name</b> box is checked in the footer of the <b>Results</b> pane, the anonymized files are created using their SOP Instance UIDs for the file names. This check box takes priority over the <b>Change names of anonymized files</b> box. If the file's name is already its SOP Instance UID, it is overwritten by the processed file.<br />
<br />
Certain other processing functions are provided in addition to anonymization:<br />
* <b>Fix DICOM</b> verifies the VR values of all the elements in the file, changing any VRs which do not match the DICOM Data Dictionary. <br />
* <b>Clear Preamble</b> overwrites the preambles of Part 10 files with all zeroes.<br />
* If the <b>Alt</b> key is held down while clicking the <b>Clear Preamble</b> button, the preambles and <b>DICM</b> identifiers are removed from any files that do not contain a file metainfo group (group 2).<br />
<br />
Duting processing, if the <b>Force IVR-LE Syntax</b> box is checked, the processed files are written with the Implicit Value Representation Little Endian transfer syntax.<br />
<br />
==The DICOM Viewer Tab==<br />
The <b>DICOM Viewer</b> tab displays a DICOM image along with its metadata. Certain elements in the metadata (most of the ones that are textual) are editable. <br />
<br />
To open a DICOM file, click the <b>Open</b> button and use the file chooser to navigate to the desired file. To close the currently open image, click the <b>Close</b> button. <br />
<br />
To edit an element, click its <b>(group,element)</b> designation. A dialog box will appear allowing you to change the value of the element. <br />
<br />
If you have made one or more changes to an image, the <b>Save</b> and <b>Save All</b> buttons will be enabled. <b>Save</b> only saves the changes made to the current image. <b>Save All</b> applies the changes to all the images with the same <b>StudyInstanceUID</b> in the current directory. <br />
<br />
An element name displayed in red is one that is referenced by a script that could cause the anonymizer to call its <b>quarantine</b> function and leave the image untouched. If you anonymize an image and the <b>Results</b> pane shows that the anonymizer called the quarantine function, look at the values in the red elements and see if there is something wrong. <br />
<br />
To save a JPEG version of the currently displayed image, click the <b>Save As JPEG</b> button. A dialog box will appear allowing you to specify the maximum width of the saved image. The actual width of the saved image will be the minimum of the width of the DICOM image and the maximum width you specify. The height will be scaled to maintain the aspect ratio.<br />
<br />
==The DICOM Anonymizer Tab==<br />
DicomEditor uses the MIRC anonymizer to process files. The processing for each individual DICOM element can be specified in the <b>DICOM Anonymizer</b> tab. For a description of the script language, see [[The MIRC DICOM Anonymizer]].<br />
<br />
==The Help Tab==<br />
The Help tab contains a list of all the script functions as a quick reference. <br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=DicomEditor&diff=2270DicomEditor2006-09-18T13:54:00Z<p>209.242.55.41: /* The Directory Tab */</p>
<hr />
<div>DicomEditor is a utility program for viewing, editing, and de-identifying DICOM images. It is written in Java and requires Java 1.5 and the JAI ImageIO tools to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used generally to modify DICOM images. <br />
<br />
==Installation==<br />
To use the program, download the [http://mirc.rsna.org/DicomEditor/DicomEditor-installer.jar installer] and run it. It will create a folder called <b>DicomEditor</b> and put the required files inside it. To launch the program, double-click the <b>DicomEditor.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
==The Directory Tab==<br />
The <b>Directory</b> tab displays a split pane with a <b>Director</b> pane on the left and a <b>Results</b> pane on the right. The <b>Directory</b> pane is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
Once a file or folder is selected in the left pane, clicking the <b>Anonymize</b> button in the footer bar of the right pane starts the de-identification process. The progress is shown in the <b>Results</b> pane. <br />
* If an individual file is selected in the <b>Directory</b> pane, that is the only file that is processed. <br />
* If a folder is selected and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then all the files in the folder are processed. <br />
* If a folder is selected and the checkbox is also checked, then the program processes the files in the folder and all its subfolders, walking the directory tree below the selected folder. Only files matching the specified extensions are processed. <br />
* If the <b>Change names of anonymized files</b> box is checked in the footer of the <b>Results</b> pane, the anonymized files are created with names ending in <b>-no-phi</b>. If the box is not checked, the files are overwritten with the processed results. When processing with the box checked, the anonymizer will not anonymize any file whose name ends in <b>-no-phi</b>.<br />
* If the <b>Use SOPIUID for name</b> box is checked in the footer of the <b>Results</b> pane, the anonymized files are created using their SOP Instance UIDs for the file names. This check box takes priority over the <b>Change names of anonymized files</b> box. If the file's name is already its SOP Instance UID, it is overwritten by the processed file.<br />
<br />
Certain other processing functions are provided in addition to anonymization:<br />
* <b>Fix DICOM</b> verifies the VR values of all the elements in the file, changing any VRs which do not match the DICOM Data Dictionary. <br />
* <b>Clear Preamble</b> overwrites the preambles of Part 10 files with all zeroes.<br />
* If the Alt key is held down while clicking the <b>Clear Preamble</b> button, the preambles and <b>DICM</b> identifiers are removed from any files that do not contain a file metainfo group (group 2).<br />
<br />
Duting processing, if the <b>Force IVR-LE Syntax</b> box is checked, the processed files are written with the Implicit Value Representation Little Endian transfer syntax.<br />
<br />
==The DICOM Viewer Tab==<br />
The <b>DICOM Viewer</b> tab displays a DICOM image along with its metadata. Certain elements in the metadata (most of the ones that are textual) are editable. <br />
<br />
To open a DICOM file, click the <b>Open</b> button and use the file chooser to navigate to the desired file. To close the currently open image, click the <b>Close</b> button. <br />
<br />
To edit an element, click its <b>(group,element)</b> designation. A dialog box will appear allowing you to change the value of the element. <br />
<br />
If you have made one or more changes to an image, the <b>Save</b> and <b>Save All</b> buttons will be enabled. <b>Save</b> only saves the changes made to the current image. <b>Save All</b> applies the changes to all the images with the same <b>StudyInstanceUID</b> in the current directory. <br />
<br />
An element name displayed in red is one that is referenced by a script that could cause the anonymizer to call its <b>quarantine</b> function and leave the image untouched. If you anonymize an image and the <b>Results</b> pane shows that the anonymizer called the quarantine function, look at the values in the red elements and see if there is something wrong. <br />
<br />
To save a JPEG version of the currently displayed image, click the <b>Save As JPEG</b> button. A dialog box will appear allowing you to specify the maximum width of the saved image. The actual width of the saved image will be the minimum of the width of the DICOM image and the maximum width you specify. The height will be scaled to maintain the aspect ratio.<br />
<br />
==The DICOM Anonymizer Tab==<br />
DicomEditor uses the MIRC anonymizer to process files. The processing for each individual DICOM element can be specified in the <b>DICOM Anonymizer</b> tab. For a description of the script language, see [[The MIRC DICOM Anonymizer]].<br />
<br />
==The Help Tab==<br />
The Help tab contains a list of all the script functions as a quick reference. <br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=DicomEditor&diff=2269DicomEditor2006-09-18T13:40:40Z<p>209.242.55.41: </p>
<hr />
<div>DicomEditor is a utility program for viewing, editing, and de-identifying DICOM images. It is written in Java and requires Java 1.5 and the JAI ImageIO tools to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used generally to modify DICOM images. <br />
<br />
==Installation==<br />
To use the program, download the [http://mirc.rsna.org/DicomEditor/DicomEditor-installer.jar installer] and run it. It will create a folder called <b>DicomEditor</b> and put the required files inside it. To launch the program, double-click the <b>DicomEditor.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
==The Directory Tab==<br />
The <b>Directory</b> tab displays a split pane with a <b>Director</b> pane on the left and a <b>Results</b> pane on the right. The <b>Directory</b> pane is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
Once a file or folder is selected in the left pane, clicking the <b>Anonymize</b> button in the footer bar of the right pane starts the de-identification process. The progress is shown in the <b>Results</b> pane. <br />
* If an individual file is selected in the <b>Directory</b> pane, that is the only file that is processed. <br />
* If a folder is selected and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then all the files in the folder are processed. <br />
* If a folder is selected and the checkbox is also checked, then the program processes the files in the folder and all its subfolders, walking the directory tree below the selected folder. Only files matching the specified extensions are processed. <br />
* If the <b>Change names of anonymized files</b> box is checked in the footer of the Results pane, the anonymized files are created with names ending in <b>-no-phi</b>. If the box is not checked, the files are overwritten with the processed results. When processing with the box checked, the anonymizer will not anonymize any file whose name ends in <b>-no-phi</b>. <br />
<br />
==The DICOM Viewer Tab==<br />
The <b>DICOM Viewer</b> tab displays a DICOM image along with its metadata. Certain elements in the metadata (most of the ones that are textual) are editable. <br />
<br />
To open a DICOM file, click the <b>Open</b> button and use the file chooser to navigate to the desired file. To close the currently open image, click the <b>Close</b> button. <br />
<br />
To edit an element, click its <b>(group,element)</b> designation. A dialog box will appear allowing you to change the value of the element. <br />
<br />
If you have made one or more changes to an image, the <b>Save</b> and <b>Save All</b> buttons will be enabled. <b>Save</b> only saves the changes made to the current image. <b>Save All</b> applies the changes to all the images with the same <b>StudyInstanceUID</b> in the current directory. <br />
<br />
An element name displayed in red is one that is referenced by a script that could cause the anonymizer to call its <b>quarantine</b> function and leave the image untouched. If you anonymize an image and the <b>Results</b> pane shows that the anonymizer called the quarantine function, look at the values in the red elements and see if there is something wrong. <br />
<br />
To save a JPEG version of the currently displayed image, click the <b>Save As JPEG</b> button. A dialog box will appear allowing you to specify the maximum width of the saved image. The actual width of the saved image will be the minimum of the width of the DICOM image and the maximum width you specify. The height will be scaled to maintain the aspect ratio.<br />
<br />
==The DICOM Anonymizer Tab==<br />
DicomEditor uses the MIRC anonymizer to process files. The processing for each individual DICOM element can be specified in the <b>DICOM Anonymizer</b> tab. For a description of the script language, see [[The MIRC DICOM Anonymizer]].<br />
<br />
==The Help Tab==<br />
The Help tab contains a list of all the script functions as a quick reference. <br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=DicomEditor&diff=2268DicomEditor2006-09-18T13:40:09Z<p>209.242.55.41: /* The DICOM Anonymizer Tab */</p>
<hr />
<div>DicomEditor is a utility program for viewing, editing, and de-identifying DICOM images. It is written in Java and requires Java 1.5 and the JAI ImageIO tools to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used generally to modify DICOM images. <br />
<br />
==Installation==<br />
To use the program, download the [http://mirc.rsna.org/DicomEditor/DicomEditor-installer.jar installer] and run it. It will create a folder called <b>DicomEditor</b> and put the required files inside it. To launch the program, double-click the <b>DicomEditor.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
==The Directory Tab==<br />
The <b>Directory</b> tab displays a split pane with a <b>Director</b> pane on the left and a <b>Results</b> pane on the right. The <b>Directory</b> pane is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
Once a file or folder is selected in the left pane, clicking the <b>Anonymize</b> button in the footer bar of the right pane starts the de-identification process. The progress is shown in the <b>Results</b> pane. <br />
* If an individual file is selected in the <b>Directory</b> pane, that is the only file that is processed. <br />
* If a folder is selected and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then all the files in the folder are processed. <br />
* If a folder is selected and the checkbox is also checked, then the program processes the files in the folder and all its subfolders, walking the directory tree below the selected folder. Only files matching the specified extensions are processed. <br />
* If the <b>Change names of anonymized files</b> box is checked in the footer of the Results pane, the anonymized files are created with names ending in <b>-no-phi</b>. If the box is not checked, the files are overwritten with the processed results. When processing with the box checked, the anonymizer will not anonymize any file whose name ends in <b>-no-phi</b>. <br />
<br />
==The DICOM Viewer Tab==<br />
The <b>DICOM Viewer</b> tab displays a DICOM image along with its metadata. Certain elements in the metadata (most of the ones that are textual) are editable. <br />
<br />
To open a DICOM file, click the <b>Open</b> button and use the file chooser to navigate to the desired file. To close the currently open image, click the <b>Close</b> button. <br />
<br />
To edit an element, click its <b>(group,element)</b> designation. A dialog box will appear allowing you to change the value of the element. <br />
<br />
If you have made one or more changes to an image, the <b>Save</b> and <b>Save All</b> buttons will be enabled. <b>Save</b> only saves the changes made to the current image. <b>Save All</b> applies the changes to all the images with the same <b>StudyInstanceUID</b> in the current directory. <br />
<br />
An element name displayed in red is one that is referenced by a script that could cause the anonymizer to call its <b>quarantine</b> function and leave the image untouched. If you anonymize an image and the <b>Results</b> pane shows that the anonymizer called the quarantine function, look at the values in the red elements and see if there is something wrong. <br />
<br />
To save a JPEG version of the currently displayed image, click the <b>Save As JPEG</b> button. A dialog box will appear allowing you to specify the maximum width of the saved image. The actual width of the saved image will be the minimum of the width of the DICOM image and the maximum width you specify. The height will be scaled to maintain the aspect ratio.<br />
<br />
==The DICOM Anonymizer Tab==<br />
DicomEditor uses the MIRC anonymizer to process files. The processing for each individual DICOM element can be specified in the <b>DICOM Anonymizer</b> tab. For a description of the script language, see [[The MIRC Anonymizer]].<br />
<br />
==The Help Tab==<br />
The Help tab contains a list of all the script functions as a quick reference. <br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=DicomEditor&diff=2267DicomEditor2006-09-18T13:39:48Z<p>209.242.55.41: /* The DICOM Viewer Tab */</p>
<hr />
<div>DicomEditor is a utility program for viewing, editing, and de-identifying DICOM images. It is written in Java and requires Java 1.5 and the JAI ImageIO tools to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used generally to modify DICOM images. <br />
<br />
==Installation==<br />
To use the program, download the [http://mirc.rsna.org/DicomEditor/DicomEditor-installer.jar installer] and run it. It will create a folder called <b>DicomEditor</b> and put the required files inside it. To launch the program, double-click the <b>DicomEditor.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
==The Directory Tab==<br />
The <b>Directory</b> tab displays a split pane with a <b>Director</b> pane on the left and a <b>Results</b> pane on the right. The <b>Directory</b> pane is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
Once a file or folder is selected in the left pane, clicking the <b>Anonymize</b> button in the footer bar of the right pane starts the de-identification process. The progress is shown in the <b>Results</b> pane. <br />
* If an individual file is selected in the <b>Directory</b> pane, that is the only file that is processed. <br />
* If a folder is selected and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then all the files in the folder are processed. <br />
* If a folder is selected and the checkbox is also checked, then the program processes the files in the folder and all its subfolders, walking the directory tree below the selected folder. Only files matching the specified extensions are processed. <br />
* If the <b>Change names of anonymized files</b> box is checked in the footer of the Results pane, the anonymized files are created with names ending in <b>-no-phi</b>. If the box is not checked, the files are overwritten with the processed results. When processing with the box checked, the anonymizer will not anonymize any file whose name ends in <b>-no-phi</b>. <br />
<br />
==The DICOM Viewer Tab==<br />
The <b>DICOM Viewer</b> tab displays a DICOM image along with its metadata. Certain elements in the metadata (most of the ones that are textual) are editable. <br />
<br />
To open a DICOM file, click the <b>Open</b> button and use the file chooser to navigate to the desired file. To close the currently open image, click the <b>Close</b> button. <br />
<br />
To edit an element, click its <b>(group,element)</b> designation. A dialog box will appear allowing you to change the value of the element. <br />
<br />
If you have made one or more changes to an image, the <b>Save</b> and <b>Save All</b> buttons will be enabled. <b>Save</b> only saves the changes made to the current image. <b>Save All</b> applies the changes to all the images with the same <b>StudyInstanceUID</b> in the current directory. <br />
<br />
An element name displayed in red is one that is referenced by a script that could cause the anonymizer to call its <b>quarantine</b> function and leave the image untouched. If you anonymize an image and the <b>Results</b> pane shows that the anonymizer called the quarantine function, look at the values in the red elements and see if there is something wrong. <br />
<br />
To save a JPEG version of the currently displayed image, click the <b>Save As JPEG</b> button. A dialog box will appear allowing you to specify the maximum width of the saved image. The actual width of the saved image will be the minimum of the width of the DICOM image and the maximum width you specify. The height will be scaled to maintain the aspect ratio.<br />
<br />
==The DICOM Anonymizer Tab==<br />
DicomEditor uses the MIRC anonymizer to process files. The processing for each individual DICOM element can be specified in the <b>DICOM Anonymizer</b> tab. For a description of the script language, see [The MIRC Anonymizer].<br />
<br />
==The Help Tab==<br />
The Help tab contains a list of all the script functions as a quick reference. <br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=DicomEditor&diff=2266DicomEditor2006-09-18T13:39:15Z<p>209.242.55.41: </p>
<hr />
<div>DicomEditor is a utility program for viewing, editing, and de-identifying DICOM images. It is written in Java and requires Java 1.5 and the JAI ImageIO tools to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used generally to modify DICOM images. <br />
<br />
==Installation==<br />
To use the program, download the [http://mirc.rsna.org/DicomEditor/DicomEditor-installer.jar installer] and run it. It will create a folder called <b>DicomEditor</b> and put the required files inside it. To launch the program, double-click the <b>DicomEditor.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
==The Directory Tab==<br />
The <b>Directory</b> tab displays a split pane with a <b>Director</b> pane on the left and a <b>Results</b> pane on the right. The <b>Directory</b> pane is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
Once a file or folder is selected in the left pane, clicking the <b>Anonymize</b> button in the footer bar of the right pane starts the de-identification process. The progress is shown in the <b>Results</b> pane. <br />
* If an individual file is selected in the <b>Directory</b> pane, that is the only file that is processed. <br />
* If a folder is selected and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then all the files in the folder are processed. <br />
* If a folder is selected and the checkbox is also checked, then the program processes the files in the folder and all its subfolders, walking the directory tree below the selected folder. Only files matching the specified extensions are processed. <br />
* If the <b>Change names of anonymized files</b> box is checked in the footer of the Results pane, the anonymized files are created with names ending in <b>-no-phi</b>. If the box is not checked, the files are overwritten with the processed results. When processing with the box checked, the anonymizer will not anonymize any file whose name ends in <b>-no-phi</b>. <br />
<br />
==The DICOM Viewer Tab==<br />
The <b>DICOM Viewer</b> tab displays a DICOM image along with its metadata. Certain elements in the metadata (most of the ones that are textual) are editable. <br />
<br />
To open a DICOM file, click the <b>Open</b> button and use the file chooser to navigate to the desired file. To close the currently open image, click the <b>Close</b> button. <br />
<br />
To edit an element, click its <b>(group,element)</b> designation. A dialog box will appear allowing you to change the value of the element. <br />
<br />
If you have made one or more changes to an image, the <b>Save</b> and <b>Save All</b> buttons will be enabled. <b>Save</b> only saves the changes made to the current image. <b>Save All</b> applies the changes to all the images with the same <b>StudyInstanceUID</b> in the current directory. <br />
<br />
An element name displayed in red is one that is referenced by a script that could cause the anonymizer to call its <b>quarantine</b> function and leave the image untouched. If you anonymize an image and the <b>Results</b> pane shows that the anonymizer called the quarantine function, look at the values in the red elements and see if there is something wrong. <br />
<br />
To save a JPEG version of the currently displayed image, click the <b>Save As JPEG<b> button. A dialog box will appear allowing you to specify the maximum width of the saved image. The actual width of the saved image will be the minimum of the width of the DICOM image and the maximum width you specify. The height will be scaled to maintain the aspect ratio. <br />
<br />
==The DICOM Anonymizer Tab==<br />
DicomEditor uses the MIRC anonymizer to process files. The processing for each individual DICOM element can be specified in the <b>DICOM Anonymizer</b> tab. For a description of the script language, see [The MIRC Anonymizer].<br />
<br />
==The Help Tab==<br />
The Help tab contains a list of all the script functions as a quick reference. <br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=Downloads&diff=2265Downloads2006-09-18T13:12:19Z<p>209.242.55.41: /* Other Components */</p>
<hr />
<div>=== Release Versions ===<br />
''These are the more stable releases of MIRC, recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCdocument.xml T28 Installation Instructions]''' - This document will guide you through the installation process.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer.jar T28 Full Installer]''' - This installer is required for new installations or for upgrades from releases before T27.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer-lite.jar T28 Lite Installer]''' - This can be used only if you are upgrading from T27 to T28. It is smaller than the full installer.<br />
<br />
* '''[[T28 Release Notes]]''' - New Features Added to this release<br />
<br />
=== Non-Release Versions ===<br />
''These versions contain all of the latest features, but have not been tested as heavily.''<br />
<br />
=== Other Components ===<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - This is a Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.<br />
* '''[[FileSender]]''' - A file transmission utility that supports DICOM, HTTP, and HTTPS.<br />
* '''[[MIRC TCE Export Manager]]''' - The MIRC implementation of the IHE Teaching Files and Clinical Trials Export integration profile Export Manager actor.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=Downloads&diff=2264Downloads2006-09-18T13:11:58Z<p>209.242.55.41: </p>
<hr />
<div>=== Release Versions ===<br />
''These are the more stable releases of MIRC, recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCdocument.xml T28 Installation Instructions]''' - This document will guide you through the installation process.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer.jar T28 Full Installer]''' - This installer is required for new installations or for upgrades from releases before T27.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer-lite.jar T28 Lite Installer]''' - This can be used only if you are upgrading from T27 to T28. It is smaller than the full installer.<br />
<br />
* '''[[T28 Release Notes]]''' - New Features Added to this release<br />
<br />
=== Non-Release Versions ===<br />
''These versions contain all of the latest features, but have not been tested as heavily.''<br />
<br />
=== Other Components ===<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - This is a Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.<br />
* '''[[FileSender]]''' - A file transmission utility that supports DICOM, HTTP, and HTTPS.<br />
* '''[[MIR TCE Export Manager]]''' - The MIRC implementation of the IHE Teaching Files and Clinical Trials Export integration profile Export Manager actor.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=FileSender&diff=2263FileSender2006-09-18T13:00:34Z<p>209.242.55.41: </p>
<hr />
<div>FileSender is a utility program for sending files via HTTP or DICOM. It is written in Java and requires Java 1.5 or better to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used more generally to upload DICOM images to MIRC DICOM services or MIRCdocument zip files to MIRC storage services. It also uploads files to MIRC file services. <br />
<br />
==Instructions==<br />
To use the program, download the [http://mirc.rsna.org/FileSender/FileSender-installer.jar installer] and run it. It will create a folder called <b>FileSender</b> and put the required files inside it. To launch the program, double-click the <b>FileSender.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
The left pane in FileSender is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
The right pane is used to specify the destination URL. There are four example URLs in the header bar: <br />
<br />
* a typical transfer to the HttpImportService of a clinical trial service using HTTP <br />
* a typical transfer to the HttpImportService of a clinical trial service using secure sockets layer (HTTPS) <br />
* a typical transfer to a DicomImportService of a clinical trial service <br />
* a typical transfer to a MIRC Submit Service using HTTP <br />
<br />
FileSender supports secure sockets layer as well as standard HTTP. To use secure sockets layer, enter <b>https:</b> for the protocol in the URL rather than <b>http:</b>. You must also specify the proper port. If you are sending to a MIRC site, SSL is typically enabled on port <b>8443</b>. If you run into certificate problems with a MIRC site, see [[Configuring Tomcat to Support SSL]]. <br />
<br />
Once a file or folder is selected in the left pane and you have entered or selected a URL in the right pane and clicked its radio button to select it, clicking the <b>Send</b> button in the footer bar of the right pane starts the transmission. <br />
* If you selected an individual file in the left pane, that is all that is sent. <br />
* If you selected a folder and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then it just sends the files in the folder. <br />
* If you selected a folder and also checked the checkbox, then it sends the files in the folder and the files in all the subfolders, walking the entire tree below the selected folder. When sending the contents of a folder, only files matching the specified extensions are sent. <br />
<br />
FileSender includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together multiple zip files. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission. <br />
<br />
FileSender supports Content-Type setting based on the extension of the file being transmitted. This feature allows transmission of MIRCdocuments in the standard MIRC zip-file export format, defining the Content-Type as <b>application/x-zip-compressed</b> as required by MIRC Submit Services. <br />
* To allow FileSender to set the Content-Type from the extension, uncheck the <b>Force DICOM Content-Type</b> box in the footer of the right pane. <br />
* When using FileSender to transmit DICOM images via HTTP or HTTPS, however, be sure to check the <b>Force DICOM Content-Type</b> box. <br />
<br />
The program creates a preferences file and initializes itself to the last settings of the previous run. Each time you run it, it lists all the previous destination URLs and gives you another blank space to add a new one. You can edit, reuse, or erase any of the URLs. <br />
<br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=FileSender&diff=2262FileSender2006-09-18T12:59:05Z<p>209.242.55.41: </p>
<hr />
<div>FileSender is a utility program for sending files via HTTP or DICOM. It is written in Java and requires Java 1.5 or better to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used more generally to upload DICOM images to MIRC DICOM services or MIRCdocument zip files to MIRC storage services. It also uploads files to MIRC file services. <br />
<br />
==Instructions==<br />
To use the program, download the [http://mirc.rsna.org/FileSender/FileSender-installer.jar installer] and run it. It will create a folder called <b>FileSender</b> and put the required files inside it. To launch the program, double-click the <b>FileSender.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
The left pane in FileSender is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
The right pane is used to specify the destination URL. There are four example URLs in the header bar: <br />
<br />
* a typical transfer to the HttpImportService of a clinical trial service using HTTP <br />
* a typical transfer to the HttpImportService of a clinical trial service using secure sockets layer (HTTPS) <br />
* a typical transfer to a DicomImportService of a clinical trial service <br />
* a typical transfer to a MIRC Submit Service using HTTP <br />
<br />
Once a file or folder is selected in the left pane and you have entered or selected a URL in the right pane and clicked its radio button to select it, clicking the <b>Send</b> button in the footer bar of the right pane starts the transmission. <br />
* If you selected an individual file in the left pane, that is all that is sent. <br />
* If you selected a folder and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then it just sends the files in the folder. <br />
* If you selected a folder and also checked the checkbox, then it sends the files in the folder and the files in all the subfolders, walking the entire tree below the selected folder. When sending the contents of a folder, only files matching the specified extensions are sent. <br />
<br />
FileSender supports secure sockets layer as well as standard HTTP. To use secure sockets layer, enter <b>https:</b> for the protocol in the URL rather than <b>http:</b>. You must also specify the proper port. If you are sending to a MIRC site, SSL is typically enabled on port <b>8443</b>. If you run into certificate problems, see [[Configuring Tomcat to Support SSL]]. <br />
<br />
FileSender supports Content-Type setting based on the extension of the file being transmitted. This feature allows transmission of MIRCdocuments in the standard MIRC zip-file export format, defining the Content-Type as <b>application/x-zip-compressed</b> as required by MIRC Submit Services. <br />
* To allow FileSender to set the Content-Type from the extension, uncheck the <b>Force DICOM Content-Type</b> box in the footer of the right pane. <br />
* When using FileSender to transmit DICOM images via HTTP or HTTPS, however, be sure to check the <b>Force DICOM Content-Type</b> box. <br />
<br />
FileSender includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together multiple zip files. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission. <br />
<br />
The program creates a preferences file and initializes itself to the last settings of the previous run. Each time you run it, it lists all the previous destination URLs and gives you another blank space to add a new one. You can edit, reuse, or erase any of the URLs. <br />
<br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=FileSender&diff=2261FileSender2006-09-18T12:54:29Z<p>209.242.55.41: </p>
<hr />
<div>FileSender is a utility program for sending files via HTTP or DICOM. It is written in Java and requires Java 1.5 or better to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used more generally to upload DICOM images to MIRC DICOM services or MIRCdocument zip files to MIRC storage services. It also uploads files to MIRC file services. <br />
<br />
==Instructions==<br />
To use the program, download the [http://mirc.rsna.org/FileSender/FileSender-installer.jar installer] and run it. It will create a folder called <b>FileSender</b> and put the required files inside it. To launch the program, double-click the <b>FileSender.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
The left pane in FileSender is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
The right pane is used to specify the destination URL. There are four example URLs in the header bar: <br />
<br />
* a typical transfer to the HttpImportService of a clinical trial service using HTTP <br />
* a typical transfer to the HttpImportService of a clinical trial service using secure sockets layer (HTTPS) <br />
* a typical transfer to a DicomImportService of a clinical trial service <br />
* a typical transfer to a MIRC Submit Service using HTTP <br />
<br />
Once a file or folder is selected in the left pane and you have entered or selected a URL in the right pane and clicked its radio button to select it, clicking the <b>Send</b> button in the footer bar of the right pane starts the transmission. <br />
* If you selected an individual file in the left pane, that is all that is sent. <br />
* If you selected a folder and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then it just sends the files in the folder. <br />
* If you selected a folder and also checked the checkbox, then it sends the files in the folder and the files in all the subfolders, walking the entire tree below the selected folder. When sending the contents of a folder, only files matching the specified extensions are sent. <br />
<br />
FileSender supports secure sockets layer as well as standard HTTP. To use secure sockets layer, enter <b>https:</b> for the protocol in the URL rather than <b>http:</b>. You must also specify the proper port. If you are sending to a MIRC site, SSL is typically enabled on port <b>8443</b>. If you run into certificate problems, see [[Configuring Tomcat to Support SSL]]. <br />
<br />
FileSender supports Content-Type setting based on the extension of the file being transmitted. This feature allows transmission of MIRCdocuments in the standard MIRC zip-file export format, defining the Content-Type as <b>application/x-zip-compressed</b> as required by MIRC Submit Services. <br />
* To allow FileSender to set the Content-Type from the extension, uncheck the <b>Force DICOM Content-Type</b> box in the footer of the right pane. <br />
* When using FileSender to transmit DICOM images via HTTP or HTTPS, however, be sure to check the <b>Force DICOM Content-Type</b> box. <br />
<br />
The program creates a preferences file and initializes itself to the last settings of the previous run. Each time you run it, it lists all the previous destination URLs and gives you another blank space to add a new one. You can edit, reuse, or erase any of the URLs. <br />
<br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=FileSender&diff=2260FileSender2006-09-18T12:53:06Z<p>209.242.55.41: </p>
<hr />
<div>FileSender is a utility program for sending files via HTTP or DICOM. It is written in Java and requires Java 1.5 or better to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used more generally to upload DICOM images to MIRC DICOM services or MIRCdocument zip files to MIRC storage services. It also uploads files to MIRC file services. <br />
<br />
<b>Instructions</b><br />
To use the program, download the [http://mirc.rsna.org/FileSender/FileSender-installer.jar installer] and run it. It will create a folder called <b>FileSender</b> and put the required files inside it. To launch the program, double-click the <b>FileSender.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
The left pane in FileSender is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
The right pane is used to specify the destination URL. There are four example URLs in the header bar: <br />
<br />
* a typical transfer to the HttpImportService of a clinical trial service using HTTP <br />
* a typical transfer to the HttpImportService of a clinical trial service using secure sockets layer (HTTPS) <br />
* a typical transfer to a DicomImportService of a clinical trial service <br />
* a typical transfer to a MIRC Submit Service using HTTP <br />
<br />
Once a file or folder is selected in the left pane and you have entered or selected a URL in the right pane and clicked its radio button to select it, clicking the <b>Send</b> button in the footer bar of the right pane starts the transmission. <br />
* If you selected an individual file in the left pane, that is all that is sent. <br />
* If you selected a folder and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then it just sends the files in the folder. <br />
* If you selected a folder and also checked the checkbox, then it sends the files in the folder and the files in all the subfolders, walking the entire tree below the selected folder. When sending the contents of a folder, only files matching the specified extensions are sent. <br />
<br />
FileSender supports secure sockets layer as well as standard HTTP. To use secure sockets layer, enter <b>https:</b> for the protocol in the URL rather than <b>http:</b>. You must also specify the proper port. If you are sending to a MIRC site, SSL is typically enabled on port <b>8443</b>. If you run into certificate problems, see "How to Enable Secure Communication for MIRC Clinical Trial Services", on the RSNA MIRC site. <br />
<br />
FileSender supports Content-Type setting based on the extension of the file being transmitted. This feature allows transmission of MIRCdocuments in the standard MIRC zip-file export format, defining the Content-Type as <b>application/x-zip-compressed</b> as required by MIRC Submit Services. <br />
* To allow FileSender to set the Content-Type from the extension, uncheck the <b>Force DICOM Content-Type</b> box in the footer of the right pane. <br />
* When using FileSender to transmit DICOM images via HTTP or HTTPS, however, be sure to check the <b>Force DICOM Content-Type</b> box. <br />
<br />
The program creates a preferences file and initializes itself to the last settings of the previous run. Each time you run it, it lists all the previous destination URLs and gives you another blank space to add a new one. You can edit, reuse, or erase any of the URLs. <br />
<br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=FileSender&diff=2259FileSender2006-09-18T12:51:06Z<p>209.242.55.41: </p>
<hr />
<div>FileSender is a utility program for sending files via HTTP or DICOM. It is written in Java and requires Java 1.5 or better to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used more generally to upload DICOM images to MIRC DICOM services or MIRCdocument zip files to MIRC storage services. It also uploads files to MIRC file services. <br />
<br />
<b>Instructions</b><br />
To use the program, download the [http://mirc.rsna.org/FileSender/FileSender-installer.jar installer] and run it. It will create a folder called <b>FileSender</b> and put the required files inside it. To launch the program, double-click the <b>FileSender.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
The left pane in FileSender is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
The right pane is used to specify the destination URL. There are four example URLs in the header bar: <br />
<br />
* a typical transfer to the HttpImportService of a clinical trial service using HTTP <br />
* a typical transfer to the HttpImportService of a clinical trial service using secure sockets layer (HTTPS) <br />
* a typical transfer to a DicomImportService of a clinical trial service <br />
* a typical transfer to a MIRC Submit Service using HTTP <br />
<br />
Once a file or folder is selected in the left pane and you have entered or selected a URL in the right pane and clicked its radio button to select it, clicking the <b>Send</b> button in the footer bar of the right pane starts the transmission. <br />
<br />
If you selected an individual file in the left pane, that is all that is sent. If you selected a folder and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then it just sends the files in the folder. If you selected a folder and also checked the checkbox, then it sends the files in the folder and the files in all the subfolders, walking the entire tree below the selected folder. When sending the contents of a folder, only files matching the specified extensions are sent. <br />
<br />
FileSender supports secure sockets layer as well as standard HTTP. To use secure sockets layer, enter <b>https:</b> for the protocol in the URL rather than <b>http:</b>. You must also specify the proper port. If you are sending to a MIRC site, SSL is typically enabled on port <b>8443</b>. If you run into certificate problems, see "How to Enable Secure Communication for MIRC Clinical Trial Services", on the RSNA MIRC site. <br />
<br />
FileSender supports Content-Type setting based on the extension of the file being transmitted. This feature allows transmission of MIRCdocuments in the standard MIRC zip-file export format, defining the Content-Type as <b>application/x-zip-compressed</b> as required by MIRC Submit Services. <br />
* To allow FileSender to set the Content-Type from the extension, uncheck the <b>Force DICOM Content-Type</b> box in the footer of the right pane. <br />
* When using FileSender to transmit DICOM images via HTTP or HTTPS, however, be sure to check the <b>Force DICOM Content-Type</b> box. <br />
<br />
The program creates a preferences file and initializes itself to the last settings of the previous run. Each time you run it, it lists all the previous destination URLs and gives you another blank space to add a new one. You can edit, reuse, or erase any of the URLs. <br />
<br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=FileSender&diff=2258FileSender2006-09-18T12:50:35Z<p>209.242.55.41: </p>
<hr />
<div>FileSender is a utility program for sending files via HTTP or DICOM. It is written in Java and requires Java 1.5 or better to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used more generally to upload DICOM images to MIRC DICOM services or MIRCdocument zip files to MIRC storage services. It also uploads files to MIRC file services. <br />
<br />
<b>Instructions</b><br />
To use the program, download the [http://mirc.rsna.org/FileSender/FileSender-installer.jar installer] and run it. It will create a folder called <b>FileSender</b> and put the required files inside it. To launch the program, double-click the <b>FileSender.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
The left pane in FileSender is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
The right pane is used to specify the destination URL. There are four example URLs in the header bar: <br />
<br />
* a typical transfer to the HttpImportService of a clinical trial service using HTTP <br />
* a typical transfer to the HttpImportService of a clinical trial service using secure sockets layer (HTTPS) <br />
* a typical transfer to a DicomImportService of a clinical trial service <br />
* a typical transfer to a MIRC Submit Service using HTTP <br />
<br />
Once a file or folder is selected in the left pane and you have entered or selected a URL in the right pane and clicked its radio button to select it, clicking the <b>Send</b> button in the footer bar of the right pane starts the transmission. <br />
<br />
If you selected an individual file in the left pane, that is all that is sent. If you selected a folder and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then it just sends the files in the folder. If you selected a folder and also checked the checkbox, then it sends the files in the folder and the files in all the subfolders, walking the entire tree below the selected folder. When sending the contents of a folder, only files matching the specified extensions are sent. <br />
<br />
FileSender supports secure sockets layer as well as standard HTTP. To use secure sockets layer, enter <b>https:</b> for the protocol in the URL rather than <b>http:</b>. You must also specify the proper port. If you are sending to a MIRC site, SSL is typically enabled on port <b>8443</b>. If you run into certificate problems, see "How to Enable Secure Communication for MIRC Clinical Trial Services", on the RSNA MIRC site. <br />
<br />
FileSender supports Content-Type setting based on the extension of the file being transmitted. This feature allows transmission of MIRCdocuments in the standard MIRC zip-file export format, defining the Content-Type as <b>application/x-zip-compressed</b> as required by MIRC Submit Services. <br />
* To allow FileSender to set the Content-Type from the extension, uncheck the <b>Force DICOM Content-Type</b> box in the footer of the right pane. <br />
* When using FileSender to transmit DICOM images via HTTP or HTTPS, however, be sure to check the <b>Force DICOM Content-Type<b> box. <br />
<br />
The program creates a preferences file and initializes itself to the last settings of the previous run. Each time you run it, it lists all the previous destination URLs and gives you another blank space to add a new one. You can edit, reuse, or erase any of the URLs. <br />
<br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=MIRC_TCE_Export_Manager&diff=2257MIRC TCE Export Manager2006-09-18T11:44:42Z<p>209.242.55.41: /* ManifestGenerator */</p>
<hr />
<div>ExportManager is an implementation of the [http://www.ihe.net IHE] Teaching Files and Clinical Trials (TCE) Integration Profile Export Manager actor. This article provides links to the ExportManager and ManifestGenerator programs. <br />
<br />
==ExportManager==<br />
<br />
The [http://mirc.rsna.org/ExportManager/ExportManager-installer.jar ExportManager installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. On a Windows platform, you can simply double-click the program. On other platforms, you can use the command: <b>java -jar ExportManager-installer.jar</b>. <br />
<br />
The installer will create a directory called <b>ExportManager</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ExportManager, run the <b>ExportManager.jar</b> file, using a command similar to the one you used to run the installer. <br />
<br />
When ExportManager first runs, its export function is disabled. The <b>Help</b> tab provides information for configuring the destination URL, all the other program parameters, and the anonymization scripts. <br />
<br />
In normal operation, the program runs unattended; however, for IHE Connectaton testing, it may be useful to monitor the Event Log and Queue Status, both of which can be viewed either by clicking the corresponding tab or by accessing the built-in HTTP server with a browser.<br />
<br />
If objects are received which cannot be anonymized or transmitted, they are moved to quarantine directories with corresponding names. For convenience, there is a DICOM file dump utility included in the Quarantine tab that displays the contents of any DICOM file. <br />
<br />
==ManifestGenerator==<br />
ManifestGenerator is a minimal test utility for constructing IHE TCE manifests referencing DICOM instances. ManifestGenerator does <b>not</b> create complete TCE manifests, however. It constructs manifests which contain only the necessary elements for an Export Manager that does not have to query for the instances. All the elements which are included are correct as defined by the TCE integration profile, but elements unnecessary for the purpose of testing the Export Manager are omitted. These manifests, therefore, will fail when tested by almost any validation program. <br />
<br />
The [http://mirc.rsna.org/ExportManager/ManifestGenerator-installer.jar ManifestGenerator installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. The installer will create a directory called <b>ManifestGenerator</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ManifestGenerator, run the <b>ManifestGenerator.jar</b> file. <br />
<br />
The program provides two tabs, one for selecting instances for inclusion in the manifest, and one for entering textual information. <br />
<br />
In the <b>Instance Selector</b> tab, click the <b>Open Directory</b> button to get a file chooser. Navigate to the directory containing the desired instances. Check or uncheck files to select or deselect instances for the manifest. All the instances must be in the same directory. As instances are selected, the right pane displays their DICOM elements. <br />
<br />
In the <b>Manifest Constructor</b> tab, enter whatever information you wish in the fields provided. The text pane at the bottom allows you to enter text data for the manifest. No testing of the entered information is done. Make certain that you insert a UID. No automatic UID generation is provided. <br />
<br />
When the <b>Save</b> button is clicked at the bottom of the <b>Manifest Constructor</b> tab, the program constructs a manifest and saves it in the same directory with the instances. Any selected instance files that do not parse are not included in the manifest. The manifest file is named <b>[UID].kos</b>. After the manifest is saved, the program then constructs a zip file containing the manifest and all the referenced instances. The zip file is named <b>[UID].kos.zip</b> and is stored in the same directory with the instances and the manifest. This zip file is a convenient way to package test sets, especially when combined with the use of the FileSender program.<br />
<br />
==FileSender==<br />
FileSender is a MIRC utility program that can transmit files using the DICOM, HTTP, and HTTPS protocols. It is separately documented on the RSNA MIRC site. To find it on the site, do a search for <b>FileSender</b>. <br />
<br />
In the context of the ExportManager and ManifestGenerator programs, FileSender can transmit manifests and instances for testing. <br />
<br />
The program includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together all the zip files for individual manifests and their instances. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=MIRC_TCE_Export_Manager&diff=2256MIRC TCE Export Manager2006-09-18T11:43:58Z<p>209.242.55.41: /* ManifestGenerator */</p>
<hr />
<div>ExportManager is an implementation of the [http://www.ihe.net IHE] Teaching Files and Clinical Trials (TCE) Integration Profile Export Manager actor. This article provides links to the ExportManager and ManifestGenerator programs. <br />
<br />
==ExportManager==<br />
<br />
The [http://mirc.rsna.org/ExportManager/ExportManager-installer.jar ExportManager installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. On a Windows platform, you can simply double-click the program. On other platforms, you can use the command: <b>java -jar ExportManager-installer.jar</b>. <br />
<br />
The installer will create a directory called <b>ExportManager</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ExportManager, run the <b>ExportManager.jar</b> file, using a command similar to the one you used to run the installer. <br />
<br />
When ExportManager first runs, its export function is disabled. The <b>Help</b> tab provides information for configuring the destination URL, all the other program parameters, and the anonymization scripts. <br />
<br />
In normal operation, the program runs unattended; however, for IHE Connectaton testing, it may be useful to monitor the Event Log and Queue Status, both of which can be viewed either by clicking the corresponding tab or by accessing the built-in HTTP server with a browser.<br />
<br />
If objects are received which cannot be anonymized or transmitted, they are moved to quarantine directories with corresponding names. For convenience, there is a DICOM file dump utility included in the Quarantine tab that displays the contents of any DICOM file. <br />
<br />
==ManifestGenerator==<br />
ManifestGenerator is a minimal test utility for constructing IHE TCE manifests referencing DICOM instances. ManifestGenerator does <b>not</b> create complete TCE manifests, however. It constructs manifests which contain only the necessary elements for an Export Manager that does not have to query for the instances. All the elements which are included are correct as defined by the TCE integration profile, but elements unnecessary for the purpose of testing the Export Manager are omitted. These manifests, therefore, will fail when tested by almost any validation program. <br />
<br />
The [http://mirc.rsna.org/ExportManager/ManifestGenerator-installer.jar ManifestGenerator] installer can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. The installer will create a directory called <b>ManifestGenerator</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ManifestGenerator, run the <b>ManifestGenerator.jar</b> file. <br />
<br />
The program provides two tabs, one for selecting instances for inclusion in the manifest, and one for entering textual information. <br />
<br />
In the <b>Instance Selector</b> tab, click the <b>Open Directory</b> button to get a file chooser. Navigate to the directory containing the desired instances. Check or uncheck files to select or deselect instances for the manifest. All the instances must be in the same directory. As instances are selected, the right pane displays their DICOM elements. <br />
<br />
In the <b>Manifest Constructor</b> tab, enter whatever information you wish in the fields provided. The text pane at the bottom allows you to enter text data for the manifest. No testing of the entered information is done. Make certain that you insert a UID. No automatic UID generation is provided. <br />
<br />
When the <b>Save</b> button is clicked at the bottom of the <b>Manifest Constructor</b> tab, the program constructs a manifest and saves it in the same directory with the instances. Any selected instance files that do not parse are not included in the manifest. The manifest file is named <b>[UID].kos</b>. After the manifest is saved, the program then constructs a zip file containing the manifest and all the referenced instances. The zip file is named <b>[UID].kos.zip</b> and is stored in the same directory with the instances and the manifest. This zip file is a convenient way to package test sets, especially when combined with the use of the FileSender program.<br />
<br />
==FileSender==<br />
FileSender is a MIRC utility program that can transmit files using the DICOM, HTTP, and HTTPS protocols. It is separately documented on the RSNA MIRC site. To find it on the site, do a search for <b>FileSender</b>. <br />
<br />
In the context of the ExportManager and ManifestGenerator programs, FileSender can transmit manifests and instances for testing. <br />
<br />
The program includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together all the zip files for individual manifests and their instances. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=MIRC_TCE_Export_Manager&diff=2255MIRC TCE Export Manager2006-09-18T11:43:12Z<p>209.242.55.41: </p>
<hr />
<div>ExportManager is an implementation of the [http://www.ihe.net IHE] Teaching Files and Clinical Trials (TCE) Integration Profile Export Manager actor. This article provides links to the ExportManager and ManifestGenerator programs. <br />
<br />
==ExportManager==<br />
<br />
The [http://mirc.rsna.org/ExportManager/ExportManager-installer.jar ExportManager installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. On a Windows platform, you can simply double-click the program. On other platforms, you can use the command: <b>java -jar ExportManager-installer.jar</b>. <br />
<br />
The installer will create a directory called <b>ExportManager</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ExportManager, run the <b>ExportManager.jar</b> file, using a command similar to the one you used to run the installer. <br />
<br />
When ExportManager first runs, its export function is disabled. The <b>Help</b> tab provides information for configuring the destination URL, all the other program parameters, and the anonymization scripts. <br />
<br />
In normal operation, the program runs unattended; however, for IHE Connectaton testing, it may be useful to monitor the Event Log and Queue Status, both of which can be viewed either by clicking the corresponding tab or by accessing the built-in HTTP server with a browser.<br />
<br />
If objects are received which cannot be anonymized or transmitted, they are moved to quarantine directories with corresponding names. For convenience, there is a DICOM file dump utility included in the Quarantine tab that displays the contents of any DICOM file. <br />
<br />
==ManifestGenerator==<br />
ManifestGenerator is a minimal test utility for constructing IHE TCE manifests referencing DICOM instances. ManaifestGenerator does <b>not</b> create complete TCE manifests, however. It constructs manifests which contain only the necessary elements for an Export Manager that does not have to query for the instances. All the elements which are included are correct as defined by the TCE integration profile, but elements unnecessary for the purpose of testing the Export Manager are omitted. These manifests, therefore, will fail when tested by almost any validation program. <br />
<br />
The [http://mirc.rsna.org/ExportManager/ManifestGenerator-installer.jar ManifestGenerator] installer can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. The installer will create a directory called <b>ManifestGenerator</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ManifestGenerator, run the <b>ManifestGenerator.jar</b> file. <br />
<br />
The program provides two tabs, one for selecting instances for inclusion in the manifest, and one for entering textual information. <br />
<br />
In the <b>Instance Selector</b> tab, click the <b>Open Directory</b> button to get a file chooser. Navigate to the directory containing the desired instances. Check or uncheck files to select or deselect instances for the manifest. All the instances must be in the same directory. As instances are selected, the right pane displays their DICOM elements. <br />
<br />
In the <b>Manifest Constructor</b> tab, enter whatever information you wish in the fields provided. The text pane at the bottom allows you to enter text data for the manifest. No testing of the entered information is done. Make certain that you insert a UID. No automatic UID generation is provided. <br />
<br />
When the <b>Save</b> button is clicked at the bottom of the <b>Manifest Constructor</b> tab, the program constructs a manifest and saves it in the same directory with the instances. Any selected instance files that do not parse are not included in the manifest. The manifest file is named <b>[UID].kos</b>. After the manifest is saved, the program then constructs a zip file containing the manifest and all the referenced instances. The zip file is named <b>[UID].kos.zip</b> and is stored in the same directory with the instances and the manifest. This zip file is a convenient way to package test sets, especially when combined with the use of the FileSender program. <br />
<br />
==FileSender==<br />
FileSender is a MIRC utility program that can transmit files using the DICOM, HTTP, and HTTPS protocols. It is separately documented on the RSNA MIRC site. To find it on the site, do a search for <b>FileSender</b>. <br />
<br />
In the context of the ExportManager and ManifestGenerator programs, FileSender can transmit manifests and instances for testing. <br />
<br />
The program includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together all the zip files for individual manifests and their instances. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=MIRC_TCE_Export_Manager&diff=2254MIRC TCE Export Manager2006-09-18T11:42:47Z<p>209.242.55.41: </p>
<hr />
<div>ExportManager is an implementation of the [http://www.ihe.net | IHE] Teaching Files and Clinical Trials (TCE) Integration Profile Export Manager actor. This article provides links to the ExportManager and ManifestGenerator programs. <br />
<br />
==ExportManager==<br />
<br />
The [http://mirc.rsna.org/ExportManager/ExportManager-installer.jar | ExportManager installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. On a Windows platform, you can simply double-click the program. On other platforms, you can use the command: <b>java -jar ExportManager-installer.jar</b>. <br />
<br />
The installer will create a directory called <b>ExportManager</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ExportManager, run the <b>ExportManager.jar</b> file, using a command similar to the one you used to run the installer. <br />
<br />
When ExportManager first runs, its export function is disabled. The <b>Help</b> tab provides information for configuring the destination URL, all the other program parameters, and the anonymization scripts. <br />
<br />
In normal operation, the program runs unattended; however, for IHE Connectaton testing, it may be useful to monitor the Event Log and Queue Status, both of which can be viewed either by clicking the corresponding tab or by accessing the built-in HTTP server with a browser.<br />
<br />
If objects are received which cannot be anonymized or transmitted, they are moved to quarantine directories with corresponding names. For convenience, there is a DICOM file dump utility included in the Quarantine tab that displays the contents of any DICOM file. <br />
<br />
==ManifestGenerator==<br />
ManifestGenerator is a minimal test utility for constructing IHE TCE manifests referencing DICOM instances. ManaifestGenerator does <b>not</b> create complete TCE manifests, however. It constructs manifests which contain only the necessary elements for an Export Manager that does not have to query for the instances. All the elements which are included are correct as defined by the TCE integration profile, but elements unnecessary for the purpose of testing the Export Manager are omitted. These manifests, therefore, will fail when tested by almost any validation program. <br />
<br />
The [http://mirc.rsna.org/ExportManager/ManifestGenerator-installer.jar | ManifestGenerator] installer can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. The installer will create a directory called <b>ManifestGenerator</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ManifestGenerator, run the <b>ManifestGenerator.jar</b> file. <br />
<br />
The program provides two tabs, one for selecting instances for inclusion in the manifest, and one for entering textual information. <br />
<br />
In the <b>Instance Selector</b> tab, click the <b>Open Directory</b> button to get a file chooser. Navigate to the directory containing the desired instances. Check or uncheck files to select or deselect instances for the manifest. All the instances must be in the same directory. As instances are selected, the right pane displays their DICOM elements. <br />
<br />
In the <b>Manifest Constructor</b> tab, enter whatever information you wish in the fields provided. The text pane at the bottom allows you to enter text data for the manifest. No testing of the entered information is done. Make certain that you insert a UID. No automatic UID generation is provided. <br />
<br />
When the <b>Save</b> button is clicked at the bottom of the <b>Manifest Constructor</b> tab, the program constructs a manifest and saves it in the same directory with the instances. Any selected instance files that do not parse are not included in the manifest. The manifest file is named <b>[UID].kos</b>. After the manifest is saved, the program then constructs a zip file containing the manifest and all the referenced instances. The zip file is named <b>[UID].kos.zip</b> and is stored in the same directory with the instances and the manifest. This zip file is a convenient way to package test sets, especially when combined with the use of the FileSender program. <br />
<br />
==FileSender==<br />
FileSender is a MIRC utility program that can transmit files using the DICOM, HTTP, and HTTPS protocols. It is separately documented on the RSNA MIRC site. To find it on the site, do a search for <b>FileSender</b>. <br />
<br />
In the context of the ExportManager and ManifestGenerator programs, FileSender can transmit manifests and instances for testing. <br />
<br />
The program includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together all the zip files for individual manifests and their instances. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=MIRC_TCE_Export_Manager&diff=2253MIRC TCE Export Manager2006-09-18T11:42:03Z<p>209.242.55.41: </p>
<hr />
<div>ExportManager is an implementation of the [[http://www.ihe.net | IHE]] Teaching Files and Clinical Trials (TCE) Integration Profile Export Manager actor. This article provides links to the ExportManager and ManifestGenerator programs. <br />
<br />
==ExportManager==<br />
<br />
The [[http://mirc.rsna.org/ExportManager/ExportManager-installer.jar | ExportManager installer]] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. On a Windows platform, you can simply double-click the program. On other platforms, you can use the command: <b>java -jar ExportManager-installer.jar</b>. <br />
<br />
The installer will create a directory called <b>ExportManager</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ExportManager, run the <b>ExportManager.jar</b> file, using a command similar to the one you used to run the installer. <br />
<br />
When ExportManager first runs, its export function is disabled. The <b>Help</b> tab provides information for configuring the destination URL, all the other program parameters, and the anonymization scripts. <br />
<br />
In normal operation, the program runs unattended; however, for IHE Connectaton testing, it may be useful to monitor the Event Log and Queue Status, both of which can be viewed either by clicking the corresponding tab or by accessing the built-in HTTP server with a browser.<br />
<br />
If objects are received which cannot be anonymized or transmitted, they are moved to quarantine directories with corresponding names. For convenience, there is a DICOM file dump utility included in the Quarantine tab that displays the contents of any DICOM file. <br />
<br />
==ManifestGenerator==<br />
ManifestGenerator is a minimal test utility for constructing IHE TCE manifests referencing DICOM instances. ManaifestGenerator does <b>not</b> create complete TCE manifests, however. It constructs manifests which contain only the necessary elements for an Export Manager that does not have to query for the instances. All the elements which are included are correct as defined by the TCE integration profile, but elements unnecessary for the purpose of testing the Export Manager are omitted. These manifests, therefore, will fail when tested by almost any validation program. <br />
<br />
The [[http://mirc.rsna.org/ExportManager/ManifestGenerator-installer.jar | ManifestGenerator]] installer can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. The installer will create a directory called <b>ManifestGenerator</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ManifestGenerator, run the <b>ManifestGenerator.jar</b> file. <br />
<br />
The program provides two tabs, one for selecting instances for inclusion in the manifest, and one for entering textual information. <br />
<br />
In the <b>Instance Selector</b> tab, click the <b>Open Directory</b> button to get a file chooser. Navigate to the directory containing the desired instances. Check or uncheck files to select or deselect instances for the manifest. All the instances must be in the same directory. As instances are selected, the right pane displays their DICOM elements. <br />
<br />
In the <b>Manifest Constructor</b> tab, enter whatever information you wish in the fields provided. The text pane at the bottom allows you to enter text data for the manifest. No testing of the entered information is done. Make certain that you insert a UID. No automatic UID generation is provided. <br />
<br />
When the <b>Save</b> button is clicked at the bottom of the <b>Manifest Constructor</b> tab, the program constructs a manifest and saves it in the same directory with the instances. Any selected instance files that do not parse are not included in the manifest. The manifest file is named <b>[UID].kos</b>. After the manifest is saved, the program then constructs a zip file containing the manifest and all the referenced instances. The zip file is named <b>[UID].kos.zip</b> and is stored in the same directory with the instances and the manifest. This zip file is a convenient way to package test sets, especially when combined with the use of the FileSender program. <br />
<br />
==FileSender==<br />
FileSender is a MIRC utility program that can transmit files using the DICOM, HTTP, and HTTPS protocols. It is separately documented on the RSNA MIRC site. To find it on the site, do a search for <b>FileSender</b>. <br />
<br />
In the context of the ExportManager and ManifestGenerator programs, FileSender can transmit manifests and instances for testing. <br />
<br />
The program includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together all the zip files for individual manifests and their instances. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=MIRC_Powerpoint_Tool&diff=2252MIRC Powerpoint Tool2006-09-13T18:18:06Z<p>209.242.55.41: /* Installation */</p>
<hr />
<div>PPT2MIRC is a Powerpoint plug-in that saves a Powerpoint presentation as a MIRCdocument on a MIRC site, allowing the presentation to be found through normal MIRC queries. It was written by Scott Keller, based on work done by Prof. Amilcare Gentili of UCSD.<br />
<br />
PPT2MIRC creates a page-mode document containing standard MIRC elements (title, author, abstract, etc.), a link to the presentation itself, images of each of the slides, and an invisible section containing the text from all the slides and notes pages, allowing the presentation to be found by searching for any of the text on any of the slides or notes pages. The link to the presentation allows the user to retrieve the original Powerpoint presentation from the MIRC site. <br />
<br />
==Installation==<br />
After downloading [http://mirc.rsna.org/PPT2MIRC/PPT2MIRC.zip the Powerpoint Tool zip file], open the file and extract <b>PPT2MIRC.ppa</b>. <br />
<br />
Before it can be used, PPT2MIRC.ppa must be registered with Powerpoint as an add-in. The default location where Powerpoint looks for add-ins is <b>C:\Documents and Settings\USERNAME\Application Data\Microsoft\AddIns</b>, where <b>USERNAME</b> is to be replaced by your actual username.<br />
<br />
After placing the file in the AddIns directory, you must set the security level for macros and then enable the add-in. <br />
<br />
To set the security level:<br />
<br />
* Run Powerpoint.<br />
* In the menu bar, select <b>Tools / Options</b>.<br />
* In the Options dialog, click the <b>Security</b> tab.<br />
* Click the <b>Macro Security...</b> button.<br />
* In the Security dialog, click the <b>Security Level</b> tab.<br />
* Click the <b>Medium</b> radio button.<br />
* Click the <b>OK</b> button on the Security dialog.<br />
* Click the <b>OK</b> button on the Options dialog.<br />
<center><br />
[[Image:MIRC2PPTa.JPG]]<br />
[[Image:MIRC2PPTb.JPG]]<br />
</center><br />
[[Image:MIRC2PPTc.JPG|frame|]]<br />
<br />
<br />
To enable the add-in:<br />
<br />
* In the menu bar, select <b>Tools / Add-ins</b>.<br />
* In the Add-Ins dialog, check the <b>PPT2MIRC</b> box if it appears; otherwise, click the <b>Add New...</b> button and navigate to the <b>PPT2MIRC.ppa</b> file.<br />
* Click the <b>Close</b> button.<br />
<br />
[[Image:MIRC2PPT2.JPG|frame|]]<br />
<br />
==Operation==<br />
To use PPT2MIRC, open a presentation in Powerpoint. In the <b>Tools</b> menu, select <b>Convert to MIRC</b>. A window will be displayed as shown to the right.<br />
<br />
Set the MIRC Address field to point to the MIRC site to which you want to submit the MIRCdocument. The default setting points to a storage service named <b>storage</b> on a MIRC site running on your local computer (<b>localhost</b>) on port <b>8080</b>. Change these parameters as required. (If you aren't sure what the values should be, go to the query page for the site, click the <b>Submit Service</b> button, and look in the browser's address bar.) <br />
<br />
Next, fill in any of the fields you want. Pay special attention to these fields: <br />
<br />
*Set the title, author and abstract fields so that the MIRCdocument reflects the presentation when it is included in query results. <br />
*Make sure you put your MIRC username in the owner field. This is important to ensure that you will have control over the document when it is stored on the MIRC site. <br />
*Set the three access fields to determine whether others can read, update, or export the document. <br />
<br />
When you have set all the fields the way you want, click the <b>Send</b> button on the MIRC Address line. <br />
<br />
PPT2MIRC will then create the MIRCdocument and the images of the slides and then submit everything to the MIRC site. The result will be displayed in the results field of the window as shown. You can click the link in the results field to go directly to the MIRCdocument on the site.<br />
<br />
If you entered your MIRC username in the owner field, you will be able to edit the MIRCdocument through the author service on the MIRC site.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=MIRC_Powerpoint_Tool&diff=2251MIRC Powerpoint Tool2006-09-13T18:16:22Z<p>209.242.55.41: /* Installation */</p>
<hr />
<div>PPT2MIRC is a Powerpoint plug-in that saves a Powerpoint presentation as a MIRCdocument on a MIRC site, allowing the presentation to be found through normal MIRC queries. It was written by Scott Keller, based on work done by Prof. Amilcare Gentili of UCSD.<br />
<br />
PPT2MIRC creates a page-mode document containing standard MIRC elements (title, author, abstract, etc.), a link to the presentation itself, images of each of the slides, and an invisible section containing the text from all the slides and notes pages, allowing the presentation to be found by searching for any of the text on any of the slides or notes pages. The link to the presentation allows the user to retrieve the original Powerpoint presentation from the MIRC site. <br />
<br />
==Installation==<br />
After downloading [http://mirc.rsna.org/PPT2MIRC/PPT2MIRC.zip the Powerpoint Tool zip file], open the file and extract <b>PPT2MIRC.ppa</b>. <br />
<br />
Before it can be used, PPT2MIRC.ppa must be registered with Powerpoint as an add-in. The default location where Powerpoint looks for add-ins is <b>C:\Documents and Settings\USERNAME\Application Data\Microsoft\AddIns</b>, where <b>USERNAME</b> is to be replaced by your actual username.<br />
<br />
After placing the file in the AddIns directory, you must set the security level for macros and then enable the add-in. <br />
<br />
To set the security level:<br />
<br />
* Run Powerpoint.<br />
* In the menu bar, select <b>Tools / Options</b>.<br />
* In the Options dialog, click the <b>Security</b> tab.<br />
* Click the <b>Macro Security...</b> button.<br />
* In the Security dialog, click the <b>Security Level</b> tab.<br />
* Click the <b>Medium</b> radio button.<br />
* Click the <b>OK</b> button on the Security dialog.<br />
* Click the <b>OK</b> button on the Options dialog.<br />
<center><br />
[[Image:MIRC2PPTa.JPG]]<br />
[[Image:MIRC2PPTb.JPG]]<br />
</center><br />
[[Image:MIRC2PPTc.JPG|frame|]]<br />
<br />
<br />
To enable the add-in:<br />
<br />
* In the menu bar, select <b>Tools / Add-ins</b>.<br />
* In the Add-Ins dialog, check the <b>PPT2MIRC</b> box if it appears; otherwise, click the <b>Add New...</b> button and navigate to the PPT2MIRC.ppa file.<br />
* Click the <b>Close</b> button.<br />
<br />
[[Image:MIRC2PPT2.JPG|frame|]]<br />
<br />
==Operation==<br />
To use PPT2MIRC, open a presentation in Powerpoint. In the <b>Tools</b> menu, select <b>Convert to MIRC</b>. A window will be displayed as shown to the right.<br />
<br />
Set the MIRC Address field to point to the MIRC site to which you want to submit the MIRCdocument. The default setting points to a storage service named <b>storage</b> on a MIRC site running on your local computer (<b>localhost</b>) on port <b>8080</b>. Change these parameters as required. (If you aren't sure what the values should be, go to the query page for the site, click the <b>Submit Service</b> button, and look in the browser's address bar.) <br />
<br />
Next, fill in any of the fields you want. Pay special attention to these fields: <br />
<br />
*Set the title, author and abstract fields so that the MIRCdocument reflects the presentation when it is included in query results. <br />
*Make sure you put your MIRC username in the owner field. This is important to ensure that you will have control over the document when it is stored on the MIRC site. <br />
*Set the three access fields to determine whether others can read, update, or export the document. <br />
<br />
When you have set all the fields the way you want, click the <b>Send</b> button on the MIRC Address line. <br />
<br />
PPT2MIRC will then create the MIRCdocument and the images of the slides and then submit everything to the MIRC site. The result will be displayed in the results field of the window as shown. You can click the link in the results field to go directly to the MIRCdocument on the site.<br />
<br />
If you entered your MIRC username in the owner field, you will be able to edit the MIRCdocument through the author service on the MIRC site.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=Downloads&diff=2250Downloads2006-09-13T18:15:06Z<p>209.242.55.41: </p>
<hr />
<div>=== Release Versions ===<br />
''These are the more stable releases of MIRC, recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCdocument.xml T28 Installation Instructions]''' - This document will guide you through the installation process.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer.jar T28 Full Installer]''' - This installer is required for new installations or for upgrades from releases before T27.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer-lite.jar T28 Lite Installer]''' - This can be used only if you are upgrading from T27 to T28. It is smaller than the full installer.<br />
<br />
* '''[[T28 Release Notes]]''' - New Features Added to this release<br />
<br />
=== Non-Release Versions ===<br />
''These versions contain all of the latest features, but have not been tested as heavily.''<br />
<br />
=== Other Components ===<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - This is a Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.</div>209.242.55.41http://mircwiki.rsna.org/index.php?title=Downloads&diff=2249Downloads2006-09-13T18:14:00Z<p>209.242.55.41: </p>
<hr />
<div>=== Release Versions ===<br />
''These are the more stable releases of MIRC, recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCdocument.xml T28 Installation Instructions]''' - This document will guide you through the installation process.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer.jar T28 Full Installer]''' - This installer is required for new installations or for upgrades from releases before T27.<br />
<br />
* '''[http://mirc.rsna.org/mircstorage/documents/T28/MIRCsite-installer-lite.jar T28 Lite Installer]''' - This can be used only if you are upgrading from T27 to T28. It is smaller than the full installer.<br />
<br />
* '''[[T28 Release Notes]]''' - New Features Added to this release<br />
<br />
=== Non-Release Versions ===<br />
''These versions contain all of the latest features, but have not been tested as heavily.''<br />
<br />
=== Other Components ===<br />
''These are client-side tools.''<br />
<br />
* '''[[Powerpoint Tool]]''' - This is a Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.</div>209.242.55.41