Metadata regarding Representations and Access Software Sample Clauses

This clause defines the requirements and responsibilities related to the documentation and management of metadata concerning representations and the software used to access them. It typically specifies what metadata must be maintained, such as file formats, software versions, or dependencies necessary to interpret digital content, and may require parties to provide or update this information as part of their obligations. By ensuring that all relevant metadata and access software details are properly recorded and shared, the clause helps maintain long-term accessibility and usability of digital assets, preventing issues related to obsolescence or incompatibility.
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 ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/standards/premis/v3/premis-3-0-final.pdf 71 Cf. PREMIS 3.0 page 8, ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/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: 1. Describe which DIP representation format is contained in the DIP (description 1); 2. Describe which piece(s) of Access Software are needed to render a specific DIP representation format. Several pieces of software may indeed be needed (description 2); 3. Describe the relationship between the DIP representation format and its Access Software (description 3).
View Source
Metadata regarding Representations and Access Software. 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).
View Source
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. ▇▇▇▇://▇▇▇.▇▇▇▇-▇▇▇▇▇▇▇.▇▇▇/resources/project-deliverables/92-d54 The descriptions below therefore show how to: 1. Describe which DIP representation format is contained in the DIP (description 1 below); 2. Describe which piece(s) of Access Software is/are needed to render a specific DIP representation format. Several ...
View Source