Submission Methods Sample Clauses

Submission Methods. SECURE G2G Portal User Interface (UI) – State Government Agencies who will be scanning paper or uploading image files directly into the SECURE G2G Portal must use a token for authentication. State Government Agencies will receive recording confirmation via the UI. The UI allows user to upload a pre-scanned 300 DPI TIFF Group IV image or use a browser scanner ▇▇▇▇▇ plugin. SECURE G2G Portal Web API (API) – State Government Agencies that directly connect to the API must adhere to the XSD standard. The XML files that are uploaded must include Base64 encoded 300 DPI TIFF Group IV image files. This process does not require a user to be involved in the transfer; it is an automatic process that will be programmed by the submitter in conjunction with the County. State Government Agencies will receive recorded information via XML return batch. SECURE G2G Portal File Transfer Site (File Transfer Site) – State Government Agencies that use the File Transfer Site will use secure file transfer protocols (FTPS or SFTP) to upload XML files. The SECURE G2G Portal will process the XML files uploaded by State Government Agencies and submit the XML files to the SECURE Web API on behalf of the State Government Agencies. The XML files shall remain encrypted in transit until they reach the designated Participating County. XML files containing recording confirmations will be placed on the File Transfer Site within one Participating County business day, not including Participating County’s holidays, for State Government Agencies to retrieve. The design of the single standard XML file format for use with the File Transfer Site will include all elements required by any County for recording documents. State Government Agency will use a standard naming convention to identify the Partner or Owner Participating County with which the file is to be recorded. State Government Agency will confirm that the name of the response file reflects the same county that was identified in the submission file.

Submission Methods. You must submit your application through ▇▇▇▇▇▇.▇▇▇ unless we give you an exemption for a paper submission. See get registered. For instructions on how to submit in ▇▇▇▇▇▇.▇▇▇, see Quick Start Guide for Applicants. Make sure that your application passes the ▇▇▇▇▇▇.▇▇▇ validation checks or we may not get it. Do not encrypt, zip, or password protect any files. See Contacts and Support if you need help. This NOFO is not subject to Executive Order 12372, Intergovernmental Review of Federal Programs. No action is needed other than checking “No” on the SF-424 box 19c.

Submission Methods. SECURE ERDS User Interface (UI)– users who will be scanning paper or uploading image files directly into SECURE ERDS will receive recording confirmation via the SECURE ERDS UI. SECURE ERDS UI allows user to upload a pre-scanned 300 DPI TIFF Group IV image or use a browser scanner ▇▇▇▇▇ plugin. SECURE ERDS Web API – users that directly connect to the SECURE ERDS Web API must adhere to the XSD standard. The SECURE ERDS XML files that are uploaded must include Base64 encoded 300 DPI TIFF Group IV image files. This process does not require a user to be involved in the transfer; it is an automatic process that will be programmed by the submitter in conjunction with the County. Users will receive recorded information via XML return package. HTTPS is required for the submission of instruments. The required security framework is provided for in the SECURE ERDS software. The ERDS software shall use a minimum of 128 bit file and image encryption. Industry standard Secure Sockets Layer (SSL) and user login with password that is encrypted shall be employed. User passwords are controlled by the user and at a minimum changed at 90 day intervals to reduce security exposure. a) Endpoint Security (Authentication Token) - one token will be required for each user that will be utilizing SECURE ERDS. For use of the token to submit documents for ERDS recording electronically, please refer to the SECURE ERDS User Manual.

Submission Methods. Two submission functions are provided as part of the Pipeline Service. One submit function, batch_submit, is provided for submission of workflows which are not interactively monitored. While int_submit is provided for interactively monitored workflows, such as those created from an authoring environment e.g. the LONI Pipeline. Both functions take a sessionID, which maps a particular user to the submitted workflow and a workflow specification is provided as a SOAP attachment.