On this page...
Retrieved Data Products
Data products which are selected for download may be organized in a directory structure once they appear on your local storage, depending upon the download method.
Browser and Bash Downloads
Downloads using the following methods
- one-click download
- browser zip or tar bundles (see Download Basket)
- bash script retrieval (example: MAST_2020-11-10T0846.sh)
will be organized in a directory structure by mission and observation ID, once the bundle is unpacked on your local storage. The abbreviated example below shows a result for the target M57, which has been observed by several missions:
FUSE
b0690201000
- (files)
HST
ibh601050
- (files)
u2sa3301t
- (files)
IUE
lwp20382
- (files)
swp02487
- (files)
MANIFEST.HTML
PS1
product
- (files)
TESS
tess2019198215352-s0014-0000000029008855-0150-s
- (files)
MANIFEST File
The MANIFEST.HTML file is just an HTML table listing the name of every file that was requested, whether the download succeeded, the name of the user, and whether the file is public or falls under exclusive access rules. If you request a file before its public release date, but are not authorized to retrieve it, the file will be listed in the Manifest but will be marked as "Not Authorized."
Batch Downloads
Files which are staged for ftp retrieval from the archive.stsci.edu ftp server are flat directories of all observations.
Batch downloads are available for only a very limited number of missions, such as for HST and (after launch) JWST.