{"id":8904,"date":"2024-06-27T08:00:16","date_gmt":"2024-06-27T14:00:16","guid":{"rendered":"https:\/\/www.research.colostate.edu\/osp\/?p=8904"},"modified":"2024-06-27T08:00:16","modified_gmt":"2024-06-27T14:00:16","slug":"file-naming-conventions-in-kr-pd-2","status":"publish","type":"post","link":"https:\/\/www.research.colostate.edu\/osp\/2024\/06\/27\/file-naming-conventions-in-kr-pd-2\/","title":{"rendered":"File Naming Conventions in KR PD"},"content":{"rendered":"<p>OSP would like everyone\u2019s help naming files uploaded to KR PD records.<\/p>\n<p>Documents loaded to a KR PD record in any of the Attachments sections should be named and described so that it is easy to identify the content of the file from the filename. While the associated description field in KR PD can also be helpful, an accurate and descriptive file name is crucial. Many of the files that are uploaded to KR PD records are stored for future reference in OSP\u2019s internal document management system, FileHold, where filenames are important for content and project management.<\/p>\n<p>When naming a file that will be attached in KR PD, please use the KR PD number and a short, accurate description for the filename. For instance, the proposal solicitation would be named \u201cKR PD number_Solicitation,\u201d whereas the budget justification would be named \u201cKR PD number_BudgetJustification.\u201d Referring to the KR PD record number and succinctly describing the document aids in the quick retrieval of information when requested. If there are multiple subawards in a proposal, please be sure to indicate the name of the subaward entity and what the document is (e.g. KR PD number_Subaward entity name_SOW).<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.research.colostate.edu\/osp\/wp-content\/uploads\/sites\/5\/2024\/06\/Picture1.png\" alt=\"\" width=\"1024\" height=\"381\" \/><\/p>\n<p>Succinct file names that include the KR PD record number aid in:<\/p>\n<ul>\n<li>Knowing the content of a document without having to open it<\/li>\n<li>Filtering documents quickly using search\/filter functions<\/li>\n<li>Storing documents related to a single project without losing context<\/li>\n<li>Browsing a file to check for missing documents<\/li>\n<li>Ensuring documents are filed internally with the correct project<\/li>\n<\/ul>\n<p>Below are examples of file naming conventions that are most helpful for quick retrieval of information.<\/p>\n<table width=\"642\">\n<tbody>\n<tr>\n<td width=\"282\"><strong>Document Type<\/strong><\/td>\n<td width=\"360\"><strong>Naming Convention<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"282\">CSU SOW\/Project Description<\/td>\n<td width=\"360\">KR PD number_SOW<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">CSU Budget in Sponsor Form\/for Proposal<\/td>\n<td width=\"360\">KR PD number_Budget<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">CSU Budget Justification<\/td>\n<td width=\"360\">KR PD number_Budget Justification<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">CSU Cost Share Commitment<\/td>\n<td width=\"360\">KR PD Number_Cost Share Commitment ICF<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">RFP\/Solicitation\/Guidelines<\/td>\n<td width=\"360\">KR PD number_Guidelines<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">Subrecipient Commitment<\/td>\n<td width=\"360\">KR PD number_Sub Entity name_Commitment Form<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">Subrecipient SOW<\/td>\n<td width=\"360\">KR PD number_Sub Entity name_SOW<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">Subrecipient Budget<\/td>\n<td width=\"360\">KR D number_Sub Entity name_Budget<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">Subrecipient Budget Justification<\/td>\n<td width=\"360\">KR PD number_Sub Entity name_Budget Justification<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">IACUC\/IRB\/IBC Approval<\/td>\n<td width=\"360\">KR PD number_IACUC IRB IBC_Approval<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">NASA China Affiliations Certification<\/td>\n<td width=\"360\">KR PD number_Person Name_China Certification<\/td>\n<\/tr>\n<tr>\n<td width=\"282\">Waiver of Indirect Costs<\/td>\n<td width=\"360\">KR PD number_IDC Waiver<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>While the attachment type and descriptions provided in KR PD are helpful for describing the attached content, the type and descriptions do not follow the document when it is added to OSP\u2019s filing system, FileHold. For example, if an attached file is named \u201cSOW,\u201d and the description reads, \u201cScope of Work for subawardee Smith at CU-Boulder,\u201d the description cannot be copied to FileHold. A better naming convention would be, \u201cKR PD number_SubrecipientName_SOW.\u201d<\/p>\n<p>We would like to thank everyone for your help with naming files when uploading them to KR PD.\u00a0 Following the above naming conventions will greatly improve the efficiency of managing documents from proposal through award.<\/p>\n<p><em>Throwback Blog by Bill Moseley, Pre-Award Manager, OSP. Original Blog, \u201cFile Naming Conventions in KR PD\u201d, January 6, 2021, by Julie Harvey, Subcontract Administrator, and Tricia Callahan, former Senior Research Education and Information Officer, OSP<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>OSP would like everyone\u2019s help naming files uploaded to KR PD records. Documents loaded to a KR PD record in any of the Attachments sections should be named and described so that it is easy to identify the content of the file from the filename. While the associated description field in KR PD can also [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-8904","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/posts\/8904","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/comments?post=8904"}],"version-history":[{"count":0,"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/posts\/8904\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/media?parent=8904"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/categories?post=8904"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.research.colostate.edu\/osp\/wp-json\/wp\/v2\/tags?post=8904"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}