Changes between Initial Version and Version 1 of DataTransferMethod


Ignore:
Timestamp:
07/06/05 08:19:42 (13 years ago)
Author:
joe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DataTransferMethod

    v1 v1  
     1= Data Transfer Methods = 
     2 
     3The VSO provides a number of keywords to describe the methods in which data products are made available from each of the VSO Data Providers. 
     4 
     5Some transfer methods may require [wiki:UserInfoKeywords additional information] to complete the request. 
     6 
     7For the most recent list of Transfer Method Keywords, please see 
     8 
     9   http://vso.nascom.nasa.gov/cgi-bin/show_details.pl?keyword=METHOD_PREFIX 
     10 
     11Each basic transfer type will typically be modified by one or more sub-types to better describe the packaging of the data products. 
     12 
     13The most recent list of subtypes can be found at 
     14 
     15   http://vso.nascom.nasa.gov/cgi-bin/show_details.pl?keyword=METHOD_SUFFIX 
     16 
     17A listing of which methods each Data Provider supports is available at 
     18 
     19   http://vso.nascom.nasa.gov/cgi-bin/show_details.pl?keyword=PROVIDER 
     20 
     21Please note that this is not a complete list of available transfer methods, and that as of this writing, at least one of them isn't currently being used by any Data Providers. The list of transfer methods used by VSO Data Providers may change as new Data Providers are added, or demand for other transfer types are identified 
     22 
     23 
     24== Basic Data Transfer Methods == 
     25 
     26=== URL === 
     27 
     28There is a URL that can be followed to get to the data of interest. 
     29 
     30=== STAGING === 
     31 
     32The data must be processed by the Data Provider before it is made available for download. Typically, for STAGING transfers, the Data Provider will request an e-mail address that they can send notification to when the process is complete. 
     33 
     34STAGING responses should contain Detail elements that give an indication as to how long the request will take to complete. 
     35 
     36=== OFFLINE === 
     37 
     38The data can be sent encoded on physical media, and sent through parcel post. Typically, for OFFLINE transfers, the Data Provider will request an e-mail address or phone number to coordinate the process. The Data Provider may request information for shipping the products, such as the recipient's name and shipping address. 
     39 
     40OFFLINE responses should contain Detail elements that give an indication as to how long it will take for the Data Provider to respond to the request, to work out necessary details, such as the possibilility of cost-recovery. 
     41 
     42=== PUSH === 
     43 
     44The data will transfer the data to you, if you give them the appropriate connection information for them to do so. Typically, for PUSH transfers, the Data Provider will request an e-mail address that they can send notification to when the process is complete, or to work out any difficulties that may occur. They will also require connection information so they can transfer the data to the requesting user. 
     45 
     46PUSH responses should contain Detail elements that give an indication as to how long the request may take to process. The time is typically an indicaton as to when the process may start, as the Data Provider would have no knowledge of the transfer rate to the user's system as this time. 
     47 
     48Please check with your local information or network security office before coordinating a PUSH of data, as it will often times be blocked a border router or firewall, or it may fall under specific security policies within your organization. 
     49 
     50== Transfer Method Subtypes == 
     51 
     52A Data Provider may support multiple methods, of one or more basic types. Specific methods are specified by giving a basic type, a hypen, and a sub-type. 
     53 
     54Subtypes vary by basic types, but for the most part, specify the method of encoding the data: 
     55 
     56=== URL === 
     57 
     58The sub-type for URL specifies the compression and packaging of the data. For example, 
     59 
     60 * URL-FILE 
     61 A single file available for each URL. 
     62 * URL-packaged 
     63 A special case, requesting few URLs to download all of the requested files. (ie, URL, but not URL-FILE) 
     64 * URL-TAR 
     65 Each URL points to a tar'd group of files. 
     66 * URL-TAR_GZ 
     67 Each URL points to a tar'd group of files, which has been gzip'd. 
     68 * URL-ZIP 
     69 Each URL points to a group of files in a ZIP archive. 
     70 
     71=== STAGING === 
     72 
     73The sub-type for STAGING specifies the compression and packaging of the data. For example, 
     74 
     75 * STAGING-TAR 
     76 The files are archived using the unix tar command or its equivalent. 
     77 * STAGING-TAR_GZ 
     78 The files are archived using the unix tar command, and then compressed using gzip. 
     79 * STAGING-GZ_TAR 
     80 The individual files are compressed using the gzip command, and then archived into a tarball. 
     81 * STAGING-ZIP 
     82 The files are archived using ZIP compression. 
     83 
     84=== OFFLINE === 
     85 
     86The sub-type for OFFLINE specifies the type of media that the Data Products should be written to for shipment. For example, 
     87 
     88 * OFFLINE-CD 
     89 The data will be written out to a Compact Disc. 
     90 * OFFLINE-DAT 
     91 The data will be written out to a 4mm Digital Audio Tape. (yes, I know, it's technically not a DAT when it's not holding audio information, but it's what people are used to calling it) 
     92 * OFFLINE-EXABYTE8200 
     93 The data will be written out to an Exabyte model 8200 tape. 
     94 * OFFLINE-EXABYTE8500 
     95 The data will be written out to an Exabyte model 8500 tape. 
     96 
     97=== PUSH === 
     98 
     99The sub-type for PUSH specifies the protocol that will be used to transfer the data. For example, 
     100 
     101 * PUSH-RCP 
     102 The data will be transfered using the Remote Copy Protocol. This will typically require the requesting user to configure an appropriate rhosts file, and the Data Provider should specify their server's name in the details element of their response. 
     103 * PUSH-FTP 
     104 The data will be transfered using the File Transfer Protocol. Please note that many places may prefer anonymous FTP, where no password is used, to prevent it from being sniffed while in transit, while others prefer that anonymous FTP not be used due to the potential for unauthorized parties to gain access to place files on the system. 
     105 * PUSH-SCP 
     106 The data will be transfered using the Secure Copy Protocol. 
     107 * PUSH-SFTP1 
     108 The data will be transfered using the Secure File Transfer Protocol, version 1. Please note that a system that supports SFTP2 may not also support SFTP1, although it is designed to degrade gracefully should SFTP1 also be installed. 
     109 * PUSH-SFTP2 
     110 The data will be transfered using the Secure File Transfer Protocol, version 2. Please note that a system that supports SFTP2 may not also support SFTP1, although it is designed to degrade gracefully should SFTP1 also be installed.