ARROW workflow Sample Clauses

ARROW workflow. The ARROW workflow has been defined through an iterative process and will still be adjusted and optimized during the development phase and in accordance with experience in the pilot phase. It reflects the consensus found in each country by national stakeholders. Here is a short description of the main steps in workflow A as implemented in the Alpha release2 and to which the messages described below conform: Step 1: Library submits a query to ARROW which acknowledges receipt;
Sample 1
AutoNDA by SimpleDocs
ARROW workflow. The purpose of ARROW is to support libraries wishing to digitize a book and use it. The Rights information Infrastructure will facilitate the process of carrying out a diligent search by means of a comprehensive system. This system will be able to provide the libraries with answers as to whether they are allowed to digitize a book or not. The information needed to fulfill the purpose includes: ■ the rights status of the work: if it is in public domain or copyrighted, if it is in print or out of print. ■ the rightholders of the work: publishers, authors and other contributors, or their agents, that is organisations entitled to manage rights on behalf of rightholders. ■ terms and conditions under which digitisation and use are allowed Information needed is stored in the systems of different organizations for their own specific purposes. The key players identified so far are: The European Library, Books in Print databases, Reprographic Rights Organizations systems, Authority Files (VIAF) The diagram below shows the basic system workflow of ARROW as an overview. It starts from a library as a potential user that wishes to digitise a book and shows the flow that the Arrow system has to build to provide a response. Several actors concur to this definition; those identified so far represent the Metadata providers of the system. In the workflow below the providers that have been taken into account are the domain- specific ARROW partners (libraries as provider (TEL), BIP providers and RROs on a European level. The finalisation of the workflow is still in progress and depends to a certain degree on given external elements as well as on further external developments (e.g. the provision of adequate clustering algorithms). Thus the workflow will still have to be adjusted and optimized during the development phase and according to the experiences reached in the pilot phase. Description of the steps in the workflow:
Sample 1
ARROW workflow. Sample Step 1: Library submits query to ARROW Create a library account. The account management is not part of this paper. It could be done partly in the front end systems (i.e. for personal user accounts in the single search interactive portal) or/and as part of the core ARROW system, based on given protocol authentication, federation with TEL or an ARROW internal account and subscription system. The library would send a list of book records to the bulk front end system (1) or would ask for a single item search on the interactive web portal (2). The ARROW system gets the request on an item by item query on the ARROW WebService.
Sample 1

Related to ARROW workflow

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • FABRICATION Making up data or results and recording or reporting them.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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