|
A Ground Motion Library is made of one or more "collections" of records.
“Collections” are not disk “folders” but rather virtual Collections of records in the ground motion database.
However, nothing prevents you from organizing records into the database such that collections mirror disk folder contents.
Importing Records into Collections
If you drag & drop one or more folders from your disk into the Ground Motion Library, QuakeManager will create collections and sub-collections with the same names as the folders and sub-folders that you are dragging, and import any ground motions in those folders into the created collections.
It is also possible to import records and metadata into a collection using the CSV Import Tool.
Modifying a Collection's Properties
To modify the properties of a collection, right-click on the collection and choose "Properties".
The Collection Properties dialog is shown below.
.png)
Figure: Ground Motion Library Tree
Note on Variable Names
Variable names can be used in defining paths. Variable names should be preceded and followed by %. Available variable names include:
%COLLECTIONNAME% the name of the collection
%GMLIBPATH% the path of the GM Library, as defined in the program Options
%PARENTPATH% the path of the parent of the collection. This is typically used when "Absolute" path is being defined, and generally is equivalent to using the "Relative to Parent" option, but provides slightly more control.
.png)
|
.png)
|
Collection Name
|
|
Collection name that appears in the Library tree
|
|
.png)
|
Full Path Name
|
|
Show the path of the library in the local disk
|
|
.png)
|
Collection ID
|
|
Database unique ID
|
|
.png)
|
Disk Path
|
|
This is where you specify the default disk path for records within this collection. Note that you have the option of defining the Disk Path to be "Absolute" or "Relative to Parent" which means it will be defined relative to this collection's parent path. This allows you to make collections that mirror folders on your disk, that you can easily move around and rearrange. For example, in the image below, the final disk path is "C:\GMLibrary\SACSteel" which includes the path of the parent collection ("C:\GMLibrary\") and the relative path of the current collection ("SACSteel"). Also, note that the collection's "Disk Path" (in this case "C:\GMLibrary\SACSteel") will be pre-added to the "FolderDisk" property of each record within the collection. The main advantage of this approach is that if you move all the records of a collection to a different folder on your disk, you will not have to modify the path of each record individually, but can simply modify the path of the collection itself to refer to the new folder.
|
|
.png)
|
Apply to all Children (Recursive)
|
|
If checked, all defined "Disk Path" properties will be applied to all collections that are children of this collection. This can be handy if all children of the current collection have the same "Disk Path".
|
|
.png)
|
Relative to Parent/Absolute (Disk)
|
|
Define if the defined "Disk Path" is absolute or relative to its parent "Disk Path"
|
|
.png)
|
Inherit from Parent (Disk)
|
|
If checked, the "Disk Path" will be set equal to its parent
|
|