There are features of the Janus Application that are common throughout. They are:

• Janus implements security by restricting access to specific applications and, in some instances, by restricting access to data. You identify yourself when you log on to Janus and the system assigns you access privileges. Janus uses theses privileges to restrict access to unassigned applications. For instance, users may have restricted access to data in the Sample application. A scientist only has access to samples that they entered themselves; a curator has access to all samples.
• The operation of Janus is different on shore versus on ship. In the ship-based application, the Janus user can only access the current leg. In the shore-based application, after login, the user can select a particular leg of interest and that leg becomes the default leg. After this, the application operates the same.
• Each window has a Help menu that accesses the on-line help for that application and a Glossary. The on-line help for Janus is a hypertext help system and is organized by application. When you select Help from any window within the application, the Help information for that application appears in the help viewer. You can navigate through the help to a particular item of interest. The Glossary is a dictionary of terms that are specific to the Ocean Drilling Program. (See Section 1.7 for a more detailed description of the on-line help.)

• The user interface is standard throughout Janus. See the section below for a detailed explanation of the windows, menus, and widgets.

The user interface standards used are Macintosh, Windows, and Motif. There are some interface differences across platforms. They are:

• On the Macintosh, the <tab> key does not advance the cursor to push buttons or choice boxes; in Windows and Motif it does. Therefore, the widget navigation is different on the Macintosh.
• On the Macintosh, the user interface does not support accelerator (shortcut) keys. In Windows and Motif, it does. NOTE: An accelerator key is a keyboard input that permits you to activate a push button without the use of the mouse. The letter that represents the accelerator key is the underlined letter in the button text. Activate it by using Alt + the keystroke.
• In Windows, the fonts default to Bold. For Macintosh and Motif, it is non-bold.
• In Windows, the buttons have a gray background; for Macintosh the background is white.
• Motif platforms display the push buttons, text edit fields, list boxes, and choice boxes shadowed rather than outlined. They become "bold outlined" when active.
• Motif platforms display the radio buttons as diamond shapes rather than circles.

The Janus system and its applications consist of different frames or windows that contain list boxes, choice boxes, buttons, and other widgets. These windows and widgets are the interface to the Janus database and are used to enter, edit, and view data, generate reports, and perform various other functions.

The figures below are typical Janus windows that show the widgets commonly used to enter and edit data.

1.2.1.1.1 Windows

Window functions such as moving and resizing, scrolling, and closing a window work slightly differently for PC, Macintosh, and workstation platforms. If you have any questions about these functions for the platform that you are on, you should consult the user's guide for that particular platform.

Some windows contain panels. Panels are regions within the window that contain widgets that are closely related functionally. Panels appear outlined in order to separate them from the rest of the window and they usually have labels that identify them with a panel name.

Janus utilizes a "status area" that is a region at the bottom of the parent window (or the bottom of the screen). The purpose is to display error and warning messages as you enter and edit data.

1.2.1.1.2 Menus

Some menus in Janus are "cascading" menus. Cascading menus have options that expand to sub-menu options. If a menu option has sub-menu options, a black diamond appears to the right of that option. When you select the option, the sub-menu options open to the right.

1.2.1.1.3 Widgets

Widgets are objects in the windows that aid in the entry and edit of the data. Types of widgets used in Janus are text edit fields, choice boxes, check boxes, radio buttons, and push buttons.

Text edit fields are labeled boxes in which to enter and edit the data. When you move into an empty edit box, an insertion point (a flashing vertical bar) appears at the far left side of the box. The text you type starts at this point. If the box you are in already contains highlighted text, then anything you type in the box replaces the existing text.

There are two types of choice boxes:

• Drop-Down Combo Box - This type of choice box is a small rectangular box identified by the down arrow to the right of the box. The choice box either contains the last option that was chosen or a default value, depending on the window. When you click on the box or the arrow in the square box at the right, a list of available choices appears. If there are more items than can fit in the box, you can use the scroll bars provided to move up and down the choice box. To scroll the list, either drag the scroll box through the information or click on the up or down arrows provided. To choose an option, click on it. The choice box closes and that item appears in the box. This type of choice box also allows you to type in an entry.

• Drop-Down List - Some choice boxes have both up and down arrows. These choice boxes do not stay open when you click on them. Therefore, to select an item from the list you must click on the arrow and, while holding the mouse button down, scroll the list until you come to the selection you want.

Radio buttons are used when there are multiple choices but you must choose only one. Radio buttons usually appear as a transparent circle next to the item. To select that item, click on the circle. A black circle then appears inside the transparent circle. When you select another item, the previously selected radio button clears.

A check box next to an option means that you can select or clear that option, or in other words, turn it "on" and "off". A checkbox uses a square box as a marker. To indicate that this value is "on", click on the box. An X appears in the box. To turn it "off", click on it again. You can select as many check box options as needed.

Push buttons appear at the top, right side, or on the bottom of a window. Most push buttons initiate an immediate action, such as saving data, closing a window, or closing a window without saving data. The purpose of some buttons is to delete selected lines of data from a table or to insert a blank line in a table so that you can add new data. Other buttons may open another smaller window in which you enter more data. A list of standard buttons used in Janus follows, along with descriptions of their functions.

• or These buttons insert a row in a list box and populate column values from a set of data entry fields.
• This button returns values selected or entered in the current window to the previous window. The window remains open.
• This button changes the column value in the selected row of the list box to values entered in edit/entry fields outside the list box.
• This button clears the values for an edit/entry field or a group of related fields.
• This button loads the selected field or cell with a default value of 150.
• This button displays the foreground of a selected row in a list box as green, which denotes that it the system marked it for deletion. The system does not actually delete the data until you execute the Save function.
• This button removes the selected data immediately from the frame. You are not able to cancel the deletion.
• This button exits the frame.
• This button duplicates the selected cell value or and entire selected row into the next row of the list box.
• or The Login button requests a user ID and password before you can proceed with the application. Select Cancel if you do not wish to continue.
• This button initiates creation of a new record.
• or These buttons appear in windows in which you enter data for one record only and then leave. Use OK to save the data and exit the window and use Cancel to exit the window without saving any data.
• This button sends the report in the window to the printer.
• This button searches the database using criteria entered in the panel containing the Query button.
• This button repopulates the window with different data from the database than what currently appears in the window.
• / Use the Save button to insert new information into the database, to update information that changed in the database, and to delete all of the accumulated records marked for deletion from the database. The window remains open. Use the Cancel button to exit the window, discarding any unsaved edits without a prompt reminding you that you have not saved.
• / / This button allows intermediate changes to the database. Use the Save button to insert new information into the database, to update information that changed in the database, and to delete all of the accumulated records marked for deletion from the database. The window remains open. Use the Close button to exit the window, with a prompt reminding you to save unsaved edits. Use the Cancel button to exit the window, discarding any unsaved edits without a prompt reminding you that you have not saved.
• This button downloads selected data to a file in spreadsheet format.
• This button displays a selected report.
• This button executes the SQL+ program that generates the report and writes it to a tab delimited ascii file.

List boxes contain data that is in table format (rows and columns). The data in these list box tables are data previously entered either in that window or some other area of the Janus Application. Some list boxes display the data exclusively in read-only format for informational purposes. In others list boxes you can enter or edit data. You can scroll list boxes in the same manner as choice boxes.

The background of the text edit fields and list boxes is colored to indicate whether they are read-only, optional entry, or required entry items.

• White Background - Read-Only: Read-only fields display existing data.
• Gray Background - Optional Entry: Optional entry fields are fields that do not require entry in order for an action to be completed. The data can be saved and you can come back at another time and fill in these optional fields.
• Green Background - Required Entry: Required entry fields must have a value in them in order for the action to be completed. In other words, you must enter data in required fields in order to save.

In some applications in Janus, the color of the text as you enter it can change, depending on the validity of the values you are entering. Text is normally colored black, however if you enter a value in a field and the color changes to blue when you move to the next field, this means that that value is invalid but the system accepts it. If it changes to red as you move to the next field, the value is invalid and you must change it to a valid entry before the system allows you to save. In either case, you can check the message in the status bar below the window to see what the problem may be with the value(s) you entered.

When entering or editing data in text edit fields, you can easily move from field to field by hitting the <Tab> key. When you do this, the cursor automatically moves to the next field available for data entry. This saves you the step of moving the cursor with the mouse to the next field.

The same is true for moving from column to column in list box tables. Some particular windows have tables that you can modify so that when you use the <Tab> key you can bypass columns not needed. The on-line help for windows containing these tables points these out specifically.

There are some exceptions to the <Tab> key navigation rule. In a few instances, you must use the <Enter> key to move out of a text edit field in order for that data to populate the list box table and the database. The on-line help also explains these exceptions.

This userís manual is an overview of Janus. There is a separate section for each Janus application that explains the purpose of each window and describes the widgets and text fields found in them. More detailed help (step-by-step instruction) can be found in the on-line help for every application.

The on-line help for Janus is a hypertext help system. When you choose an option in the Help menu of any of the application windows, the Help Viewer appears. The viewer contains the text descriptions of the particular topic selected along with a list of other topics related to the subject in the window. The other topics appear as blue text. When you place the mouse pointer over any blue text, it changes to a pointing hand. When you click on the blue text, a new window appears that contains the help corresponding to that topic. This text may also contain words or terms that are in red. When you click on these while holding down the mouse button, a small window pops up that contains a more detailed explanation or a hint concerning the word or term in red. Below is a picture of the Help Viewer containing a sample topic.

The Help Viewer contains a menu bar with the following commands that aid in reading and finding help on certain topics.

• File Menu

• Open: Opens the file selector which allows you to select a help file to display. In other words, while you are in one applicationís help you can retrieve the help for another application.
• Print Topic: Prints the topic in the current window.
• Printer Setup: Opens the Setup window for your particular printer.
• Exit: Closes the Help Viewer.
• About Help: Opens the about box for the On-Line Help.

• Edit Menu

• Copy to Clipboard: Copies the contents of the current topic to the clipboard. This allows you to paste the text into a document.

• Help on Help - This brings up detailed instruction on using the Open Interface Help.

The Help Viewer also contains a series of buttons that activate commands:

• Home: Jumps to the first window of the help. Generally, the first window contains a list of topics about the application.

• Contents:

• Back: Takes you back to the last window or topic that you were viewing.

• <<: Jumps to the previous topic in a list of topics.

• >>: Jumps to the next topic in a list of topics.

• Up: Jumps to the parent topic of the current topic.

Double-click on the Janus icon to start the Janus Application.

The Janus startup window containing copyright and proprietary messages appears.

 The purpose of this button is to bring up the Janus Login window.

When you start up Janus, the Janus Login window appears.

To log on, enter your Username and your Password in the appropriate fields and click on the Login button. When you log on, the Enter Leg window appears (see Section 2.3.1.2) in which to enter the number of the leg you wish to edit.

• Clicking on this button completes the log in function after you enter User name and Password. The Enter Leg window also appears when you click the button.
• This button exits the window without logging on to Janus.

The main window of Janus, called Ocean Drilling Program - Janus, provides access to all of the individual applications that make up Janus. It also contains functions used to set preferences, change legs, and view a list of Janus-related reports. The window opens after you log on to Janus.

The File menu options are:

The Logout option in the File menu is used to quit a Janus session without actually quitting the application. When you select Logout, the ODP Database Login window appears and the next user can log on.

The Change Legs option in the File menu is active when Janus is used on shore and is inactive on the ship. Selecting this option brings up the Enter Leg window which allows you access to all of the data from any leg to which you were assigned. The window automatically comes up when you log on to Janus from the shore.

When the window opens, the Barcode/Leg field is blank. Enter the leg from which you wish to see data or scan any barcode label from the leg.

• Clicking on this button retrieves all the data for the leg entered in the Barcode/Leg field. The Ocean Drilling Program - Janus window returns.
• This button exits the window.

The Quit option in the File menu is used to exit Janus.

The Applications menu options provide access to all of the applications found within Janus:

The Chemistry application is used to input and process different types of chemistry data generated and then stored in a comma-delimited file. These files can be read and then transferred into the Janus database. Chemistry sample records can also be updated or deleted and new items can be added to chemistry-related reference tables in the database.

Open Chemistry by selecting the Chemistry option from the Applications menu of the Ocean Drilling Program - Janus window.

The Core application consists of functions related to core activities. These functions include entering, editing, and viewing core, section, and section half data; printing bar code labels for D-tubes; entering expansion and contraction data for sections and section halves; rebuilding depth maps; and generating tracking sheets. Core works in conjunction with many Operations functions where leg, site, hole, and primary and secondary core data are entered. Core requires that this key data already exist in the database.

To open Core, select the Core option from the Applications menu of the Ocean Drilling Program - Janus window.

The Core Description application provides a method of exporting core and section data into the AppleCore program.

To open the window, select the Core Description option from the Applications menu of the Ocean Drilling Program - Janus window.

The Curation application consists functions that include entering and editing sample requests, assigning scientists and their mailing addresses to a request, entering new scientist information, and entering sample codes.

To open Curation, select the Curation option from the Applications menu of the Ocean Drilling Program - Janus window.

The MST Application provides methods to transfer Lab View data into the Janus Application, enter and edit sensor data, and upload Lab View data into files to use in spreadsheets.

To open MST, select the MST option from the Application menu of the Ocean Drilling Program - Janus window.

The Operations Application consists of functions related to operations activities. Operations activities include entering leg, site, and hole data, starting a new hole, entering primary and secondary data for new cores, entering beacon and bit inventory data, entering beacon and bit usage data, and entering pump liner sizes. Many Core Application functions rely on the operations data entered here.

To open Operations, select the Operations option from the Application menu of the Ocean Drilling Program - Janus window.

The Paleontology application provides an environment that paleontologists can tailor to their own investigative tastes in which to enter, edit, and view data related to paleontology. They can also generate reports.

Open the Paleontology application by selecting the Paleontology option from the Applications menu of the Ocean Drilling Program - Janus window.

The Physical Properties application allows you to retrieve files generated by Lab Viewís Velocity and Shear and Moisture Density applications and upload these files into Janus.

Open Physical Properties by selecting the Physical Properties option from the Application menu of the main Ocean Drilling Program - Janus window.

The Sample application consists of functions that include entering and editing data for samples taken from retrieved cores, and generating sample labels and tracking sheets.

To open Sample, select the Sample option from the Applications menu of the main Ocean Drilling Program - Janus.

The Splicer Application in Janus is used to take output files from ODP's Splicer application and load them into the Janus system. ODP's Splicer application provides a shipboard and shorebased tool for compositing and splicing MST core data. Splicer has two primary output files that are related to its two main functions, which are compositing and splicing. Compositing refers to the process of linearly depth-shifting individual cores to optimally align stratigraphic features between multiple holes at a given site. Splicing is the process of using the depth-shifted (composited) core data to build a single, continuous record by splicing core intervals from various holes at a given site.

Open the application by selecting the Splicer option from the Application menu in the Ocean Drilling Program - Janus window.

The Xray application consists of functions that allow Xray Techs to store XRD data to the database, input XRF and XRD data into the database from existing files, add new data to the references tables in the database.

Open Xray by selecting the Xray option from the Applications menu of the Ocean Drilling Program - Janus window.

There are three options in the Preferences menu that are used to set defaults for use in a session:

The Depth Calculation Preferences window is used to set the preferences for the way the system calculates the depths in any window that performs depth calculations. To open the window, select the Depths option in the Preferences menu.

When the window opens, the preferences are set to system defaults. These defaults are:

• Map Type = STD;
• Depths NOT adjusted by MCD;
• Depths NOT adjusted by Core Compression;

You can change these defaults directly in the database so that they appear in the window when it opens after initial log on. To change the default depth preferences for the current session, select any of the other options. Once you log out and log back on again, the preferences revert to the system defaults. When you open the Depth Calculation Preferences window again in the same session, the Map Type field defaults to the last one selected. The Map Type Description field contains the description of that Map Type. The Select MCD Adjustment and Select Compression Adjustments are those last selected.

• Clicking on this button applies the depth preferences selected in the window to the current Janus session. The window closes.
• This button exits the window without changing preferences.

The principles underlying the management of depths in Janus are discussed in detail in DEPTH DATA ACQUISITION, PROCESSING AND ARCHIVING IN THE OCEAN DRILLING PROGRAM, Recommendations and Results from the ODP/TAMU DEPTH WORKSHOP (January 1995). The followiwng paragraphs discusses the practical computation of depths in Janus.

Calculation of depths in the Janus system is a two step process. Step 1 is creation and maintenance of depth_map table entries for each section entered into the system. For each section, a set of map intervals is defined that relate points on that section to a depth. For example, suppose a section is 1.5 meters in length. Then a possible set of depth_map entries for this section could be: (0,.5:200,200.5), (.5,1.5;200.5,201.5). In essence, a depth_map is a set of piecewise linear curves defined over every section in a hole, a row in the depth_map table contains the coordinates of the endpoints of each portion of the curve. There are four map types:

• STD - standard MBSF depth, this is the current depth calculation method offered by ODP.
• SV - STD depths with voids removed.
• SE - STD depths with exotic regions removed ( see Depth Workshop report for definition of exotic interval).
• SVE - STD depths with void and exotic intervals removed.

Upon initial entry into corelog of a section, default map intervals are entered into the depth_map table for each map type. Each default interval is equal to the length of the section. Users may then use the Core Subsection window (cor07) to designate intervals within a section as void or exotic, and the system then makes the appropriate updates to the SV, SE, SVE map intervals for that section. Note, for any section, the sum of the length of the map intervals (for a given map type) is always equal to the curated length of the section. Conceptually then, for any point in a section, the depth of that point can be determined by doing an interpolation on the map interval that contains that point.

Step 2 of the depth calculation process is generation of a depth using the SQL function GET_DEPTHS. An important feature of the Janus depth calculation scheme is that depths are always calculated on the server using this function, they are NOT stored for each sample or MST measurement. This means that, to correct errors in depth calculations for a given hole, only the depth_map table entries for this hole need to be corrected. The syntax for the GET_DEPTHS function is:

Note that, for each of the four depth types, depths can also be adjusted by MCD or can be compressed. MCD adjustment of depths is done by adding meter_comp_depth from the core table to the unadjusted depth. This value is input into Janus from the affine table generated by Splicer. In effect, meter_comp_depth is the factor generated by Splicer that puts cores from all holes at a given site on a commensurate depth scale. Consider holes A and B at site iii. For cores A1,A2,...Am, B1,B2,...,Bn the depths top_depthA1, top_depthA2, ..., top_depthAm are not directly comparable to the depths top_depthB1, top_depthB2, ..., top_depthBn, i.e. it is not proper to make statements such as top_depthA3 > top_depthB3. However, using the results from Splicer, and adjusting the top of each core by its corresponding meter_comp_depth(mcd), the depths top_depthA1+ mcdA1, top_depthA2 + mcdA2, ..., top_depthAm + mcdAm, top_depthB1+ mcdB1, top_depthB2 + mcdB2, ..., top_depthBm + mcdBm are commensurate and it is therefore proper to make statements such as top_depthA3 + mcdA3 > top_depthB3 + mcdB3.

Compressed depths are generated in the following ways. For depth type STD, all sections for a given core are uniformly compressed so that the sum of their lengths is equal to the advancement for that core. For depth types SV, SE, SVE, all sections are first adjusted by having the appropriate map intervals subtracted from their length and then are uniformly compressed so that the sum of the adjusted lengths is equal to the advancement for the core. If the sum of the section lengths for STD or adjusted section lengths otherwise is less than the advancement for the core, no compression is done and, conversely, sections are not expanded to match advancement.

The Janus depth calculation scheme can be expanded to produce other depth estimates. All that is needed is definition of a new map type and insertion into the depth_map table of a set of map intervals for each section. Note, nonlinear depth approximations can be made by using piecewise linear curves that approximate the non-linear depth.

The Age Model Preferences window is used to set the age model type that is used when creating age models in the current session. Open the window by selecting the Age Model option in the Preferences menu.

When the window opens, the Model Type choice box selection defaults to the last model type preference selected. The choice box contains the three standard model types, Shipboard, Initial Reports, and Post Moratorium, plus any user-defined types that have been entered in the Enter Age Model Control Points window during the current leg. The Model Type Description field contains the description of that model type.

To set the model type to be used for creating age models during the current session, select it in the choice box. NOTE: If you select an age model that was created using a personalized name for the type like "John Smithís Model", it appeasr as "User-defined model" in the Model Type field.

• Clicking on this button updates the database with the age model preference you selected. The window closes.
• This button exits the window without saving.

The Set Up XRD Queues window is used to set the directories in which the UDF and UDI files for transfer reside while they are waiting for transfer and after they are transferred. Open the window by selecting the XRD Queues option in the Preferences menu.

The XRD queues should be set up for the local machine that runs the XRD Phillips software. NOTE: These queues must be accessible from that machine. For instance, they could reside on a network drive that is mounted on that machine. Since the UDF/UDI files are kept on network drives, it is suggested to have the "waiting" queues on the local machine and the "transferred" queues on the network drive where they are normally stored. Be sure the network drive is physically attached to the computer when you begin to do an upload.

The four queues that need to be set up are:

• UDF Waiting -- This directory contains the UDF files that are waiting to be transferred.
• UDF Transferred -- This directory contains the UDF files that have been uploaded to the Janus database.
• UDI Waiting -- This directory contains the UDI files that are waiting to be transferred.
• UDI Transferred -- This directory contains the UDI files that have been uploaded to the Janus database.

To change the XRD queues for the current session only, type them into the appropriate fields and click on the OK button. The system saves the queues and the window closes.

To change the XRD queues in the defaults table in the database. enter the queues and click on the Save Preferences to Database button. NOTE: Saving the queues to the defaults table prevents you having to enter new queues each time an upload is done.

• Clicking on this button changes the XRD queues for the current to those entered in the four fields. The window closes.
• This button exits the window without saving.
• When you click on this button, the system saves the XRD queues entered in the window to the defaults table in the database.

The Output/Reports menu options are:

The Pick List option in the Reports menu accesses the Reports Pick List window which allows you to locate reports by specific category and then view the report.

When the window opens, the category of report in the Filter panel defaults to "Any" and the list box contains a list of all existing Janus reports. To view a list of reports in a particular category (operation, curation, core, etc.), select that category in the Filter choice box. When you select a report in the list box, the panel below the list box contains a description of that report.

The Depths Utility window is used to attach depths to files containing leg, site, hole, core, core type, section, and top and bottom intervals. Access the window by selecting the Depths Utility option from the Output/Reports menu of the ODP - Janus Application window.

When the window opens, the Input/Output File Name fields are blank. The Output Format defaults to Insert in Row. The Use Preference Selection field is whatever depth preference was set for the current session in the "Depths" window. The Records Processed field defaults to 0.

To load a file to which to attach depths, either type in the name of the file in the Input File Name field or use the Query Input function to select a file for input. Next, enter a name for the output file in the Output File Name field, or choose an existing file to overwrite using the Query Output function to select that file.

To attach the depths, select the desired Output Format (Insert in Row or Add to ID) and then click on the Attach Depths button. If you wish to have the age model type that was used when generating depths displayed, click on the Add Ages check box before clicking the Attach Depths button. The system reads the file, attach the depths to the data, and then write the new output file. As the system writes the new file, the Processing Log at the bottom is loaded with information that pertains to the status of the depths being attached to the file. The Records Processed value increases as records are processed.

• Clicking on this button activates the selection dialog box for choosing a file to input. After you select the file, the system loads that filename into the Depth Input File Name field.
• This button activates the selection dialog box for choosing a file to overwrite with the new output file. The file name then appears in the Depth Output File Name field.
• When you click on this button, the system reads the input file, attaches depths to the data, and then writes the new output file. As the file is written, the Processing Log is displays the status of the depths being attached.

The Sample Barcode List window allows you to print a list of the barcodes for a particular set of sample codes. Open the window by selecting the Barcode List option in the Output/Reports menu. You can also access the window in the Xray application through the Tech Support menu. NOTE: In order for the barcode list window to work properly, the Bartender format file, xraylist.btw, needs to be in the janus/lib directory. See the Janus Maintenance Manual for details.

To print a barcode list, enter the Leg, Site, Hole, Core and Core Type (core and core type are optional) for the samples and then list the sample codes. You can also scan a barcode label. Click on the Print button to print the list.

You can use this list to scan barcodes anywhere in Janus that a barcode entry is required.

• Click on this button to print the sample barcode list for the leg, site, hole, core, CT and Sample Codes entered.
• This button closes the window.

The Barcode Translator window is used to translate a barcode into its corresponding identifiers. You can also translate a set of identifiers into the corresponding barcode. Open the window by selecting the Barcode Translator option in the Output/Reports menu. You can also access the window through the Tech Support menu in the Xray application.

To translate a set of identifiers to the corresponding barcode, enter the identifiers into the fields in the ODP Identifiers panel. Select the Sample or Section radio button and click on the << button. The system displays the barcode in the Barcode field.

• Clicking on this button translates a set of identifiers entered in the ODP Identifiers panel into its corresponding barcode.
• Use this button to translate a barcode entered in the Barcode field to the corresponding identifiers.
• This button closes the window.