performed on the Product before the Product is placed into PDA's inventory Example: "NONE", "CRC32", "SHA-384", etc. Checksum Receive Method: Input the method by which the checksum will be received. The following values are valid for this (if Integrity Yes field: Check not "NONE") FILE_NOTIFICATION: The value is provided in 3.10 the File Notification message FILE: The value is contained in an associated file Example: Must be either: or “FILE” “FILE_NOTIFICATION” Checksum FileName Pattern: If the receive method for the checksum is by file, then this field is populated with the regular expression that is used for matching the Checksum Yes (if Integrity file name. Check not "NONE") 3.11 Example: "sst.tmpobs.SATIDs.yyyy.ddd.hhmm" (where SATIDs are multiple 3-character satellite IDs concatenated together reflecting the data in the file) Example: "sst.tmpobs.n19m02n18n17.2010.270.1807" Checksum File Sub String: If the receive method for the checksum is by file, then this field is populated with the substitution Yes (if Integrity string used to build the Checksum file name. Check not "NONE") 3.12 Example: "sst.tmpobs.SATIDs.yyyy.ddd.hhmm" (where SATIDs are multiple 3-character satellite IDs concatenated together reflecting the data in the file) Example: "sst.tmpobs.n19m02n18n17.2010.270.1807" Product Acquisition Strategy: Indicate how the file will be acquired by PDA. The expectation is that the product should be pushed to PD. If acquisition strategy is a form of pull, you must justify. 3.13 Yes Example: For PDA, must be one of the following: FTPPULL (PDA performs an FTP PULL), FTPPUSH (The file is FTP PUSHed to PDA), FTPSPULL (PDA performs an FTPS PULL),
performed on the Product before the Product is placed into PDA's inventory Example: "NONE", "CRC32", "SHA-384", etc. 3.10 Checksum Receive Method: Input the method by which the checksum will be received. The following values are valid for this field: FILE_NOTIFICATION: The value is provided in the File Notification message FILE: The value is contained in an associated file Example: Must be either: “FILE” or “FILE_NOTIFICATION” Yes (if Integrity Check not "NONE") 3.11 Checksum FileName Pattern: If the receive method for the checksum is by file, then this field is populated with the regular expression that is used for matching the Checksum file name. Example: "sst.tmpobs.SATIDs.yyyy.ddd.hhmm" (where SATIDs are multiple 3-character satellite IDs concatenated together reflecting the data in the file) Example: "sst.tmpobs.n19m02n18n17.2010.270.1807" Yes (if Integrity Check not "NONE") 3.12 Checksum File Sub String: If the receive method for the checksum is by file, then this field is populated with the substitution string used to build the Checksum file name. Example: "sst.tmpobs.SATIDs.yyyy.ddd.hhmm" (where SATIDs are multiple 3-character satellite IDs concatenated together reflecting the data in the file) Example: "sst.tmpobs.n19m02n18n17.2010.270.1807" Yes (if Integrity Check not "NONE") 3.13 Product Acquisition Strategy: Indicate how the file will be acquired by PDA. The expectation is that the product should be pushed to PD. If acquisition strategy is a form of pull, you must justify. Example: For PDA, must be one of the following: FTPPULL (PDA performs an FTP PULL), FTPPUSH (The file is FTP PUSHed to PDA), FTPSPULL (PDA performs an FTPS PULL), Yes
ESPCDataSubmissionRequestForm-Nov2016.docx