AWR/ROW Data Model Sample Clauses

AWR/ROW Data Model. The following figure represents a logic view of some of the possible relations considered in designing the ROW, according to the requirements for the ROW gathered so far and can be extended with additional entities and relation if necessary. A brief description of the model is provided starting from the WORK entity which is the ROW main one. This entity contains an ARROW_WORK_ID which uniquely identifies it in the AWR. Each work is also related to a list of identifiers of the same work (WORK_IDENTIFIER entity). Such list will initially contain the TEL Work ID and may further contain the ISTC assigned to the work. Other attributes of the WORK entity are the PublishingStatus, CopyrightStatus, OrphanStatus. They correspond to the last work status values obtained for that work as a consequence of an ARROW transaction. Such transaction is modeled by the ARROW_TRANSACTIONS entity and the relation between them is enabled by the ARROW_TRANSACTION_Id. Work status and metadata may change due to different workflows such as: RII workflow handling library requests or claiming workflow on orphan works upon validation of in charge organizations. In order to express this scenario the ARROW_TRANSACTIONS entity is designed as a generalization of a RII transaction or claim transaction by the means of the TRANSACTION_TYPE attribute. This choice allows to scale to further workflows that may be added to the ARROW system influencing the above work data. REFERENCE_PARTY entity models the role of the different organizations playing a role in the ARROW system, related both to the RII and to the ROW. For example it contains the necessary information for identifying an RRO or a BIP as well as a ROW Manager. A relation between the ARROW_TRANSACTION entity and the REFERENCE_PARTY entity exists since the ARROW System always needs to know the responsible organization for the particular transaction. For example the RRO declaring work status data (RII_TRANSACTION) or confirming claiming data (CLAIM_TRANSACTION). In order to maintain the work history, the WORK_HISTORY entity is provided. This entity contains an ARROW_WORK_ID, the work status information, the ARROW_TRANSACTION_ID and a DATE. Each time an ARROW_TRANSACTION is performed, this entity is enriched with the previous work information (the ones represented by the WORK entity). The WORK entity itself is updated with the most recent information. There is obviously a relation between the WORK entity and the WORK_HISTORY entity that ena...
Sample 1
AutoNDA by SimpleDocs

Related to AWR/ROW Data Model

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements. Acknowledging your access and consent to receive and sign documents electronically To confirm to us that you can access this information electronically, which will be similar to other electronic notices and disclosures that we will provide to you, please confirm that you have read this ERSD, and (i) that you are able to print on paper or electronically save this ERSD for your future reference and access; or (ii) that you are able to email this ERSD to an email address where you will be able to print on paper or save it for your future reference and access. Further, if you consent to receiving notices and disclosures exclusively in electronic format as described herein, then select the check-box next to ‘I agree to use electronic records and signatures’ before clicking ‘CONTINUE’ within the DocuSign system. By selecting the check-box next to ‘I agree to use electronic records and signatures’, you confirm that: • You can access and read this Electronic Record and Signature Disclosure; and • You can print on paper this Electronic Record and Signature Disclosure, or save or send this Electronic Record and Disclosure to a location where you can print it, for future reference and access; and

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient.

  • Client Software You may only use the client software with the ERP solution. You may install an unlimited number of copies of the client software to access your ERP solution.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

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