Data Collection and Submission. CONTRACTOR shall collect, maintain and enter any and all participant-level data obtained as a result of the rental assistance, case management and supportive services provided pursuant to the terms and conditions of this Agreement into the Humboldt County Homeless Management Information System for participant identification, quality assurance, data-entry, service tracking and reporting purposes.
Data Collection and Submission. CONTRACTOR shall maintain and enter any and all required participant-level data obtained as a result of the temporary shelter services provided pursuant to the terms and conditions of this Agreement into the Humboldt County Homeless Management Information System for participant identification, quality assurance, data-entry, service tracking and reporting purposes. CONTRACTOR shall adhere to any and all applicable local, state and federal security and confidentiality laws, regulations, standards and protocols regarding the collection and distribution of data entered into the Humboldt County Homeless Management Information System pursuant to the terms and conditions of this Agreement.
Data Collection and Submission a. District level and school level FSCS staff participate in quarterly data and program check-ins with Xxxxxxxx Committee staff. FSCS District director will provide oversight, support, and communications to participating schools to ensure grant deliverables are met, Exhibit D and others as identified by the State Steering Committee.
b. Participate in an annual project evaluation, which includes collecting and reporting data after review and approval from any required boards or committees. It also includes interactions with the evaluation team as they engage on-site, through observations, interviews, and focus groups. Evaluation will include, but not be limited to the data indicators required in the grant application outlined in Exhibit D.
Data Collection and Submission. (a) For so long as data submission by the Provider Licensees of data included in the Member Network Database does not require the merging of two or more data sources, the data shall be submitted by Provider Licensees to Vermont Oxford and APACHE shall not collect data directly from the Provider Licensees. Vermont Oxford shall then deliver the data to APACHE within forty-five (45) days from the end of the quarter.
(b) If Vermont Oxford does not submit data to APACHE within the time stated in this Agreement, APACHE may collect data directly from the Provider Licensees.
(c) Once data submission requires the merging of two or more data sources, APACHE shall collect data directly from the Provider Licensees.
(d) If APACHE is collecting data directly from Provider Licensees, APACHE agrees to deliver to Vermont Oxford updates to the Databases within 45 days from the end of each quarter. APACHE agrees to submit these updates in the data record format described in Section 10 or another usable format as APACHE deems appropriate.
(e) APACHE shall not collect data from Vermont Oxford members who are not Provider Licensees for use in updating the Member Network Database.
Data Collection and Submission. All data collected under the Phase I tasks shall be retained and shall be made available for submission upon request by the Department within fifteen (15) days after the end of each calendar quarter to the Department at the address listed in Paragraph 27. GIS data shall be stored and shall be submitted to the Department upon request in Environmental Systems Research Institute (ESRI)-compatible format, as specified in Paragraph 6. The CCTV data collected under Paragraph 5 shall be stored in digital format and shall be submitted to the Department upon request. All other data collected under Phase I tasks shall be formatted and stored in a relational database (Open Database Configuration compliant), such as Microsoft Access, Microsoft Excel or equivalent, and submitted to the Department upon request in a form equivalent to the example attached hereto as Appendix B. Flows shall be calculated and reported in million gallons per day (MGD), not cubic feet per second (CFS). Data shall be formatted to three (3) decimal places (x.xxx).
Data Collection and Submission. Planning shall maintain and provide EcDev with participant- level records, on a monthly basis, that detail which equity licensee received which services.
Data Collection and Submission. The survey is administered online via QuestionPro. The link to the most up to date survey is available on the credit union administrative site. We highly recommend account holders complete the survey online directly. This can be done with the credit union staff member at account opening. If a credit union chooses to distribute hard copies of the survey, credit union staff would be required to input responses into QuestionPro.
Appendix 1 Implementation Checklist
Data Collection and Submission a) Collaborators will upload their data to private folders via the PIRAT Network website (xxx.xxxxxxxxxxxx.xxx).
b) Collaborators are responsible for ensuring that data are uploaded in accordance with predefined PIRAT standards (see metadata submission forms) and submitted in a timely fashion, but at least twice a year.
c) Collaborators will inform the Data Manager of any errors, inaccuracies or necessary updates with respect to data that have been uploaded to the PIRAT Node as soon as becoming aware of such issues.
d) Array and Tracking Collaborators will provide project metadata at the initiation of the project.
e) Upon retrieval and downloading of a receiver, Array Collaborators will provide operational metadata along with intact .VRL files, as soon as is practical. Receiver operational metadata must include the following: • Deployment Date • Download Date • Retrieval Date • Deployment Coordinates • Station depth (Depth of receiver) • Station Information (e.g. FAD, topographic feature) • Station name
f) Upon deployment of a transmitter, Tracking Collaborators will provide the following metadata: • Transmitter manufacturer • Transmitter model (e.g. V9-1H, V16P-1L) • Transmitter serial number • Transmitter ID Code and code space • Estimated transmitter (battery) life • Sensor type (if any) • Scientific and common names of species on which transmitter was deployed • Release coordinates • Release date/time
g) For acoustic telemetry data held by the PIRAT Node, basic transmitter metadata are considered unrestricted and will be published as soon as is practical. The following represents a complete list of those metadata considered unrestricted: • Scientific and common names of species on which transmitter was deployed • General release location (coordinates rounded to nearest 0.1 degrees ~11 km resolution) • Release date
h) Requests may be made to treat such metadata as Restricted Data, given any ecological or economic sensitivities as identified by the Collaborator, and will be considered on a case-by-case basis by the Data Manager. Animal morphology information and ongoing locational information, in whatever capacity the instrument is capable of reporting, are considered by default to be Restricted Data.
i) Collaborators are entitled to request that their data in the PIRAT Node be initially restricted to individuals approved by project principal investigators in their sole discretion (hereinafter Restricted Data).
j) Collaborators are entitled to specify an...
Data Collection and Submission a) Collaborators will upload their data to private folders via the PIRAT Network website (xxxxxxxxxxxx.xxx).
