The TRI library editor allows you to edit library files of TRI screen information. The screens do not have to be valid and duplicate screen names for a given type of screen is permitted.
Short name is a name for this library file which will be displayed in the TRI libraries tree.
Description is a longer description of this library file.
Create screen of type allows you to select a type of screen which you would like to create. Once you've completed creating the screen, it will be added to the "Current screens" table.
Current screens contains the screens which currently make up this library. An entry may be edited using the "Edit" button and deleted using the "Delete" button. Screens in the standard TRI display may be dragged and dropped onto this table to add a data node to this library.
TRI will always have a library "My library". This would be a good location to store you individual information for the "People" screen. Then this information could be dragged and dropped onto the General information People node any time a new test request is being created.
Departments or engine groups may want to create their own shared library of engine information for use with the Engine screen. Likewise create a shared library of project information for use with the Project screen.
Screens defined in libraries do not have to be valid. For example a screen might be partially filled in expecting it to be completed when dropped into a test request. In this case the TRI library display will not show the screen to be invalid. However when this screen is dropped into a test request TRI will show that it's invalid where it was dropped.
Presently (02/06/2014) only screens from Libraries -> Local Screens may be dropped into libraries. They may be dropped onto the base library node in the Libraries tree or if the library editor is being displayed they may be dropped onto the Current screens table.