Common use of Error Reconciliation Clause in Contracts

Error Reconciliation. The Archive will report any problems or errors with file integrity, file name, checksum validation, or other errors that inhibit the data ingest and archive to the Provider. A new corresponding submission manifest will be required for files re-submitted by the Provider. Receipt Confirmation: The Archive will provide an inventory of the data ingested once it is completed or as requested by the Provider. Quality Assurance: No quality checks on the submitted data are planned. Archive File Packaging: Archival Information Packages (AIPs) will be organized into one AIP per platform type. The data files will be exact duplicates of the data that was posted to the FTP server. Archive Storage Archive File Type Name: Descriptive name for this archive file type Archive File Attributes/IDs: Archive attributes of each archived file type. Attribute/ID Type Value None Attribute/ID value Archive Updates New, never-before seen data files will be archived based on which buoy they are: each buoy will be assigned an accession number. New, data from a previously submitted buoy: The AIP for that buoy will be updated (NCEI's major-revision) with the new data file. Revised, data that was previously submitted that needs to be updated: If the naming conventions match and the checksums do not match, then the most recent submission of that file will be assumed to be the latest and greatest submission and will replace the previous file.

Error Reconciliation. The Archive will report any problems or errors with file integrity, file name, checksum validation, or other errors that inhibit the data ingest and archive to the Provider. A new corresponding submission manifest will be required for files re-submitted by the Provider. Receipt Confirmation: The Archive will provide an inventory of the data ingested once it is completed or as requested by the Provider. Quality Assurance: No quality checks on the submitted data are planned. Archive File Packaging: Archival Information Packages (AIPs) will be organized into one AIP per platform typestation. The data files will be exact duplicates of the data that was posted to the FTP SCCOOS server. Archive Storage Archive File Type Name: Descriptive name for this archive file type Archive File Attributes/IDs: Archive attributes of each archived file type. Attribute/ID Type Value None Not Applicable Attribute/ID value Archive Updates New, never-before seen data files will be archived based on which buoy station they are: each buoy station will be assigned an accession number. New, data from a previously submitted buoystation: The AIP for that buoy station will be updated (NCEI-MD's major-revision) with the new data file. Revised, data that was previously submitted that needs to be updated: If the naming conventions match and the checksums do not match, then the most recent submission of that file will be assumed to be the latest and greatest submission and will replace the previous file.

Error Reconciliation. The Archive will report any problems or errors with file integrity, file name, checksum validation, or other errors that inhibit the data ingest and archive to the Provider. A new corresponding submission manifest will be required for files re-submitted by the Provider. Receipt Confirmation: The Archive will provide an inventory of the data ingested once it is completed or as requested by the Provider. Quality Assurance: No quality checks on the submitted data are planned. Archive File Packaging: Archival Information Packages (AIPs) will be organized into one AIP per platform typeplatform. The data files will be exact duplicates of the data that was posted to the FTP server. Archive Storage Archive File Type Name: Descriptive name for this archive file type Archive File Attributes/IDs: Archive attributes of each archived file type. Attribute/ID Type Value None Attribute/ID value Archive Updates New, never-before seen data files will be archived based on which buoy they are: each buoy will be assigned an accession number. New, data from a previously submitted buoy: The AIP for that buoy will be updated (NCEINODC's major-revision) with the new data file. Revised, data that was previously submitted that needs to be updated: If the naming conventions match and the checksums do not match, then the most recent submission of that file will be assumed to be the latest and greatest submission and will replace the previous file.

Error Reconciliation. The Archive will report any problems or errors with file integrity, file name, checksum validation, or other errors that inhibit the data ingest and archive to the Provider. A new corresponding submission manifest will be required for files re-submitted by the Provider. Receipt Confirmation: The Archive will provide an inventory of the data ingested once it is completed or as requested by the Provider. Quality Assurance: No quality checks on the submitted data are planned. Archive File Packaging: Archival Information Packages (AIPs) will be organized into one AIP per platform type. The data files will be exact duplicates of the data that was posted to the FTP server. Archive Storage Archive File Type Name: Descriptive name for this archive file type Archive File Attributes/IDs: Archive attributes of each archived file type. Attribute/ID Type Value None Attribute/ID value Archive Updates New, never-before seen data files will be archived based on which buoy they are: each buoy will be assigned an accession number. New, data from a previously submitted buoy: The AIP for that buoy will be updated (NCEI's major-revision) with the new data file. Revised, data that was previously submitted that needs to be updated: If the naming conventions match and the checksums do not match, then the most recent submission of that file will be assumed to be the latest and greatest submission and will replace the previous file.

Error Reconciliation. The Archive will report any problems or errors with file integrity, file name, checksum validation, or other errors that inhibit the data ingest and archive to the Provider. A new corresponding submission manifest will be required for files re-submitted by the Provider. Receipt Confirmation: The Archive will provide an inventory of the data ingested once it is completed or as requested by the Provider. Quality Assurance: No quality checks on the submitted data are planned. Archive File Packaging: Archival Information Packages (AIPs) will be organized into one AIP per platform typeplatform. The data files will be exact duplicates of the data that was posted to the FTP server. Archive Storage Archive File Type Name: Descriptive name for this archive file type Archive File Attributes/IDs: Archive attributes of each archived file type. Attribute/ID Type Value None Attribute/ID value Archive Updates New, never-before seen data files will be archived based on which buoy they are: each buoy will be assigned an accession number. New, data from a previously submitted buoy: The AIP for that buoy will be updated (NCEINODC's major-revision) with the new data file. Revised, data that was previously submitted that needs to be updated: If the naming conventions match and the checksums do not match, then the most recent submission of that file will be assumed to be the latest and greatest submission and will replace the previous file.

Error Reconciliation. The Archive will report any problems or errors with file integrity, file name, checksum validation, or other errors that inhibit the data ingest and archive to the Provider. A new corresponding submission manifest will be required for files re-submitted by the Provider. Receipt Confirmation: The Archive will provide an inventory of the data ingested once it is completed or as requested by the Provider. Quality Assurance: No quality checks on the submitted data are planned. Archive File Packaging: Archival Information Packages (AIPs) will be organized into one AIP per platform typestation. The data files will be exact duplicates of the data that was posted to the FTP SCCOOS server. Archive Storage Archive File Type Name: Descriptive name for this archive file type Archive File Attributes/IDs: Archive attributes of each archived file type. Attribute/ID Type Value None Attribute/ID value Archive Updates New, never-before seen data files will be archived based on which buoy station they are: each buoy station will be assigned an accession number. New, data from a previously submitted buoystation: The AIP for that buoy station will be updated (NCEI-MD's major-revision) with the new data file. Revised, data that was previously submitted that needs to be updated: If the naming conventions match and the checksums do not match, then the most recent submission of that file will be assumed to be the latest and greatest submission and will replace the previous file.