{"component": "clause", "props": {"groups": [{"snippet_links": [{"key": "source-of", "type": "definition", "offset": [14, 23]}, {"key": "the-content", "type": "clause", "offset": [24, 35]}, {"key": "relates-to", "type": "definition", "offset": [192, 202]}, {"key": "other-information", "type": "definition", "offset": [203, 220]}, {"key": "the-information", "type": "clause", "offset": [229, 244]}, {"key": "for-example", "type": "definition", "offset": [254, 265]}, {"key": "description-of", "type": "definition", "offset": [348, 362]}, {"key": "information-object", "type": "definition", "offset": [397, 415]}, {"key": "examples-include", "type": "definition", "offset": [567, 583]}, {"key": "information-from", "type": "clause", "offset": [675, 691]}, {"key": "information-of-a", "type": "clause", "offset": [874, 890]}, {"key": "data-set", "type": "clause", "offset": [1041, 1049]}, {"key": "representation-information", "type": "clause", "offset": [1128, 1154]}, {"key": "obtaining-information", "type": "definition", "offset": [1259, 1280]}, {"key": "information-packages", "type": "clause", "offset": [1311, 1331]}, {"key": "description-information", "type": "clause", "offset": [1477, 1500]}, {"key": "received-by", "type": "definition", "offset": [1582, 1593]}, {"key": "the-consumer", "type": "definition", "offset": [1594, 1606]}, {"key": "form-of", "type": "definition", "offset": [1768, 1775]}, {"key": "packaging-information", "type": "clause", "offset": [1910, 1931]}, {"key": "the-producer", "type": "definition", "offset": [2159, 2171]}, {"key": "the-process", "type": "clause", "offset": [2255, 2266]}, {"key": "data-producers", "type": "definition", "offset": [2276, 2290]}, {"key": "the-relationship", "type": "clause", "offset": [2342, 2358]}, {"key": "transfer-of-data", "type": "clause", "offset": [2475, 2491]}, {"key": "preliminary-phase", "type": "clause", "offset": [2520, 2537]}, {"key": "initial-contacts", "type": "clause", "offset": [2606, 2622]}, {"key": "feasibility-studies", "type": "clause", "offset": [2678, 2697]}, {"key": "scope-of-the-project", "type": "definition", "offset": [2729, 2749]}, {"key": "the-sip", "type": "clause", "offset": [2762, 2769]}, {"key": "and-finally", "type": "clause", "offset": [2781, 2792]}, {"key": "submission-agreement", "type": "clause", "offset": [2801, 2821]}, {"key": "the-formal", "type": "clause", "offset": [2823, 2833]}, {"key": "definitions-of", "type": "clause", "offset": [2899, 2913]}, {"key": "transfer-conditions", "type": "definition", "offset": [3012, 3031]}, {"key": "restrictions-on-access", "type": "clause", "offset": [3040, 3062]}, {"key": "delivery-schedule", "type": "definition", "offset": [3084, 3101]}, {"key": "the-transfer", "type": "clause", "offset": [3103, 3115]}, {"key": "transfer-of-the", "type": "clause", "offset": [3142, 3157]}, {"key": "in-the-agreement", "type": "clause", "offset": [3270, 3286]}, {"key": "validation-phase", "type": "definition", "offset": [3292, 3308]}, {"key": "depending-on-the", "type": "clause", "offset": [3555, 3571]}, {"key": "completion-of-the", "type": "clause", "offset": [3635, 3652]}, {"key": "guidelines-for", "type": "clause", "offset": [3764, 3778]}, {"key": "changes-to-the", "type": "definition", "offset": [3872, 3886]}, {"key": "time-delay", "type": "clause", "offset": [4005, 4015]}, {"key": "beginning-of-the", "type": "clause", "offset": [4060, 4076]}, {"key": "final-outcome", "type": "clause", "offset": [4201, 4214]}, {"key": "contained-in", "type": "definition", "offset": [4276, 4288]}, {"key": "other-documents", "type": "definition", "offset": [4337, 4352]}, {"key": "additional-documents", "type": "definition", "offset": [4360, 4380]}, {"key": "interface-control-document", "type": "clause", "offset": [4398, 4424]}, {"key": "memorandum-of-understanding", "type": "definition", "offset": [4434, 4461]}, {"key": "memorandum-of-agreement", "type": "definition", "offset": [4471, 4494]}, {"key": "service-level-agreement", "type": "clause", "offset": [4504, 4527]}, {"key": "operations-agreement", "type": "definition", "offset": [4538, 4558]}, {"key": "of-documents", "type": "clause", "offset": [4632, 4644]}, {"key": "necessary-information", "type": "definition", "offset": [4728, 4749]}, {"key": "the-term", "type": "clause", "offset": [4821, 4829]}, {"key": "inclusive-of", "type": "clause", "offset": [4863, 4875]}], "samples": [{"hash": "iWB8sXKHMw8", "uri": "/contracts/iWB8sXKHMw8#provenance", "label": "Submission Agreement", "score": 26.5037645448, "published": true}], "size": 4, "snippet": "describes the source of the Content Information, who has had custody of it since its origination, and its history (including processing history). Context describes how the Content Information relates to other information outside the Information Package. For example, it would describe why the Content Information was produced, and it may include a description of how it relates to another Content Information object that is available. Reference provides one or more identifiers, or systems of identifiers, by which the Content Information may be uniquely identified. Examples include an ISBN number for a book, or a set of attributes that distinguish one instance of Content Information from another. Fixity provides a wrapper, or protective shield, that protects the Content Information from undocumented alteration. For example, it may involve a checksum over the Content Information of a digital Information Package. Much of the PDI content is included in national and international metadata standards. If it is already available for the data set, it can be referenced rather than being included in every SIP. Similarly, the Representation Information may be available separately and can also be referenced rather than included in every SIP. Figure 6.1-2. Obtaining Information from Data in an OAIS Archival Information Packages and Dissemination Information Packages An Archival Information Package (AIP) consists of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS. Dissemination Information Packages are received by the Consumer in response to a request to the Archive. In response to a request, the OAIS provides all or a part of an AIP, or potentially multiple AIPs, to a Consumer in the form of a Dissemination Information Package (DIP). The DIP may also include collections of AIPs, and it may or may not have complete PDI. The Packaging Information will necessarily be present in some form so that the Consumer can clearly distinguish the information that was requested. Figure 6.1-3. OAIS Information Package Concepts and Relationships PAIMAS BACKGROUND The second document, the Producer-Archive Interface Methodology Abstract Standard (PAIMAS), describes four phases of the process that the Data Producers and the Archive will follow. These phases describe the relationship, interactions, and negotiation between the Producer and the Archive that result in both a final SA and a successful transfer of data. The PAIMAS phases are: The Preliminary Phase, also known as a pre-ingest or pre-accessioning phase, includes the initial contacts between the Producer and the Archive and any resulting feasibility studies, preliminary definition of the scope of the project, a draft of the SIP definition and finally a draft Submission Agreement. The Formal Definition Phase includes completing the SIP design with precise definitions of the digital objects to be delivered, completing the Submission Agreement with precise contractual transfer conditions such as restrictions on access and establishing the delivery schedule. The Transfer Phase performs the actual transfer of the SIP from the Producer to the Archive and the preliminary processing of the SIP by the Archive, as it is defined in the agreement. The Validation Phase includes the validation processing of the SIPs by the Archive and any necessary follow-up action with the Producer. Different systematic or in-depth levels of validation may be defined. Validations may be performed after each delivery, or later, depending on the validation constraints. The SA, when finalized, represents the completion of the Formal Definition Phase. The Transfer and Validation phases will be subsequent steps and are documented in the Guidelines for the Producer-Archive Interface document. Note that there will, in many cases, be some needed changes to the Producer and/or the Archive software to accommodate specific functionality defined in this SA. This may necessitate a time delay between the formal definition phase and the beginning of the transfer phase so that these modifications can be developed, integrated, and tested. While the PAIMAS describes a SA as the final outcome, or deliverable, the Archive recognizes that the information contained in the PAIMAS version of the SA may be included in other documents. These additional documents could include an Interface Control Document (ICD), a Memorandum of Understanding (MOU), a Memorandum of Agreement (MOA), a Service Level Agreement (SLA), an Operations Agreement (OA), or other similar documents, and may be any combination of this set of documents. The Archive does not dictate which of these documents must be used, only that the necessary information be appropriately documented. However, for simplicity in this document, the term SA is used and is intended to be inclusive of all necessary information whether in the SA itself and/or in additional documents. TERMINOLOGY This section is a glossary which defines the common terminology as it is used in this document.", "hash": "2d332d38049c57ea79682fb0daca5bf8", "id": 1}, {"snippet_links": [{"key": "source-of", "type": "definition", "offset": [14, 23]}, {"key": "the-content", "type": "clause", "offset": [24, 35]}, {"key": "relates-to", "type": "definition", "offset": [192, 202]}, {"key": "other-information", "type": "definition", "offset": [203, 220]}, {"key": "information-package", "type": "definition", "offset": [233, 252]}, {"key": "for-example", "type": "definition", "offset": [254, 265]}, {"key": "description-of", "type": "definition", "offset": [348, 362]}, {"key": "information-object", "type": "definition", "offset": [397, 415]}, {"key": "examples-include", "type": "definition", "offset": [567, 583]}, {"key": "information-from", "type": "clause", "offset": [675, 691]}, {"key": "information-of-a", "type": "clause", "offset": [874, 890]}, {"key": "data-set", "type": "clause", "offset": [1041, 1049]}, {"key": "representation-information", "type": "clause", "offset": [1128, 1154]}, {"key": "obtaining-information", "type": "definition", "offset": [1259, 1280]}], "samples": [{"hash": "ktz0J4KrWgK", "uri": "/contracts/ktz0J4KrWgK#provenance", "label": "Submission Agreement", "score": 26.2683093771, "published": true}, {"hash": "1xlfSeQi1hf", "uri": "/contracts/1xlfSeQi1hf#provenance", "label": "Submission Agreement", "score": 25.9438740589, "published": true}], "size": 3, "snippet": "describes the source of the Content Information, who has had custody of it since its origination, and its history (including processing history). Context describes how the Content Information relates to other information outside the Information Package. For example, it would describe why the Content Information was produced, and it may include a description of how it relates to another Content Information object that is available. Reference provides one or more identifiers, or systems of identifiers, by which the Content Information may be uniquely identified. Examples include an ISBN number for a book, or a set of attributes that distinguish one instance of Content Information from another. Fixity provides a wrapper, or protective shield, that protects the Content Information from undocumented alteration. For example, it may involve a checksum over the Content Information of a digital Information Package. Much of the PDI content is included in national and international metadata standards. If it is already available for the data set, it can be referenced rather than being included in every SIP. Similarly, the Representation Information may be available separately and can also be referenced rather than included in every SIP. Figure 6.1-2. Obtaining Information from Data in an OAIS", "hash": "0f4d39b68b24edb2c6a682812f836766", "id": 2}, {"snippet_links": [{"key": "section-106", "type": "clause", "offset": [92, 103]}, {"key": "federal-agencies", "type": "clause", "offset": [147, 163]}, {"key": "the-country", "type": "definition", "offset": [269, 280]}, {"key": "identify-historic-properties", "type": "clause", "offset": [384, 412]}, {"key": "interested-parties", "type": "definition", "offset": [530, 548]}, {"key": "the-public", "type": "definition", "offset": [554, 564]}, {"key": "weigh-in", "type": "clause", "offset": [579, 587]}, {"key": "final-decision", "type": "definition", "offset": [614, 628]}, {"key": "cfr-800", "type": "clause", "offset": [674, 681]}], "samples": [{"hash": "4W5B9p8BWih", "uri": "/contracts/4W5B9p8BWih#provenance", "label": "Programmatic Agreement", "score": 31.4485320534, "published": true}, {"hash": "bZ1Oe6iwTc5", "uri": "/contracts/bZ1Oe6iwTc5#provenance", "label": "Programmatic Agreement", "score": 26.2251882272, "published": true}], "size": 2, "snippet": "The chronology of something\u2019s existence including origin, ownership, custody, and location. Section 106 \u2013 Section 106 of the NHPA of 1966 requires federal agencies to consider the effects of projects they carry out, assist, fund, permit, license, or approve throughout the country (known as \u201cUndertakings\u201d) on historic properties. The Section 106 process requires federal agencies to identify historic properties, assess effects on those properties, and consider alternatives to resolve those effects. Section 106 gives the ACHP, interested parties, and the public the chance to weigh in on these matters before a final decision is made. The ACHP has issued regulations, 36 CFR 800, which guide how agencies should fulfill this responsibility.", "hash": "fc2ae3563c49f8bb9949d1f6e254bf59", "id": 5}, {"snippet_links": [], "samples": [{"hash": "7FJpTyZE05C", "uri": "/contracts/7FJpTyZE05C#provenance", "label": "Educational Services", "score": 33.5162337011, "published": true}], "size": 3, "snippet": "Mortuary temple of Merenptah Bibliography: To be published by \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587 Excerpt: \u00a713,1\u2013\u00a713,3", "hash": "c5431bff91d874dfd3e2106c7f4b42c6", "id": 3}, {"snippet_links": [{"key": "the-client-warrants", "type": "clause", "offset": [0, 19]}, {"key": "represents-that", "type": "clause", "offset": [24, 39]}, {"key": "reason-to-suspect", "type": "definition", "offset": [69, 86]}, {"key": "client-assets", "type": "definition", "offset": [101, 114]}, {"key": "order-form", "type": "definition", "offset": [155, 165]}, {"key": "for-the-benefit-of", "type": "definition", "offset": [195, 213]}, {"key": "transactions-with", "type": "clause", "offset": [250, 267]}, {"key": "on-behalf-of", "type": "clause", "offset": [271, 283]}, {"key": "sanctioned-person", "type": "definition", "offset": [286, 303]}], "samples": [{"hash": "gEsM7Y6FvFb", "uri": "/contracts/gEsM7Y6FvFb#provenance", "label": "Master Services Agreement (CoinShares Valkyrie Bitcoin Fund)", "score": 35.7570157426, "published": true}, {"hash": "3hpkSKHhgKG", "uri": "/contracts/3hpkSKHhgKG#provenance", "label": "Master Services Agreement (CoinShares Valkyrie Bitcoin Fund)", "score": 35.7488021903, "published": true}], "size": 2, "snippet": "The Client warrants and represents that it does not know or have any reason to suspect that:\n(a) any Client Assets are (or, during the subsistence of this Order Form, will be) derived from, held for the benefit of, or otherwise related in any way to transactions with or on behalf of a Sanctioned Person; or\n(b) any Sanctioned Person has (or, during the subsistence of this Order Form, will have) any interest (legal or beneficial) in:\n(i) the Client; or\n(ii) the Client Assets.", "hash": "5880cfd3a85704b07f09e4ae9cc4961a", "id": 4}, {"snippet_links": [{"key": "the-location", "type": "clause", "offset": [0, 12]}, {"key": "associated-with", "type": "definition", "offset": [26, 41]}, {"key": "the-object", "type": "clause", "offset": [42, 52]}], "samples": [{"hash": "cKd2a80fiLZ", "uri": "/contracts/cKd2a80fiLZ#provenance", "label": "Museums Shared Services Partnership", "score": 22.1704312115, "published": true}, {"hash": "c82SvvDCYxb", "uri": "/contracts/c82SvvDCYxb#provenance", "label": "Museums Shared Services Partnership", "score": 19.3819301848, "published": true}], "size": 2, "snippet": "the location most closely associated with the object, or from where it was being offered as a donation/purchase/loan or bequest.", "hash": "503b960f46dbd7c79c7caece6e442091", "id": 6}, {"snippet_links": [], "samples": [{"hash": "goDo2xOcgG5", "uri": "/contracts/goDo2xOcgG5#provenance", "label": "Grant Agreement", "score": 24.2439354503, "published": true}], "size": 2, "snippet": "SP2 WP1 Task 2.1.9", "hash": "86098e49b6ebf6c2dcdc27e952c14ea0", "id": 7}, {"snippet_links": [], "samples": [{"hash": "7FJpTyZE05C", "uri": "/contracts/7FJpTyZE05C#provenance", "label": "Educational Services", "score": 33.5162337011, "published": true}], "size": 2, "snippet": "Mortuary temple of Merenptah, workshops in the south-west area of the temple Bibliography: To be published by \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587 Excerpt: \u00a713,5\u2013\u00a714,1", "hash": "6e0bb65bf8fc6a646bfd5a4c91839bdf", "id": 8}, {"snippet_links": [{"key": "complex-task", "type": "definition", "offset": [147, 159]}, {"key": "the-standard", "type": "clause", "offset": [182, 194]}, {"key": "at-the-end-of", "type": "clause", "offset": [299, 312]}, {"key": "changes-to-the", "type": "definition", "offset": [346, 360]}, {"key": "provenance-data", "type": "definition", "offset": [383, 398]}, {"key": "further-details", "type": "clause", "offset": [533, 548]}, {"key": "the-context", "type": "clause", "offset": [569, 580]}, {"key": "web-services", "type": "clause", "offset": [814, 826]}, {"key": "in-combination", "type": "definition", "offset": [925, 939]}, {"key": "february-2011", "type": "clause", "offset": [987, 1000]}, {"key": "depending-on-the", "type": "clause", "offset": [1254, 1270]}, {"key": "other-projects", "type": "definition", "offset": [1400, 1414]}, {"key": "maintenance-of", "type": "clause", "offset": [1453, 1467]}, {"key": "development-stage", "type": "definition", "offset": [1562, 1579]}, {"key": "error-handling", "type": "clause", "offset": [1631, 1645]}, {"key": "development-tasks", "type": "clause", "offset": [1725, 1742]}, {"key": "specific-situations", "type": "clause", "offset": [1805, 1824]}, {"key": "early-development", "type": "definition", "offset": [1920, 1937]}, {"key": "lack-of", "type": "clause", "offset": [1984, 1991]}, {"key": "new-version", "type": "clause", "offset": [2157, 2168]}, {"key": "in-order-to", "type": "clause", "offset": [2169, 2180]}], "samples": [{"hash": "kX8bcSnEzu", "uri": "/contracts/kX8bcSnEzu#provenance", "label": "Grant Agreement", "score": 20.1285801712, "published": true}], "size": 2, "snippet": "WS-GR-02. ILC has managed to extract data from the Taverna automatic provenance system (Taverna handles provenance using an intern database). This complex task is being done outside the standard Taverna provenance system which is useful but cannot be extracted. Taverna is releasing a new workbench at the end of February, which could bring some changes to the actual situation. The provenance data issue will become more important in the version of PANACEA handling massive data, where the Taverna Server solution will be examined. Further details will be provided in the context of D3.3 (t22). \u2587\u2587-\u2587\u2587-01. Massive data can be handled in two different ways: as large collections of small (or average-sized) files, or as small collections of large files. UPF has used some workflows to test large files with Soaplab web services. File sizes were tested successfully from 100 KB to 100MB. However, bigger files should be tested in combination with the new Taverna Server (to be released in February 2011). The scenario with many small files has been tested up to 50 files. Again, these tests must be further examined in combination with the Taverna Server. This task and its result will be presented in D3.3 (t22). All tasks regarding Axis web services are depending on the Soaplab success. UPF has developed different web services using Axis2. Some of these web services are being successfully used in other projects. However, the cost of development and maintenance of these web services is much bigger than using Soaplab. Moreover, Axis2 web services, with this development stage, provide fewer features than Soaplab: more complex error handling and temporary files management, etc. From this point of view, Axis web service development tasks will be postponed and used as a fallback position or for some specific situations. WF-TV-02. Some tests with Taverna server were done at UPF. However, they were conducted at an early development stage of Platform version 1, when there was a lack of real workflows and finalized Soaplab web services. The new Taverna Server to be released in February 2011 makes it more interesting to continue those tests with the new version in order to address the real challenge of massive data with the now more stable PANACEA web services. This task and its result will be presented in D3.3 (t22).", "hash": "48bbf050b70adbb591fa3d0b5a02dd09", "id": 9}, {"snippet_links": [{"key": "covered-by", "type": "definition", "offset": [13, 23]}, {"key": "sales-agreement", "type": "definition", "offset": [41, 56]}, {"key": "received-by", "type": "definition", "offset": [62, 73]}, {"key": "act-of-sale", "type": "definition", "offset": [115, 126]}], "samples": [{"hash": "k8PwARfc0IO", "uri": "/contracts/k8PwARfc0IO#provenance", "label": "Preliminary Sales Agreement", "score": 29.5662388594, "published": true}], "size": 2, "snippet": "The property covered by this Preliminary Sales Agreement were received by \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587 by virtue of Public Act of Sale (Compravendita) N. 71324 Rep, N. 22863 Racc., registered on 1/2009 in Soverato, n. 2378 (Apartment sub 145).", "hash": "13be6eb90a8f7c2b97fc8d3945bfb511", "id": 10}], "next_curs": "ClMSTWoVc35sYXdpbnNpZGVyY29udHJhY3Rzci8LEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhNwcm92ZW5hbmNlIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"title": "Provenance", "parents": [["pensions", "Pensions"], ["governing-law-jurisdiction", "GOVERNING LAW, JURISDICTION"], ["retention", "Retention"], ["client-assets", "Client Assets"], ["fourth-ezra", "Fourth Ezra"]], "size": 40, "children": [["", ""], ["data-usage-to-date", "Data usage to date"], ["correlative-optical-and-fib", "Correlative optical and FIB"], ["data-description-functional-annotation-of-k-channels", "Data Description: Functional Annotation of K channels"], ["data-description-k-channel-kinetics", "Data Description: K Channel Kinetics"]], "id": "provenance", "related": [["environmental-compliance-and-reports", "Environmental Compliance and Reports", "Environmental Compliance and Reports"], ["responsibility-for-environmental-contamination", "Responsibility for Environmental Contamination", "Responsibility for Environmental Contamination"], ["marketing-materials-and-representations", "MARKETING MATERIALS AND REPRESENTATIONS", "MARKETING MATERIALS AND REPRESENTATIONS"], ["environmental-and-social-standards", "Environmental and Social Standards", "Environmental and Social Standards"], ["periodic-review-of-costs-of-environmental-compliance", "Periodic Review of Costs of Environmental Compliance", "Periodic Review of Costs of Environmental Compliance"]], "related_snippets": [], "updated": "2025-07-07T12:37:48+00:00", "also_ask": [], "drafting_tip": "Specify the origin of goods, require supporting documentation, and define verification procedures to ensure traceability, prevent disputes, and facilitate compliance.", "explanation": "A Provenance clause establishes the requirement to document and verify the origin and history of goods, materials, or data involved in a transaction or agreement. In practice, this clause may require parties to provide records, certifications, or other evidence tracing the source and chain of custody for items delivered or used. Its core function is to ensure transparency and authenticity, helping to prevent fraud, counterfeiting, or the use of unauthorized materials."}, "json": true, "cursor": ""}}