Metadata regarding Representations and Access Software Sample Clauses

Metadata regarding Representations and Access Software. 4.4.1.3.4 Access tools Since the full ERMS DIP shares most of characteristics with other SMURF DIP sub-formats all the requirements mentioned above for the single records DIP and case file DIP apply. In addition we expect the following scenario specific requirements related to the Data folder of the Full ERMS DIP to be fulfilled: • ability to view/browse the classification schema, preferably presented in hierarchal structure; • ability to view the metadata of the whole classification schema; • ability to view/browse the classes and their metadata; • search over the full classification schema with the use of class metadata as filters; • ability to view/browse the aggregations (e.g. case file) in original context (possibility to browse the original classification); • ability to view detailed aggregations metadata; • search over classes with the use of aggregation metadata as filters; • ability to view/browse the internal structure of the archived aggregation (e.g. case file) with the possibility to browse contained records; • ability to view the detailed record metadata; • search over aggregations with the use of records metadata as filters; • ability to view/browse the archived record with the possibility to browse contained attachments (imbedded/related computer files); • ability to access content of contained attachments (embedded/related computer files).
Sample 1
AutoNDA by SimpleDocs
Metadata regarding Representations and Access Software. In PREMIS, a representation is a “set of files, including structural metadata, needed for a complete and reasonable rendition of an Intellectual Entity.”50. One of the core concepts in PREMIS is the above formulated definition of a representation, but it is also important to note that the E-ARK Common Specification Information Package structure also incorporates physical management of different representations. When implementing PREMIS in E-ARK packages one must therefore choose if there must exist PREMIS files at representation level or at root level only (see Common Specification) and one must also choose how fine-grained each description should be. In PREMIS, a representation is indicated using the semantic unit “1.1 objectIdentifier”. In E-ARK Access, as already mentioned, the DIP representation formats are SMURF ERMS, SMURF SFSB, SIARD1.0, SIARD2.0, SIARDDK, OLAP, GML, and GeoTIFF. It is important to emphasise that the E-ARK project has neither created specifications nor tools for specific file formats51 (fine-grained descriptions), but only for the aforementioned DIP representation formats. Hence, the Access Software developed by the E-ARK project does guarantee the rendering of the E-ARK representations, but not of specific file formats contained inside an E-ARK representation. As an example, the SMURF ERMS could contain several file formats unknown to the E-ARK IP Viewer52 (note: even though this is unlikely, because archives generally make sure that the number of file formats that they preserve is limited and their use widespread. As such for example PDF or TIFF files would be rendered). To enable rendition, three pieces of information are needed in PREMIS: One identifying the representation to be rendered; one identifying the software to enable this; and one establishing a relationship between the two. 50 PREMIS Editorial Committee (2015). “PREMIS Data Dictionary for Preservation Metadata”, p.8. 51 For example PDF or JPG. 52 The generic Access tool that allows for the rendering of the DIP reference format, ie. the folder structure, descriptive metadata,and the most common file formats, cf. D5.4 Search, Access and Display Interfaces. xxxx://xxx.xxxx-xxxxxxx.xxx/resources/project-deliverables/92-d54 The descriptions below therefore show how to:
Sample 1
Metadata regarding Representations and Access Software. In PREMIS, a representation is a “set of files, including structural metadata, needed for a complete and reasonable rendition of an Intellectual Entity.”71 In E-ARK Access, as already mentioned, the DIP representation formats are SMURF ERMS, SMURF SFSB, SIARD1.0, SIARD2.0, SIARDDK, OLAP, GML, and GeoTIFF. In PREMIS, a representation is indicated using the semantic unit “1.1 objectIdentifier”. It is important to emphasise that the E-ARK project has neither created specifications nor tools for specific file formats, but only for the aforementioned DIP representation formats. Hence, the Access Software developed by the E-ARK project does guarantee the rendition of the E-ARK representations, but not of specific file formats contained in an E-ARK representation. As an example, the SMURF ERMS could contain several file formats unknown to the E-ARK ERMS Viewer72, even though this is unlikely, because archives generally make sure that the number of file formats that they preserve is limited and their use widespread. Everything needed to describe the representation is already taken care of in the AIP, and the only other piece of information needed from an Access perspective is information about rendition (Representation Information). To enable rendition, three pieces of information are needed in PREMIS: One identifying the representation to be rendered; one identifying the software to enable this; and one establishing a relationship between the two. 70 xxxx://xxx.xxx.xxx/standards/premis/v3/premis-3-0-final.pdf 71 Cf. PREMIS 3.0 page 8, xxxxx://xxx.xxx.xxx/standards/premis/v3/premis-3-0-final.pdf 72 GUI conceived by the E-ARK project to view ERMS systems. The below descriptions therefore show how to:
Sample 1

Related to Metadata regarding Representations and Access Software

  • Customer Representations Customer hereby represents and warrants that:

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Bid Attributes Disadvantaged/Minority/Women Business & Federal HUBZone Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Historically Underutilized Business (HUB) Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No National Coverage Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • Power Supply Information and Access to Information 12 POWER SUPPLY INFORMATION

  • IDENTIFYING INFORMATION AND PRIVACY NOTIFICATION (a) FEDERAL EMPLOYER IDENTIFICATION NUMBER and/or FEDERAL SOCIAL SECURITY NUMBER. As a condition to NYSERDA’s obligation to pay any invoices submitted by Contractor pursuant to this Agreement, Contractor shall provide to NYSERDA its Federal employer identification number or Federal social security number, or both such numbers when the Contractor has both such numbers. Where the Contractor does not have such number or numbers, the Contractor must give the reason or reasons why the payee does not have such number or numbers.

  • Client Representations Client represents and warrants to Consultant that;

  • Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • Contractor Certification regarding Business with Certain Countries and Organizations Pursuant to Subchapter F, Chapter 2252, Texas Government Code], Contractor certifies Contractor is not engaged in business with Iran, Sudan, or a foreign terrorist organization. Contractor acknowledges this Agreement may be terminated and payment withheld if this certification is inaccurate.

  • Internet Access to Contract and Pricing Information Access by Authorized Users to Contract terms and pricing information shall be made available and publically posted on the OGS website. To that end, OGS shall publically post the Contract Pricelist, including all subsequent changes in the Contract offerings (adds, deletes, price revisions), Contractor contact information, and the Contract terms and conditions, throughout the Contract term.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!