AWR/ROW Feeding Sample Clauses

AWR/ROW Feeding. The ARROW System starting point is the workflow of the Rights Information Infrastructure (RII), where each search submitted consists in a transaction, that is a set of message exchanges gathering and processing information from different data sources (TEL, VIAF, BIPs, RROs), grouped under the same Arrow Transaction ID (the unique and persistent identifier assigned by ARROW to each RII transaction) and stored in the RII repository. As described later in this document, these transactions are fundamental for the ROW history. The Arrow Transaction ID also bounds the RII repository and the ARROW Work Registry. The figure below provides a high level overview of the AWR and its relation with the RII. Figure 24: AWR/ROW Feeding The ARROW RII has been simplified representing three subsequent processes: the TEL process, the BIP process and the RRO process. In synthesis at the end of the ARROW workflow, and hence of these three processes, the RII comes out with two different outputs: the first one constitutes the bases for the RII repository, while the second one those for the AWR. When the ARROW system proceeds with the construction of the M7Q it also initialises the Work/Manifestation Identification process responsible to identify uniquely for each request coming from the library the underling work and manifestation metadata. Once this process is completed the ARROW system proceeds with the storage of these information on the ARROW Work Registry. The ARROW Work Registry (AWR) stores all the relevant pieces of information collected by the RII workflow in a structured way that allows the retrieval and use of that information in the framework of ARROW services. The gathered information mainly regards to: • Work and manifestation metadata • Authors and other contributors metadata • A set of so called ARROW Assertions on each work: Copyright status, Publishing Status and Orphan Status • Reference source (TEL, VIAF, BIPs, RROs) of work metadata, manifestation metadata, authors and contributors metadata From the above sections can be inferred that the implementation of the RII, and in particular the ARROW Work Registry (AWR), constitutes the fundament for the Registry of Orphan Works (ROW). The ROW core database in other words can be seen as a view of the AWR, result of the RII workflow. The design and set up of the ROW hence strongly depends on the AWR design. Being the ROW a subset of the AWR, the ROW starts ‘empty’ and gets populated by digitisation requests being proc...
Sample 1
AutoNDA by SimpleDocs

Related to AWR/ROW Feeding

  • Unbundled Sub-Loop Feeder 2.8.4.1 Unbundled Sub-Loop Feeder (USLF) provides connectivity between BellSouth's central office and cross-box (or other access point) that serves an end user location.

  • Advanced Services As a general matter, shall have the meaning set forth by the FCC.

  • Dining Services Meal Plan and applicable Dining Services policies are as stated herein. Any questions regarding Resident’s Meal Plan or Torero ID Card should be directed to Campus Card Services: xxxxxxxxxx@xxxxxxxx.xxx or (000) 000-0000.

  • Television Equipment Recycling Program If this Contract is for the purchase or lease of covered television equipment, then Contractor certifies that it is compliance with Subchapter Z, Chapter 361 of the Texas Health and Safety Code related to the Television Equipment Recycling Program.

  • Dark Fiber Transport Dark Fiber Transport is defined as Dedicated Transport that consists of unactivated optical interoffice transmission facilities without attached signal regeneration, multiplexing, aggregation or other electronics. Except as set forth in Section 6.9.1 below, BellSouth shall not be required to provide access to Dark Fiber Transport Entrance Facilities pursuant to this Agreement.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5.1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Unbundled Digital Loops 2.3.1 BellSouth will offer Unbundled Digital Loops (UDL). UDLs are service specific, will be designed, will be provisioned with test points (where appropriate), and will come standard with OC and a DLR. The various UDLs are intended to support a specific digital transmission scheme or service.

  • 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.

  • Shared Services 5.1.1 ETFO agrees to adopt a shared services model that will allow other Trusts to join the shared services model. The shared services office of the Trust is responsible for the services to support the administration of benefits for the members, and to assist in the delivery of benefits on a sustainable, efficient and cost effective basis.

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

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