Date: Thu, 28 Mar 2024 06:34:46 -0400 (EDT) Message-ID: <426243443.725.1711622086763@ploutercf.stsci.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_724_2129952650.1711622086761" ------=_Part_724_2129952650.1711622086761 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Data products which are selected for download may be organized in a dire= ctory structure once they appear on your local storage, depending upon the = download method.
Downloads using the following methods
will be organized in a directory structure by mission and observation ID= , once the bundle is unpacked on your local storage. The abbreviated exampl= e below shows a result for the target M57, which has been observed by sever= al missions:
FUSE
b0690201000
HST
ibh601050
u2sa3301t
IUE
lwp20382
swp02487
MANIFEST.HTML
PS1
product
TESS
tess2019198215352-s0014-0000000029008855-0150-s
The MANIFEST.HTML file is just an HTML table listing the name of every f= ile that was requested, whether the download succeeded, the name of the use= r, 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."
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.