Permanency Files. III.10.7.1 Candidates are responsible for assembling their own permanency file and for delivering it to the Library Permanency Committee by the date specified in III.10.5.2.
Permanency Files Sample Clauses
Related to Permanency Files
Electronic Files a. It is the Buyer's responsibility to maintain a copy of any original Electronic File provided by the Buyer.
Grievance Files Written grievances and responses will be maintained separately from the employee’s personnel file.
Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to <<customer_name>> 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.
Personnel Files An employee, or his/her certified representative with the written consent of the employee, may inspect that employee's personnel file with the exception of all material obtained from other employers and agencies at the time that employee was hired. An employee shall be advised of, and entitled to read, any written statement by the employee's supervisor or departmental Management regarding his/her work performance or conduct if such statement is to be placed in his/her personnel file. The employee shall acknowledge that he/she has read such material by affixing his/her signature on the copy to be filed, with the understanding that such signature merely signifies that he/she has read the material to be filed but does not necessarily indicate agreement with its content. If the employee refuses to sign, the supervisor shall note his/her refusal on the copy to be filed along with the supervisor's signature and the signature of a witness to the employee's refusal to sign. The employee may file a grievance regarding any such document within the prescribed time limits of the grievance procedure. If the employee fails to file a grievance within the designated time limits, the document becomes part of the official file. If the employee does file a grievance within the designated time limits, said document shall not be placed in the official file nor referenced in any Performance Evaluation or Appraisal of Promotability until the grievance procedure or civil service appeal rights have been exhausted. Grievances filed under this provision shall not be subject to the Arbitration provisions of the Grievance Procedure unless they involve violation of a specific provision of this agreement. Management agrees that no properly used full paid sick leave used in the twelve months immediately prior to an Appraisal of Promotability or a Performance Evaluation will be referenced on such forms. The employee may attach his/her statement to any document within twenty (20) business days if he/she chooses not to file a grievance regarding such document or within ten (10) business days following final determination if he/she has filed a grievance regarding such document. On reviewing his/her personnel file, an employee may request and have any written warnings issued more than one year prior placed in an envelope and sealed in his/her personnel file except as such may be a part of an official permanent record. On the face of the sealed envelope it shall read "The contents herein shall be disclosed only upon written consent of the subject employee or by subpoena or other legal process from a public body of competent jurisdiction." The date the contents of the sealed envelope will be destroyed shall also appear on the face of envelope. That date shall be two (2) years from the date of issue of the documents in the sealed envelope. An employee on reviewing his/her personnel file, may request and have any written warnings or reprimand(s) issued more than two (2) years prior removed from his/her personnel file except as such may be a part of an official permanent record. All departments employing peace officers covered by the Peace Officers Bill of Rights shall comply with its provisions.
COMPUTER GRAPHICS FILES The Engineer agrees to comply with Attachment G, Computer Graphics Files for Document and Information Exchange, if determined by the State to be applicable to this contract.
Project Records As further described below, Project records include but are not limited to Grantee, financial, and voucher records. All Project records must be retained for a period of three (3) years after final payment under this Grant. All Project records are subject to audit pursuant to Section P of this Grant Agreement. Upon completion of the third year of record retention, the Grantee shall submit all Project records to CARB. Hardcopy of electronic records are suitable. Acceptable forms of electronic media include hard drives, CDs, DVDs, and flash drives. Other forms of electronic media may be allowed based on prior written concurrence from CARB.
ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to Image Access 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 (one hundred seventy-five (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 (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
Client Records 26.2.1 CONTRACTOR shall prepare and maintain accurate and complete records of clients served and dates and type of services provided under the terms of this Contract in a form acceptable to ADMINISTRATOR.
Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.
Physical Safeguards USAC and the Department agree to maintain all automated matching records in a secured computer environment that includes the use of authorized access codes to restrict access. Those records will be maintained under conditions that restrict access to persons who need them for official duties related to the matching process. The user’s supervisor will ensure that USAC or the Department are notified when a user has departed or duties have changed so the user no longer needs access to the system, to ensure timely deletion of the user’s account and password.
