Call Us: US - +1 845 478 5244 | UK - +44 20 7193 7850 | AUS - +61 2 8005 4826

Planetary Data System

Directory Structure Data will be transferred using a directory structure that parallels the logical organization of a corresponding bundle (Section 2A). Note that the directory structure does not itself have to meet the requirements for logical bundles or collections. Many transfers will contain only a portion of a bundle or collection. 3 See Planetary Data System, PDS 2010 System Architecture Specification, Version 1.2, Pasadena: Jet Propulsion Laboratory, May 2011 (and as updated), available on request from the PDS Engineering Node. PDS Standards Reference 1.11.0 2018-10-01 14 The following sections describe such a directory structure, starting with the root directory. Under the root are subdirectories — i.e., collections, following the logical organization of the bundle — that have controlled names. Under the controlled-name subdirectories are optional sub-directories4 , for which there is no name control (except in the case of a SPICE kernels collection, where name control extends one more level; see Section 2B.2.2.3). In the tables and figures below, the following conventions have been adopted: o Bold-faced font is used for directory names, while unbolded font is used for file names. Where no pattern for directory or file name construction is specified, example names are shown in italics. o The asterisk “*” is a ‘wild card’. In Table 2B-1 browse[_*] means that “browse” or any directory name starting with “browse_” is acceptable. See Section 6C for restrictions on directory and file names. o Square brackets “[ ]” identify variable parts of file or directory names. For example, readme[_*].txt in Table 2B-1 means that the file name beginning with “readme” may be lengthened with any character string that begins with an underscore “_”.