Provenance 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 may be included in national and/or international standard metadata. If these metadata are 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-5. 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.
Provenance. Upon request, Artist will furnish Purchaser and his successors a written history and provenance of the Work, based on TAR's and Artist's best information as to shows.
Provenance 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
Provenance. 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. Xxxxxxx 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). Soaplab Test massive data XX-XX-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). Axis web services 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. Taverna Server test 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).
Provenance the location most closely associated with the object, or from where it was being offered as a donation/purchase/loan or bequest.
Provenance. The chronology of something’s existence including origin, ownership, custody, and location. Section 106 – 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 “Undertakings”) 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.
Provenance. XX0, XX0.0, Task 1.1.2: Xxxxx XXXXXXX (UOXF)
Provenance. SP2 WP1 Task 2.1.9
Provenance. The property covered by this Preliminary Sales Agreement were received by Xxxxxx Xxxxxx Xxxxxx 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).
Provenance. By signing the Incoming Loan Contract, the Lender confirms that to the best of his/her knowledge he/she/it has clear title to the loaned objects and no part of the provenance of any of the pieces conflict with national or state civil or criminal laws.
