Version History definition

Version History. Date Developed: 12/1999; replaces policy of same name dated 5/03 Last Review/Revision: 12/2005, 2008, 10/2013, 5/2014, 6/2019, 8/2020 Legal Review: 7/2019, 8/2020 To define the requirements for Sponsoring Institution’s Statement of Commitment, inter-institutional affiliation agreements and program letters of agreement for the University of Arkansas for Medical Sciences College of Medicine (UAMS COM) and its Accreditation Council for Graduate Medical Education (ACMGE) sponsored residency programs.
Version History button was expected but the data are listed in the tab “Files” 2) For the content administrator it is difficult to recognize which metadata were updated for each specific version. 1) Rename tab “Files” to “Version History”. 2) Mark with a different colour the metadata that were updated. The feature needs to be tested within the BF5 environment. 3 CS5 Import RF12- The archive can import METS BF5 Blogforever METS files supplied by CERN match the METS standards. None None 4 CS5 Image files RF67- The archive fetches and stores embedded content BF5 Media such as images that are contained in a blog post are ingested into the repository and are visible to the user under the tab "Files". These media files are stored within the repository and are viewable by a user. This feature is functional on some records, but not all. Ensure embedded media files from all records are fetched and stored in the repository. 3
Version History. The version history is provided for informational purposes and lists information regarding prior versions of the regional standard.

Examples of Version History in a sentence

  • Version History Definitions of Terms Used in StandardThis section includes all newly defined or revised terms used in the proposed standard.

  • Accept Voucher XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module.

  • Accept Flight Following XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module.

  • Version History This Policy is for Invesco internal use only unless otherwise specified.

  • Accept Credit Shell XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module.

  • Click on the highlighted Funding Opportunity Number that appears and then click on the various tabs to read the Synopsis, review the Version History, read the Full Announcement, and complete the Application Package.

  • Version History Attachment 1-EOP-002-2.1 Energy Emergency Alerts IntroductionThis Attachment provides the procedures by which a Load Serving Entity can obtain capacity and energy when it has exhausted all other options and can no longer provide its customers’ expected energy requirements.

  • While it is preferable to have four VSLs for each requirement, some requirements do not have multiple “degrees” of noncompliant performance and may have only one, two, or three VSLs. Each requirement is assigned one or more VSLs in accordance with the latest approved set of VSL criteria.8 Version History: The version history is provided for informational purposes and lists information regarding prior versions of Reliability Standards.

  • Accept PNR XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module.

  • Version History: This Fast Fact was originally edited by David E Weissman MD.


More Definitions of Version History

Version History. Date Developed: 12/1999; replaces policy of same name dated 5/03 Last Review/Revision: 12/2005, 2008, 10/2013, 5/2014, 6/2019, 8/2020, 9/2021, 9/2022 Legal Review: 7/2019, 8/2020, 9/2021, 9/2022 To define the requirements for Sponsoring Institution’s (SI) Statement of Commitment, inter- institutional affiliation agreements and program letters of agreement for the University of Arkansas for Medical Sciences College of Medicine (UAMS COM) and its Accreditation Council for Graduate Medical Education (ACGME) sponsored residency/fellowship programs and ACGME Non-Standard Training programs.
Version History. Date Developed: 12/1999; replaces policy of same name dated 5/03 Last Review/Revision: 12/2005, 2008, 10/2013, 5/2014, 6/2019, 8/2020, 9/2021, 9/2022 Legal Review: 7/2019, 8/2020, 9/2021 To define the requirements for Sponsoring Institution’s (SI) Statement of Commitment, inter- institutional affiliation agreements and program letters of agreement for the University of Arkansas for Medical Sciences College of Medicine (UAMS COM) and its Accreditation Council for Graduate Medical Education (ACGME) sponsored residency/fellowship programs. organization (HMO), a medical examiner’s office, a consortium or an educational foundation.

Related to Version History

  • Dataset means the data specified in Appendix 1 (Environmental Information) to Schedule 11.2 (Management Information) as the same may be amended from time to time by the Secretary of State (acting reasonably);

  • Version of a variant means vehicles, which consist of a combination of items shown in the information package subject to the requirements in Annex VIII.

  • template version has the meaning ascribed to such term in NI 41-101 and includes any revised template version of marketing materials as contemplated by NI 41-101;

  • Fluoroscopic imaging assembly means a subsystem in which X-ray photons produce a visual image. It includes the image receptor(s) such as the image intensifier and spot-film device, electrical interlocks, if any, and structural material providing linkage between the image receptor and diagnostic source assembly.

  • Compatibility means compatibility as defined in point (10) of Article 2 of Directive (EU) 2019/770;

  • Speech or language impairment means a communication disorder, such as stuttering, impaired articulation, a language impairment, or a voice impairment, that adversely affects a child’s educational performance.

  • Configuration means State-specific changes made to the Software without Source Code or structural data model changes occurring.

  • Translucent means a substance that allows light to pass through, but does not allow an object or person to be seen through the substance.

  • Model shall refer to a particular brand of Vehicle sold by an OEM (e.g., Taurus, Tahoe, Grand Caravan).

  • Firefighter means any regular, paid or volunteer, member of a lawfully constituted fire department of a municipal corporation, township, fire district, or village.

  • Sample means a sample of blood, tissue or other biological material.

  • Interfaces means, collectively, the CAD Interface and the Channel Access Interface.

  • Protocol means, in respect of any category of object and associated rights to which this Convention applies, the Protocol in respect of that category of object and associated rights;

  • Cold Weather Alert means the notice that PJM provides to PJM Members, Transmission Owners, resource owners and operators, customers, and regulators to prepare personnel and facilities for expected extreme cold weather conditions.

  • Fluoroscopy means a technique for generating x-ray images and presenting them simultaneously and continuously as visible images. This term has the same meaning as the term "radioscopy" in the standards of the International Electrotechnical Commission.

  • Spectrum Compatibility means the capability of two (2) copper loop transmission system technologies to coexist in the same cable without service degradation and to operate satisfactorily in the presence of cross talk noise from each other. Spectrum compatibility is defined on a per twisted pair basis for specific well-defined transmission systems. For the purposes of issues regarding Spectrum Compatibility, service degradation means the failure to meet the Bit Error Ratio (BER) and Signal-to-Noise Ratio (SNR) margin requirements defined for the specific transmission system for all Loop lengths, model Loops, or loss values within the requirements for the specific transmission system.

  • Simulation means a technique to replace or amplify real experiences with guided experiences that evoke or replicate substantial aspects of the real world in a fully interactive manner.

  • Visual impairment including blindness means an impairment in vision that, even with correction, adversely affects a student's educational performance. The term includes both partial sight and blindness.

  • Systems Engineering means preparing specifications, identifying and resolving interface problems, developing test requirements, evaluating test data, and supervising design.

  • functionality means the ability of a tenderer to provide goods or services in accordance with specifications as set out in the tender documents.

  • Seaplane means an aircraft that is capable of landing and taking off on the water.

  • Project Management Report means each report prepared in accordance with Section 4.02 of this Agreement;

  • Database means the Commercial Driver Alcohol and Drug Testing Database of the Office of Driver Services of the Arkansas Department of Finance and Administration.

  • Verbal abuse means, but is not limited to, the use of derogatory terms or names, undue voice volume and rude comments, orders or responses to residents.

  • CREFC® Operating Statement Analysis Report The monthly report in the “Operating Statement Analysis Report” format substantially in the form of and containing the information called for therein for the Mortgage Loans, or such other form for the presentation of such information as may be approved from time to time by the CREFC® for commercial mortgage securities transactions generally.

  • Production Environment means a logical group of virtual or physical computers comprised within the Cloud Environment to which the Customer will be provided with access and use the purchased Cloud Application(s) in production and for its generally marketed purpose.