ROW History Sample Clauses

ROW History. ROW history is the functionality that allows a country ROW manage operating on the centralised infrastructure, to see for a selected work: • the current situation of the selected work: the work rights status, the reference sources of the work rights status19, the work metadata as well as the current set of manifestations associated to it • How the work metadata changed over time • How the work status changed over time and the reference sources of this information 19 Any change of status that is not output of a new RII transaction and therefore not linked to a ARROWTransactionID assigned by the front end, needs to be assigned with its own Transaction ID and linked to the ARROWWorkID. • How the list of the manifestations associated to a work changed over time This functionality is a key element of the ROW, as according to the HLG guidelines on diligent search on orphan works, once a diligent search is conducted it is necessary to gather evidence that the search has been done, documenting also the sources of information consulted during the search. In order to document all the processes in the ARROW workflow and the results obtained, ARROW implements mechanisms to store information, including records of the searches performed along the whole workflow and their sources. History is designed to provide evidence of all previous diligent searches conducted for a work and the main changes occurred over time, in terms of: • Work rights status (Publishing Status, Copyright Status, Orphan Status) • Work and related Manifestation as well as the associated metadata. This is possible thanks to the use of unique identifiers to identify and track works and transactions involving the work. In fact, each ARROWWorkId (in the future each ISTC) is associated to one or more ARROWTransactionId that univocally identifies a search process along the whole ARROW workflow. Keeping this relation enables an easy retrieval and display of al the results obtained in the different steps of the workflow, for each transaction (search) associated to the work. Once the work is selected by the user, it may be possible to see all the responses obtained by different data providers by exploiting the ARROWTransactionId. Beside the RII transactions, the history shall maintain also evidence of changes in the work rights status (from “ProbablyOrphan” to “NotOrphan”) triggered by the claiming process or in the future by an external diligent searches: these changes of status need to be assigned with thei...
AutoNDA by SimpleDocs

Related to ROW History

  • History The two Boards approved a "Proposed Plan to Further Simplify and Facilitate Transfer of Credit Between Institutions" at their meetings in February 1996. This plan was submitted as a preliminary report to the Joint Legislative Education Oversight Committee in March 1996. Since that time, significant steps have been taken toward implementation of the transfer plan. At their April 1996 meetings, the Boards appointed their respective sector representatives to the Transfer Advisory Committee to direct, coordinate, and monitor the implementation of the proposed transfer plan. The Transfer Advisory Committee membership is listed in Appendix D. Basic to the work of the Transfer Advisory Committee in refining transfer policies and implementing the transfer plan has been the re-engineering project accomplished by the North Carolina Community College System, especially common course names, numbers, credits, and descriptions. The Community College Combined Course Library includes approximately 3,800 semester-credit courses written for the associate degree, diploma, and certificate programs offered in the system. Colleges select courses from the Combined Course Library to design all curriculum programs. Of approximately 700 arts and sciences courses within the Combined Course Library, the faculty and administrators of the community colleges recommended approximately 170 courses as appropriate for the general education transfer core. The Transfer Advisory Committee then convened a meeting on May 28, 1996, at which six University of North Carolina faculty in each of ten general education discipline areas met with six of their professional counterparts from the community colleges. Through a very useful and collegial dialog, these committees were able to reach consensus on which community college courses in each discipline were acceptable for transfer to University of North Carolina institutions as a part of the general education core. This list of courses was distributed to all University of North Carolina and community college institutions for their review and comments. Considering the recommendations of the general education discipline committees and the comments from the campuses, the Transfer Advisory Committee established the list of courses that constitutes the general education transfer core. This general education core, if completed successfully by a community college student, is portable and transferable as a block across the community college system and to all University of North Carolina institutions. With the establishment of the general education core as a foundation, joint academic disciplinary committees were appointed to draw up guidelines for community college curricula that will prepare students for intended majors at University of North Carolina institutions. Each committee consisted of representatives from each UNC institution offering such major programs and eight to ten representatives from community colleges. The Transfer Advisory Committee distributed the pre- majors recommended by the faculty committees to all University of North Carolina and community college institutions for their review and comments. Considering the faculty committee recommendations and the campus comments, the Transfer Advisory Committee established pre-majors which have significant numbers of transfers from the community colleges to the University of North Carolina institutions. The special circumstances surrounding transfer agreements for associate in applied science programs, which are not designed for transfer, require bilateral rather than statewide articulation. Special circumstances include the different accreditation criteria for faculty in transfer and non-transfer programs, the different general education requirements for transfer and non-transfer programs, and the workforce preparedness mission of the technical/community college AAS programs. A major element in the proposed transfer plan adopted by the two boards in February 1996 is the transfer information system. Simultaneously with the work being done on the general education and professional specialization (major) components of the transfer curriculum, the joint committee on the transfer information system laid out a plan, approved by the Boards of The University of North Carolina and the North Carolina Community College System, "to provide students with accurate and understandable information regarding the transfer of credits...[and] to increase the adequacy and availability of academic counseling for students who are considering a college transfer program." In addition to the printed publications currently being distributed to students, transfer counselors, admissions directors, and others, an electronic information network provides (1) electronic access to the articulation database which will include current transfer policies, guidelines, and on-line catalogs for public post-secondary institutions; (2) computerized common application forms, which can be completed and transmitted electronically along with transcripts and other education records; and (3) an electronic mail network for transfer counselors and prospective transfer students. Access to the e-mail network is available in the transfer counselors' offices and other selected sites on campuses. The final element of the transfer information system is the Transfer Student Academic Performance Report. This report, recently refined with suggestions from community college administrators, is sent annually to each community college and to the State Board of Community Colleges. These data permit the rational analysis of transfer issues and are beneficial to students and to educational and governmental decision-makers. This performance report provides the important assessment component necessary for evaluating and improving the transfer process. Appendix C Transfer Advisory Committee Procedures Articulation between the North Carolina Community College System and The University of North Carolina is a dynamic process. To ensure the currency of the Comprehensive Articulation Agreement (CAA), occasional modifications to the CAA may be necessary. These modifications may include the addition, deletion, and revision of courses on the transfer list, development and/or revision of pre- majors, and changes in course designation (i.e. additions to UGETC list or changing a course from general education to elective). The TAC will receive requests for modification only upon the recommendation of the chief academic officer of the NCCCS or UNC. Additions, deletions, and modifications may be subject to faculty review under the direction of the TAC. Because the modification process involves faculty and administrative review, this process may require up to 12 months for final action. Additions to the Universal General Education Transfer Component Courses currently included on the approved transfer course list may be considered for inclusion as a Universal General Education Transfer Component (UGETC) course through the following procedures:

  • EXTRADITION Treaty on extradition. Signed at Buenos Aires June 10, 1997; entered into force June 15, 2000. TIAS ; 2159 UNTS 129. FINANCE Agreement relating to investment guaranties under section 413(b)(4) of the Mutual Security Act of 1954, as amended. Signed at Buenos Aires December 22, 1959; entered into force provisionally December 22, 1959; definitively May 5, 1961. 12 UST 955; TIAS 4799; 411 UNTS 41. Agreement regarding the consolidation and re- scheduling of certain debts owed to, xxxxxx- xxxx by or insured by the United States Gov- ernment and its agencies, with annexes. Signed at Buenos Aires April 8, 1986; entered into force May 19, 1986. NP Swap agreement between the United States Treasury and the Central Bank of the Argen- tine Republic/Government of the Argentine Republic, with related letter and amendment. Signed at Washington and Buenos Aires Feb- ruary 23, 1988; entered into force February 23, 1988. TIAS Swap agreement between the United States Treasury, the Central Bank of the Argentine Republic/Government of the Argentine Repub- lic, with memorandum of understanding. Signed at Washington and Buenos Aires Octo- ber 19, 1988; entered into force October 19, 1988. TIAS Agreement regarding the consolidation and re- scheduling or refinancing of certain debts owed to, guaranteed by, or insured by the United States Government and its agencies, with annexes. Signed at Buenos Aires Decem- ber 14, 1989; entered into force January 22, 1990. NP Agreement regarding the consolidation and re- scheduling of certain debts owed to, xxxxxx- xxxx by, or insured by the United States Gov- ernment and its agencies, with annexes. Signed at Buenos Aires December 5, 1990; entered into force January 16, 1991. NP Agreement regarding the consolidation and re- scheduling or refinancing of certain debts owed to, guaranteed by or insured by the United States Government and its agencies, with annexes. Signed at Washington December 6, 1991; entered into force February 10, 1992. NP Agreement regarding the consolidation and re- scheduling of certain debts owed to, xxxxxx- xxxx by or insured by the United States Gov- ernment and its agencies, with annexes. Signed at Washington January 13, 1993; entered into force March 8, 1993. NP Agreement regarding the reduction of certain debts related to foreign assistance owed to the Government of the United States and its agen- cies, with appendices. Signed at Washington and Buenos Aires January 13 and 15, 1993; entered into force February 14, 1993. NP

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Screening 3.13.1 Refuse containers located outside the building shall be fully screened from adjacent properties and from streets by means of opaque fencing or masonry walls with suitable landscaping.

  • Litigation History There shall be no consistent history of court/arbitral award decisions against the Tenderer, in the last (Specify years). All parties to the contract shall furnish the information in the appropriate form about any litigation or arbitration resulting from contracts completed or ongoing under its execution over the year’s specified. A consistent history of awards against the Tenderer or any member of a JV may result in rejection of the tender.

  • SAMPLE (i) Unless agreed otherwise, wheeled or track lay- ing equipment shall not be operated in areas identified as needing special measures except on roads, landings, tractor roads, or skid trails approved under B5.1 or B6.422. Purchaser may be required to backblade skid trails and other ground disturbed by Purchaser’s Opera- tions within such areas in lieu of cross ditching required under B6.6. Additional special protection measures needed to protect such known areas are identified in C6.24.

  • Tax Examinations Abroad 1. A Contracting Party may allow representatives of the competent authority of the other Contracting Party to enter the territory of the first-mentioned Party to interview individuals and examine records with the written consent of the persons concerned. The competent authority of the second-mentioned Party shall notify the competent authority of the first-mentioned Party of the time and place of the meeting with the individuals concerned.

  • Geometric visibility The visibility of the illuminating surface, including its visibility in areas which do not appear to be illuminated in the direction of observation considered, shall be ensured within a divergent space defined by generating lines based on the perimeter of the illuminating surface and forming an angle of not less than 5° with the axis of reference of the headlamp. The origin of the angles of geometric visibility is the perimeter of the projection of the illuminating surface on a transverse plane tangent to the foremost part of the lens of the headlamp.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Scoring The number of routes each company operates (Route # 0001-2999, 8000-8199) will be multiplied by 2 to determine the daily number of trips. (Only accidents, breakdowns and service reports related to routes falling in this range will be used for the evaluation). The daily number of trips will be multiplied by 175 to arrive at the annual number of trips. The number of accidents, breakdowns and service complaints will be divided by the total number of trips to calculate a percent figure. Each company’s percentage will be compared to the total average. See below for a sample. BUS COMPANY NUMBER OF TOTAL BKDN PERCENT ACCIDENTS PERCENT2 SERVICE PERCENT3 ROUTES TRIPS BKDN ACCIDENTS REPORTS COMPLAINTS TO TRIPS TO TRIPS TO TRIPS A 360 58680 3 0.01% 27 0.05% 46 0.08% B 48 7824 3 0.04% 4 0.05% 39 0.50% C 123 20049 11 0.05% 9 0.04% 27 0.13% D 91 14833 0.00% 10 0.07% 11 0.07% E 124 20212 20 0.10% 19 0.09% 18 0.09% TOTALS 746 121598 37 0.03% 69 0.06% 141 0.12% To score, if a company’s percentage is less than or equal to the total percentage for that category, the company will be awarded 6 points per category. Percentages greater than the total percentage for each distinct category (Accident, Breakdown, Service Complaints) will be scored according to the following scale: Vendor Category Percent Points Less than-Equal to Ave. 6 points 0-3% above average 5 points 4-7% above average 4 points 5-8% above average 3 points 9-12% above average 2 points 13-16% 1 points Greater than 17% 0 points Example: Company A had a lower percent of breakdowns than the average total, and would receive 6 points for breakdowns. If a company has a higher percentage than the average total, 0 point will be added to their score. Company B would not receive 6 points for breakdowns. The same calculation would be performed for accidents and service complaints. Any circumstance whereby a Breakdown or Accident is found by PTS to be ‘Non Reported’ by vendor within the required timeframe (see G-36) will count as (20) ‘Reported’ instances for the purpose of this Contractor Evaluation Scoring.

Time is Money Join Law Insider Premium to draft better contracts faster.