Purging of Files Sample Clauses

Purging of Files. Material once placed in a Licensed Educational Interpreters personnel file may be removed from such file by the mutual agreement of the Licensed Educational Interpreter and the Superintendent or his/her designee. All negative material will be removed from the file after 36 months, at the request of the Licensed Educational Interpreter if there has been no other record of occurrence in the file. Such material will also be removed if either a grievance contending that it was placed in the file without following the procedures of section 14.02 is sustained or a grievance contending that it is false is sustained.
AutoNDA by SimpleDocs
Purging of Files. Offenses will be removed from an employee’s file according to the following structure: GROUP I OFFENSES: After five (5) years from the time of the incident. GROUP II AND III OFFENSES: After two (2) years from the time of the incident, provided that no further violations/offenses occurred within that two (2) year period. Section 11:01‌
Purging of Files. 38.01 The Board agrees to purge all Service files, including a Member's personnel file of: (a) all incidents, negative or otherwise, after two (2) years (recognizing that the purpose of recording an incident is to assist a Supervisor with an annual performance appraisal); (b) all negative documentation and admonishments or informal discipline penalties two (2) years after the date of the last negative documentation, admonishment or penalty; (c) all records of any Criminal and/or Provincial Offence in which there was a withdrawal or dismissal of the charge against a Member; (d) all records of any Provincial Offence conviction two (2) years after the date of the conviction; (e) all records of any Criminal Offence five (5) years after the date of conviction where there was a conditional or absolute discharge; (f) all records of any discipline conviction under the Police Services Act two (2) years after the last discipline conviction provided the confirmed penalty (after all appeal procedures have been exhausted) does not exceed the forfeiture of forty (40) or more hours pay or leave, or forty (40) or more hours suspension without pay.
Purging of Files. Except as set out in Article 32.02, the Board agrees to purge all Service files, including a Member's personnel file of:
Purging of Files. 30.01 The Board agrees to purge all department files, including a Member's personnel file of: a) all incidents, negative or otherwise, after two (2) years (recognizing that the purpose of recording an incident is to assist a Supervisor with an annual performance appraisal); b) all negative documentation and admonishments or informal di scipline penalties two (2) years after the date of the last negative documentation, admonishment or penalty; c) all records of any Criminal and/or Provincial Offence in which there was a withdrawal or dismissal of a charge against a Member; d) all records of any Provincial Offence conviction two (2) years after the date of conviction; e) all records of any Criminal Offence five (5) years after the date of conviction where there was a conditional or absolute discharge;
Purging of Files. An employee's file may be purged of reprimands, warnings, or poor evaluations after fifteen months of continuous employment during which time no such reprimands, warnings or poor evaluations were issued.
Purging of Files. An employee may request that letters of warning be removed from his official personnel file after two (2) years and letters of reprimand be removed from his official personnel file after four (4) years. If there has been no recurrence of the intent cited in these letters or other incidents resulting in formal disciplinary action, this request will be honored by the Borough.
AutoNDA by SimpleDocs

Related to Purging of Files

  • Processing of Deposit files The use of compression is recommended in order to reduce electronic data transfer times, and storage capacity requirements. Data encryption will be used to ensure the privacy of registry escrow data. Files processed for compression and encryption will be in the binary OpenPGP format as per OpenPGP Message Format -­‐ RFC 4880, see Part A, Section 9, reference 3 of this Specification. Acceptable algorithms for Public-­‐key cryptography, Symmetric-­‐key cryptography, Hash and Compression are those enumerated in XXX 0000, not marked as deprecated in OpenPGP IANA Registry, see Part A, Section 9, reference 4 of this Specification, that are also royalty-­‐free. The process to follow for the data file in original text format is: (1) The XML file of the deposit as described in Part A, Section 9, reference 1 of this Specification must be named as the containing file as specified in Section 5 but with the extension xml. (2) The data file(s) are aggregated in a tarball file named the same as (1) but with extension tar. (3) A compressed and encrypted OpenPGP Message is created using the tarball file as sole input. The suggested algorithm for compression is ZIP as per XXX 0000. The compressed data will be encrypted using the escrow agent’s public key. The suggested algorithms for Public-­‐key encryption are Elgamal and RSA as per XXX 0000. The suggested algorithms for Symmetric-­‐key encryption are TripleDES, AES128 and CAST5 as per XXX 0000. (4) The file may be split as necessary if, once compressed and encrypted, it is larger than the file size limit agreed with the escrow agent. Every part of a split file, or the whole file if not split, will be called a processed file in this section. (5) A digital signature file will be generated for every processed file using the Registry Operator’s private key. The digital signature file will be in binary OpenPGP format as per RFC 4880 Section 9, reference 3, and will not be compressed or encrypted. The suggested algorithms for Digital signatures are DSA and RSA as per XXX 0000. The suggested algorithm for Hashes in Digital signatures is SHA256. (6) The processed files and digital signature files will then be transferred to the Escrow Agent through secure electronic mechanisms, such as, SFTP, SCP, HTTPS file upload, etc. as agreed between the Escrow Agent and the Registry Operator. Non-­‐electronic delivery through a physical medium such as CD-­‐ROMs, DVD-­‐ROMs, or USB storage devices may be used if authorized by ICANN. (7) The Escrow Agent will then validate every (processed) transferred data file using the procedure described in Part A, Section 8 of this Specification.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!