File Upload Sample Clauses

File Upload. The Customer is responsible for the uploading of files to their Website, maintenance and backup of their content. The Cus- tomer must keep a copy of the Website for the upload of files and content in his hosting space.
Sample 1Sample 2
File Upload. The Customer is responsible for the uploading of files to their Website, maintenance and backup of their content. The Customer must keep a copy of the Website for the upload of files and content in his hosting space.
Sample 1Sample 2
File Upload. Page This page allows the stakeholder to upload files relating to the same building(s) into the session. An IFC file and/or an E57-file have to be uploaded. If both file types are uploaded an optional registration file between the two can be selected. The workflow for creating a registration file is described in 2.1.
Sample 1
File Upload. Please upload any products that have been produced or developed using funds from this program. This could include a management plan for your property, detailed project plans, CEQA documentation, project implementation maps, and other items. If no products have been produced yet, do not upload anything. There is a size limitation and file type limitation with this software. If you get an error message please reach out to xxxxx@xxxx.xxx to determine best method for submission. If you have multiple files to upload, please upload one file per response area. Additional information for implementation projects: the grantee will provide the following produced by a Registered Professional Forester or qualified resource professional (1) a topographic map containing a north arrow, legend, map scale, project location and Assessor’s Parcel number and (2) an ESRI shapefile (Zipped folder, will all files .shp, .shx, .prj, etc.) Polygon feature that depicts the outer footprint boundaries of the area on which treatment activities have been completed. The shapefile shall depict the actual project treatment area and shall be detailed/accurate enough that the GIS calculated acreage deviates from the invoiced acreage by no more than 5%. Have you spent any grant or matching funds in this reporting period? Yes No Please input $0 if no grant funds were expended this period. This value should not surpass the above noted "Amount Awarded". Please input $0 if no matching funds were expended this period. File upload of supporting documentation of any grant funds that have been expended during the reporting period. An example of this supporting documentation would be an itemized invoice with proof of payment from a contractor or Registered Professional Forester. This supporting documentation is required to issue reimbursement for grant expenditures.
Sample 1

Related to File Upload

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • File Search Reports File search reports have been obtained from each Uniform Commercial Code filing office identified with respect to such Grantor in Section 2 hereof, and such search reports reflect no liens against any of the Collateral other than those permitted under the Credit Agreement.

  • Computers All computers, hardware, software, computer upgrades and maintenance in connection therewith shall be at Owner's expense.

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

  • Customer Materials Subject to Section 4(a), all right, title and interest (including all Intellectual Property Rights) in and to the Customer Materials are owned by Customer or Customer’s suppliers.

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • Hyperlinks 12.1 You must not link to any material using or by means of the Services that would, if it were made available through the Services, breach the provisions of this Policy.

  • Website E-bidders are responsible to identify the property properly and to ensure that the details and description of the Property are correct and accurate before bidding.

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • Reports; Proxy Materials (i) PFPC Trust shall furnish to the Fund the following reports: (A) such periodic and special reports as the Fund may reasonably request; (B) a monthly statement summarizing all transactions and entries for the account of the Fund, listing each portfolio security belonging to the Fund (with the corresponding security identification number) held at the end of such month and stating the cash balance of the Fund at the end of such month. (C) the reports required to be furnished to the Fund pursuant to Rule 17f-4 of the 1940 Act; and (D) such other information as may be agreed upon from time to time between the Fund and PFPC Trust. (ii) PFPC Trust shall transmit promptly to the Fund any proxy statement, proxy material, notice of a call or conversion or similar communication received by it as custodian of the Property. PFPC Trust shall be under no other obligation to inform the Fund as to such actions or events. For clarification, upon termination of this Agreement PFPC Trust shall have no responsibility to transmit such material or to inform the Fund or any other person of such actions or events.