The CLC URL - name form
The object-name form of CLC URLs can be used to refer to data resources within persistence models or to refer to files located on the machine the CLC Server software is running on.
The first section of a object-name form of a CLC URL indicates whether it is referring to a data object in a CLC Server persistence model or to a file stored in an area configured as an Import/Export location for the CLC Server. These forms are:
clc://server
clc://server URLs refer to a data object present in a persistence model. This part of the URL is then followed by the name of the persistence model the data is located in. For example, the name of particular CLC Server File Location. An example of this form is:clc://server/CLC_Server_Project/alignments/myAlignment
Note that for CLC data in a persistence model, you need the name of the data object (as seen via the Navigation Area of the Workbench) not the name of the file holding the data object (as seen when listing files using system tools like the commands ls or dir).
clc://serverfile
clc://serverfile URLs refer to a file in an area configured as an Import/Export area for the CLC Server. This form would commonly be used to point at files containing data that is about to be imported into the CLC Server, or to indicate a location to export data to. An example of this form is:
clc://serverfile/mnt/data/project1/s_1_1.sequence.txt
Benefits of the name form:
Human readable and easier for many people when first starting out working with the Command Line Tools or when just running a few commands directly (as opposed to via a script).
Drawbacks of the name form:
Any changes to the names of data objects or folders in the persistence model will break the URL.