ARROW workflow Clause Samples
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;
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:
Step 1. Library submits a query to ARROW Step 2. ARROW “forwards” the query to TEL