Page Description

The Storage Transfer page provides the ability to place the metacontainer or samples in other metacontainers. This functionality is what allows a storage hierarchy to be built and storage and tracking to be done on samples.

This page can be entered from a Storage Transfer menu item under the Manage Samples menu. The transfer worklist contains all available samples and metacontainers marked as transferable. This list can be reduced using the filter or by building the list through manually selecting/scanning manifest, metacontainers, or sample IDs. It can also be entered from other pages where one or more samples or metacontainers can be selected and used to prepopulate the transfer worklist.

The destination will initially be blank when the page is first opened. After a destination is selected, the Transfer buttons on the worklist will appear on all containers that are eligible to be placed in the destination based on its Metacontainer Type definition (acceptable container types) and what other samples already exist in it (storage temperature and testing host). A special destination of Uncontained can be selected that will remove the transferred containers out of the storage hierarchy so they exist on their own. All samples and metacontainers will initially be uncontained until they are first transferred into another metacontainer.

For more help, click one of the following links:

• Accessing this Page
• Storage Transfer Worklist
• Storage Transfer Notes

Accessing this Page

• Click the Tasks menu, followed by the Manage Samples menu button, then click the Storage Transfer button.

[Return to Top]

Storage Transfer Worklist

1. This is the filter that limits what containers appear in the table. This filter is used to find specific metacontainers or samples based on the defined filter criteria or can also be used to build a worklist. If no filter criteria is defined, all non-disposed of metacontainers or samples are displayed in the table.
2. The filter contains the following filter fields:
   • Manifest/Order/Sample/Metacontainer ID:shows all samples that are contained within the identified object if a manifest, order, or metacontainer ID is entered.
   • Container Type: displays either the metacontainer or tube/container type.
3. The filter contains the following filter conditions:
   
   • Show Ancestors: shows all metacontainers that are above them in the storage hierarchy in addition to the metacontainers or samples that are returned by the filter criteria. This is selected by default.
   • Show Descendants: shows all metacontainers or samples that are below them in the storage hierarchy in addition to the metacontainers or samples returned by the filter criteria. This is selected by default.
4. The transfer worklist can be populated based on results from the defined filter criteria, from building the worklist manually, or come pre-populated from a previous page. As containers are transferred into their destination metacontainers from the worklist, they are removed from the worklist until the transfer process is saved.
5. Click Transfer to place the container from the worklist into the current position in the destination metacontainer. Only containers that are eligible to be placed in the destination will have the button available. This eligibility is based on the destination's Metacontainer Type definition (acceptable container types) and what other samples already exist in the destination (storage temperature and testing host). The current position in the destination metacontainer should automatically advance to the next available position in the destination metacontainer after clicking the button.
6. Use the Destination search field to search for all non-disposed of metacontainers. Once selected, the Transfer buttons on the eligible containers on the worklist appears. The destination metacontainter can be changed as needed while progressing through the worklist. This allows a worklist to be built, transfer half of the containers into one rack, and then transfer the other half into a different rack. All transfers will not commit until Save is clicked.
7. Click Create Metacontainers to create new metacontainers from the page. This is useful for metacontainers that are disposable (e.g., bags, boxes, etc.). If multiple metacontainers are created at once, the first one is selected as the destination. If only one metacontainer is created, it is automatically selected as the destination.
8. Use the visual representation of the layout of the destination metacontainer for types with defined positions. Filled positions are colored in green and empty positions are colored in gray. Clicking a filled position will highlight the position in the contents table. Clicking an empty position will color the position like a target and highlight the position in the contents table. The next available position is selected automatically after the destination metacontainer is selected. This can be collapsed by default through the setup of the MetaContainer Type. If the MetaContainer Type is non-positional, this section will not be visible.
9. The table displays the following columns:
   • Position: displays the numbered position of the container.
   • Container ID: displays the container ID.
   • Container Type: displays the container type.
   • Description: displays a description of the container.
   • Temperature: displays the storage temperature of the container.
   • Testing Host: displays the testing host.
10. Select any empty position in the table and select a container from the worklist to transfer into that position. Once a container has been transferred into a destination metacontainer (before Save is clicked) an option will exist to revert the transfer. This removes the container from the destination, places it back on the worklist, and restores it into its previous position in the storage hierarchy. If its previous position in the storage hierarchy has already been filled, a warning appears alerting the user that both transfers will be reverted. If Uncontained is selected as the destination, it is not necessary to show all containers that are uncontained. This only shows containers that have been transferred into it, but are yet to be saved.
11. Use the search-as-you-type control to select an eligible container from the worklist and place it in this position. This is the same functionality as clicking Transfer next to the container on the worklist, but is more bar code scanner friendly. It allows the user to scan a tube, have that container placed in the current position of the destination metacontainer, and automatically advances it to the next available position in the destination metacontainer. If the container ID that is scanned is not found among the eligible containers from the worklist, an audible alert warns the user. If the sample ID that is scanned has multiple trackable instances, an audible alert warns the user and a pop-up appears for the user to select what trackable instance they wish to transfer.
12. Click Save to save changes made on the page, or click Cancel to not make any changes.

[Return to Top]

Storage Transfer Notes

• If a sample has multiple trackable instances associated with it, and its sample ID is scanned to build the worklist, all trackable instances of that sample appears in the worklist. The user then has to decide what trackable instance they wish to transfer.
• If a sample has multiple trackable instances associated with it, and its sample ID is scanned to place it in the destination metacontainer, a pop-up appears for the user to select what trackable instance they wish to transfer. An audible signal alerts the user that they need to resolve the conflict before proceeding to the next sample.
• In order to be eligible to appear in the transfer worklist, the container must be transferable and not disposed of. All samples are transferable; however, metacontainers can be marked as non-transferable. Metacontainers that are ultimately intended to be non-transferable will need to initially be marked as transferable so they can be placed into the storage hierarchy. Once they are transferred into their correct position, they can be marked as non-transferable, and will no longer be eligible to appear in the transfer worklist. This is intended to prevent them from being accidentally transferred into a different storage hierarchy.

[Return to Top]

 © 2018 Orchard Software Corporation