Naming Convention. It is not allowed to change the name of the translated file, except for adding the ISO 639-1 target language code according to the following format: [ORIGINAL NAME]_[TARGET LANGUAGE CODE].[FORMAT] (For example: "title_EN.doc" for a Word document translated into English). If revision or review is performed, "rev" (for revision) or "rwd" (for review) is added between the language code and the format ("title_ENrev.doc or "title_ENrwd.doc"). ACOLAD uses 2-letter language codes from ISO 639-1 for identification of the languages.
Naming Convention. The interface source file’s naming convention is comprised of several nodes. An example of an interface source file name as well as an explanation of each of the naming convention nodes are described below. ECAPS_FR_TIMEI_AESS_20051101 ■ DOC_DEPT_CD – The second node is the two or three byte eCAPS department id (e.g. SH - Sheriff, FR – Fire, PB - Probation, etc…) ■ DOC_CD – The third node is the four or five byte eCAPS document code (TIMEI) ■ LEGACY78 – The fourth node is a maximum of eight bytes for the department legacy system identifier (e.g. CWTAPPS, CWPAY, AESS, etc…) or external scheduling system. ■ YYYYMMDD – The fifth node is the appropriately formatted date the interface source file is generated (20051101). This date should change depending upon the frequency of the interface. It is preferred that the date be coded as the system date. In the case where multiple files are sent on the same day, the file name should be unique.
Naming Convention. It is not allowed to change the name of the translated file, except for adding the ISO 639-1 target language code according to the following format: [ORIGINAL NAME]_[TARGET LANGUAGE CODE].[FORMAT] (For example: "title_EN.doc" for a Word document translated into English). If revision or review is performed, "rev" (for revision) or "rwd" (for review) is added between the language code and the format ("title_ENrev.doc or "title_ENrwd.doc"). ACOLAD uses 2-letter language codes from ISO 639-1 for identification of the languages. Annex 1 - Linguistic Quality check (LQC) Specification Description Fundamental checks File can be opened No corruptions, garbled characters due to tag integrity, etc. are found No unintentional blank pages are left Correct target language Check for correct language locale File names File names are not altered and are consistent with client instructions Full set of files/batch All files/batches are accounted for; translated files are available in the Output Package/Delivery folder Client and project-specific rules and instructions Verify that STA, style guide, glossaries, references and instructions have been followed Open queries and answers Make sure all questions are answered and answers implemented in the translation Comments/remarks added to the translation Any necessary remarks are appropriate both in terms of format as well as wording Automated process completed Auto QA Process full tag check Used tag checker in the CAT tool Process spellcheck Used spellcheck in CAT tool or Windows spellchecker Process termcheck Used termverifier integrated in the CAT tool Unedited fuzzy matches Used QA checker in CAT tool Consistency checks Used QA checker in CAT tool General layout Clean files Verify that no tag issues, etc. remain in target file; Check for text irregularities Make sure no words are cut-off Check for suspicious capitalizations in mid-sentence Punctuation Follow the source punctuation whenever is appropriate and does not interfere with target language rules Ensure there are no missing or additional punctuation marks Check that bulleted/numbered lists follow source (or are consistent with language requirements) Spaces Verify that there are no double spaces or missing spaces between words, after trademark symbols, etc. Verify that space between number and unit are consistent based on language rules Check consistency in spaces before degree symbols based on language rules Hyphenation Check for cut-off words, suspicious line breaks, ...
Naming Convention. If the tags contain a human-readable number, it shall correspond to the marker ID number. Independent projects shall have different project indices.
Naming Convention. If the fiducial tags code a number, the use of the same tag number as the marker ID number is strongly recommended.
Naming Convention. The final ethics agreement or understanding shall be named using the employee’s name and initial(s), document type (i.e. Ethics Agreement or Ethics Understanding), and date the agreement was signed by the employee. Use hyphens or underscore between words. Do not include blank spaces in the file name. For example, Dr. Xxxxxxx Xxxxx signed his Ethics Agreement on January 1, 2015. The file will be named as follows: JonesI-Ethics-Agreement-2015-1-1.pdf Files must be saved in a format which can be opened by other users, such as pdf or Microsoft Office software, i.e., Word or Excel. PDF files from a scanner are acceptable. Document History: File Name: Q:\EMIS\SOPs\Employee-Forms\CRADA-Data-Entry.doc 2/16/08 New Document. NEO (FEPlyler) 3/13/13 Revised, per revision of data table. FEPlyler
Naming Convention. Under the 2023 QI Agreement, each QDD must separately qualify and be approved for QDD status. In applying for QDD status, the applicant must follow the naming convention described in section 2.63 of the 2023 QI Agreement on its application and, if approved as a QDD, on any other tax forms or other materials for which the QDD must be identified. This is the same naming convention that was previously described in an FAQ #13 – Certifications and Periodic Reviews for the 2017 QI Agreement.
Naming Convention. Proposals shall be limited to the separate email attachments identified by the Naming Convention and page limitations below. Subject lines shall begin with the Company’s name, e.g., “Subject: XYC Company Proposal for N00178-21-R-7000.” Multiple emails shall be identified, i.e., email 1 of 4, email 2 of 4, etc. NAMING CONVENTION Submission Identification Document Name Page Limit* Cover Letter Company_Name_CAGE_ Cover_Letter 1 Technical Proposal Company_Name_CAGE_Technical_Proposal 5 *Experience Supporting Documentation (if applicable) Company_Name_CAGE_Experience_ Supporting_Docs N/A SF33 (Signed Cover Page) Company_Name_CAGE_SF33 1 Attachment J.1 Contractor Information Spreadsheet Company_Name_CAGE_Contractor_Info N/A Attachment J.2 System for Award Management Certifications Company_Name_CAGE_ SAM_Certs N/A Attachment J. 3 Pre Award Accounting System Questionnaire Company_Name_CAGE_Acctg_Sys_Questionnaire N/A Subcontracting Plan (if applicable) Company_Name_CAGE_Subcontracting_Plan N/A *The Government will not consider any information presented beyond the last whole word within the PAGE LIMIT.
Naming Convention. Please assist us in maintaining our standards and ensure that any listing of our hotel’s name says “Viceroy Anguilla Resort & Residences” without exception.
Naming Convention. ROADWAY aa## aa = Plan sheet type (will be more than two digits in some instances) ## = Number identifying the number of drawings of the same type, i.e., 01, 02, 03, ... (Minimum of two digits are necessary.) THE USE OF A 3 DIGIT JOB IDENTIFICATION AT THE FRONT OF THE FILE NAME IS AN OPTION. For example the Alignment file for CSJ 072003102 could be named 102RAL01.dgn. FILE FOLDER STRUCTURE CSJ _Hwy Subfolders Example: CSJ_Hwy = 038907029_SH146 Subfolder = Ref_Base DocuSign Envelope ID: F2FBC84C-FAF2-48EB-B372-AE084F522D98 DocuSign Envelope ID: FF5C91A2-ECF2-41F9-B9A9-7A5C5F04D96D Legacy Contract No36-6IDP5369 PeopleSoft Contract No. 5680 Subfolder REF_BASE (References and Basemaps) Sheet Type DGN Name (First letter will be an R) Aerial Maps RA## (example: RA01.dgn) Alignments RAL## Pavement/Geometry RG## Drainage RD## Drainage Areas RDA## Profiles RP## Right of Way ROW## Traffic Control (Phase) RTC##(example: RTC02.dgn=Traf. Cont. Phase 2) Utilities RU## Bench Xxxx Layout RBM## Bore Location Layout RBO## Exist. Ground (2d) R2D## Exist. Ground (3D) R3D## Schematic RS## Schematic-Plot file RSP## Engineer Seal RES## Border File RBD## Miscellaneous RM## Subfolder GENERAL Sheet Type DGN Name (First letter will be a G) Title Sheet GT## Index of Sheets GIX## (.xls or .dgn files) Prop. Typical Sections GTY## Exist. Typ. Sections GXT## Project Layouts GPL## Permits GPM## General Notes GN## Summary Sht. Roadway GSR## Summary Sht. Stm. Swr GSS## Summary Sht. Traffic Con. GST## Summary Sht. Pv. Xxxx GSP## Estimated Quantities GQ## Subfolder ROADWAY Sheet Type DGN Name (First letter will be a P) Plan View-Roadway PVR## Plan & Profile-Roadway PP## P&P-Roadway LEFT PPL## P&P-Roadway RIGHT PPR## DocuSign Envelope ID: F2FBC84C-FAF2-48EB-B372-AE084F522D98 DocuSign Envelope ID: FF5C91A2-ECF2-41F9-B9A9-7A5C5F04D96D Legacy Contract No36-6IDP5369 PeopleSoft Contract No. 5680 P&P-Access Road PAC## Plan View-Intersection PVI## Plan & Profile-Intersection PPI## Plan & Profile-Ramps PPM## Survey Data PSR## Horiz. Align. Layout PHA## Horiz. Align. Data PHD## (.xls or .dgn files) Superelevation Tables PSU## Plan View-Widening PVW## Miscellaneous PM## Subfolder under ROADWAY BENCHMARK Sheet Type DGN Name (First letter will be a P) Benchmark Data Sheets PBM## (.xls or .dgn files) Miscellaneous PBM## Subfolder under ROADWAY BORE_ LOG Sheet Type DGN Name (First letter will be a P) Bore Log Sheets PBO## Miscellaneous POM## Subfolder RDWY_STR Sheet Type DGN Name (First letters will be PS) ...
