Follow

Evidence Data Export in LIMS-plus when Transferring to a Storage Location

LIMS-plus will allow users to transfer evidence items to a designated storage location which will trigger an export of the evidence data points in xml format. The application can either export the xml to a designated share folder or call a designated web service that can accept the xml. The application will also have a method to store xslt that will transform the standard xml into an alternate format to enable integration with most any other system. By default, the xml will be exported without transformation and the standard format is included in Appendix A. If an xslt script is required, the creation of that xslt will have to be done by the client or JusticeTrax can provide this service for a fee. There is no limitation to the number of storage locations that can be used for export.  (See pdf attachment for screenshots and sample xml data.)

IMPORTANT NOTE: This functionality is only available in the Evidence Transfer form, so the initial chain of custody form will not have this functionality. This is intended for the final transfer not an initial transfer.

STORAGE LOCATION ADMINISTRATION

To utilize this feature, in LIMS-plus, System Administration, Storage Areas, the LIMS-plus Administrator will designate a Storage Location as "This storage area is to be used as a transfer export." The checkboxes are not mutually exclusive so a storage location could be marked as a disposition and used for transfer export.

If this box is checked the Export tab fields will be available.

1. Export Unit – The LIMS-plus performs evidence transfers as a single transfer, no matter how many items are involved in the transfer. The application (or web service) that is receiving the exported items may not be able to accept the items within a single xml. So these options indicate whether to export the items within a single xml or separate each item and transfer them one at a time.

    a. Entire Transfer is a single export (Entire Transfer succeeds or fails as a single unit) – This is the method in which the LIMS-plus application performs transfers. All items are transferred within one transaction. If the export is using a web service and a failure message is returned, none of the items will be transferred and the user will be notified of that failure during transfer.

    b. Each Evidence Item is exported separately (some evidence may fail while others succeed) – This option allows the export to handle the transfer of the bulk evidence items as individual transfers. If the export is using a web service, the call will be made for each individual item and if a failure message is returned for any single item, that item will not be transferred and the user will be notified of that during the transfer. So, within a bulk transfer in LIMS-plus it is possible that some items will transfer successfully and some will not.

NOTE: Since this is NOT the way LIMS-plus performs transfers, the application must use the Broker service and transform the xml using the XSLT. If an XSLT is not provided and this option is selected, the application will notify the user that the XSLT is required and offer to input the default XSLT. The default XSLT can be found in Appendix B of this document.

2. Broker Service – In order to perform all the different variations of the export, the application utilizes a Broker web service to perform most of the functions. This is a separate installation from the LIMS-plus application.

    a. Requirements for the Broker web service installation:

        i. IIS 7 or better must be installed

        ii. WCF Activation must be enabled in IIS

        iii. See Appendix C for Screen shots of IIS Setup

    b. Once installed, the url for the web service is http://<insertservername>/Lims3.Services.Broker.PassThrough/ServiceBroker.svc

Example: http://gloin/Lims3.Services.Broker.PassThrough/ServiceBroker.svc

    c. Ensure that the website that is hosting the service is started.

    d. The only time the application does not require the Broker web service is under the following conditions:

        i. The export is to a File Path

        ii. The Entire Transfer is a single export (Entire Transfer succeeds or fails as a single unit) radio button is selected.

        iii. There is no XSLT transformation

3. Web Service – The application can perform an export by either calling a web service or exporting the xml to a folder on disk. If the export is to use a web service:

    a. The Broker web service must be installed

    b. The Broker Service url must be populated

    c. The Web service url must be populated

    d. You cannot have a File Path

4. XSLT – if a valid XSLT transformation script is copied into the XSLT field, the application will use this XSLT script to transform the default xml prior to export.

    a. The application does not require, but can use if needed, the XSLT when the Entire Transfer is a single export (Entire Transfer succeeds or fails as a single unit) radio button is selected.

    b. The application does require the XSLT when the Each Evidence Item is exported separately (some evidence may fail while others succeed) radio button is selected.

    c. If an XSLT is required but is not provided, the application will prompt the user to use the default XSLT.

 

USING THIS STORAGE LOCATION

Users will transfer the items as normal using the evidence transfer screen.

When the transfer is applied, the application will perform the export.

 

FAILURES

If the application uses a web service and that web service returns a failure, the user will be notified that the transfer could not take place at the time of transfer. These items will not be transferred and will remain in the original location.

1. If the Entire Transfer is a single export (Entire Transfer succeeds or fails as a single unit) radio button is selected on the export storage location, this indicates an "all or nothing" transfer. So, if the web service returns a failure or if the folder does not exist, none of the items will be transferred and the user will receive a message that "LIMS-plus encountered a problem exporting these evidence items and cannot record the transfer."  The user will be asked if he/she would like to try again.

The user can choose Retry and the application will try the web service again. If the user clicks Cancel, a message is presented that chain of custody information will not be recorded.

When the user clicks OK, he/she is taken back to the Transfer screen.

2. If the Each Evidence Item is exported separately (some evidence may fail while others succeed) radio button is selected, then some items may transfer successfully and some of the items may not. If the web service returns a failure for any one of the items, the user will receive a message that "LIMS-plus encountered a problem exporting one or more evidence items. Transfer information for successfully exported evidence items will be recorded."

When the user clicks OK, a message is presented indicating which items could not be transferred. The user will then have to determine why the external system could not transfer these items, fix those issues and transfer the items again.

 

APPENDIX A

The data provided in the xml will include:

 Case Agency Records

 Evidence Record

 Transfer Record – only for the transfer record to the designated storage area

 Firearms, Shotshell, Bullet/Cartridge Data

See an example xml in the attachment that is exported for 3 items: 1 is a firearm, 1 is a shotshell and 1 is a bullet.

 

APPENDIX C

See the screen shots in the attachment for IIS 7 that will allow the broker service to be installed and used. Note that the Windows Communication Foundation options are enabled.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

2 Comments

Please sign in to leave a comment.
Powered by Zendesk