Physical folder structure Sample Clauses

Physical folder structure. The general folder structure of a DIP containing geodata is fully compliant with the folder structure of the E-ARK Information Packages described in section 4.1 of the Introduction to the Common Specification for Information Packages in the E-ARK Project. Within the IP, geodata can be stored within one or more representations. The following schemas show some possible structures of packages, depending on the type of geodata (raster/vector) and different possible locations of the documentation.
View Source
Physical folder structure. The folder structure of a DIP containing relational databases in SIARD format is fully compliant with the folder structure of E-ARK Information Packages described in section 4.1 of the Introduction to the Common Specification for Information Packages in the E-ARK Project. In the case where the IP contains more than one representation of the database, the difference(s) between the representations must be indicated using PREMIS metadata. Different representations should be treated as different (representation) object entities belonging to the same intellectual (object) entity. The relationship between the representations can be expressed by the semantic unit (PREMIS) “relationship”. This semantic unit includes “relationshipType” and “relationshipSubType” as semantic components. In regard to the recommendation to use PREMIS, both components’ values should be taken from a controlled vocabulary. The documentation folder should include all relevant OLAP specific data which may be: 1. A textual description (including diagrams) of the definition of the specific OLAP objects. 2. Vendor specific exports (files) of the OLAP cube. 3. Vendor specific documentation for particular software tools for creating and analysing OLAP data. 4. Software tools for creating and analysing OLAP data (always together with sufficient documentation). 5. SQL scripts or any other vendor specific scripts needed to create e.g. a star schema, or further OLAP objects. The primary data of the RDB to be delivered to the user are stored in the form of a ▇▇▇▇▇ ▇▇. The actual content of a ▇▇▇▇▇ ▇▇ within an E-ARK DIP will be a subset of the content of the ▇▇▇▇▇ ▇▇ (from a certain representation) of the AIP.
View Source

Related to Physical folder structure

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to CLEC-1 via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage Feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. 6.2.2 Data circuits (private line or dial-up) may be required between BellSouth and CLEC-1 for the purpose of data transmission. Where a dedicated line is required, CLEC-1 will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. CLEC-1 will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on a case by case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to CLEC-1. Additionally, all message toll charges associated with the use of the dial circuit by CLEC-1 will be the responsibility of CLEC-1. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the parties. All equipment, including modems and software, that is required on CLEC-1 end for the purpose of data transmission will be the responsibility of CLEC-1.

  • Physical Collocation (a) If space for Physical Collocation is immediately available at the time of Requesting Carrier’s Collo Order, Ameritech shall include in its Collo Response to Requesting Carrier notice of such immediate availability. (b) If Requesting Carrier’s requested Physical Collocation space is available, Ameritech and Requesting Carrier shall have an initial walk-through of such space within the interval specified in the Implementation Plan. Absent Ameritech’s written consent, Requesting Carrier must have at least one (1) authorized employee (i.e., in addition to any authorized vendor) at such walk- through. If during the initial walk-through, Requesting Carrier wishes to modify or change its Collo Request, Requesting Carrier must sign or initial any such modifications or changes and provide Ameritech a change order reflecting same within five (5) Business Days of such initial walk-through. If a change or modification is noted at the initial walk-through, Ameritech shall have no obligation to commence work on Requesting Carrier’s Collocation space until it receives a change order to amend the Collo Request or written confirmation that Requesting Carrier does not wish to pursue such change or modification. Failure to provide Ameritech the change order or written confirmation within the foregoing five (5) Business Day period shall be deemed a Requesting Carrier Delaying Event for the period between the expiration of such five (5) day period and the date of actual receipt by Ameritech. (c) Ameritech shall deliver to Requesting Carrier the requested space on or before the later of (i) one hundred twenty (120) days from Ameritech’s receipt of Requesting Carrier’s Collo Order, (ii) ninety (90) days from the date of the initial walk-through and (iii) such other reasonable date that the Parties may agree upon if it is not feasible for Ameritech to deliver to Requesting Carrier such space within the foregoing intervals (such date of delivery referred to as the “Delivery Date”). (d) Physical Collocation space ordered by Requesting Carrier will be made available to Requesting Carrier by Ameritech as more fully described in Section 1 of Schedule 12.12. (e) Ameritech may begin billing recurring charges for the Collocated space on the date such space is made available for occupancy (the “Occupancy Date”). Requesting Carrier shall vacate the Collocated space if either (i) Requesting Carrier (or one of its Resident Collocators, if applicable) fails to install within ninety (90) days of the Occupancy Date the equipment necessary for Interconnection with Ameritech and/or access to Ameritech’s unbundled Network Elements to be housed in such space or (ii) Requesting Carrier (or one of its Resident Collocators, if applicable) fails to Interconnect to the Ameritech network within one hundred fifty (150) days of the Occupancy Date. If Requesting Carrier is required to vacate the space pursuant to this Section 12.12.2(e), Requesting Carrier (and its Resident Collocators) shall vacate such space within ninety (90) Business Days of the earliest to occur of the foregoing events. If, after vacating a space, Requesting Carrier still requires Collocation in that Premises, Requesting Carrier shall be required to submit a new request for Collocation pursuant to the provisions of Section 12.12.1. (f) Physical Collocation will be subject to the additional rules and regulations set forth in Section 2.0 of Schedule 12.12. (g) At Requesting Carrier’s request Ameritech shall provide for APCS within three

  • Preservative-treated Wood Containing Arsenic Grantee may not purchase preservative-treated wood products containing arsenic in the performance of this Agreement unless an exemption from the requirements of Chapter 13 of the San Francisco Environment Code is obtained from the Department of the Environment under Section 1304 of the Code. The term “preservative-treated wood containing arsenic” shall mean wood treated with a preservative that contains arsenic, elemental arsenic, or an arsenic copper combination, including, but not limited to, chromated copper arsenate preservative, ammoniacal copper zinc arsenate preservative, or ammoniacal copper arsenate preservative. Grantee may purchase preservative-treated wood products on the list of environmentally preferable alternatives prepared and adopted by the Department of the Environment. This provision does not preclude Grantee from purchasing preservative-treated wood containing arsenic for saltwater immersion. The term “saltwater immersion” shall mean a pressure-treated wood that is used for construction purposes or facilities that are partially or totally immersed in saltwater.

  • Physical Fitness New Employees. New employees are required to file a medical examination report with the Director of Health Services before reporting for duty in the Des Moines schools. The employee must pay the cost of this examination given by a physician of his/her choice and reported on the form provided by the Employer.