Folder structure. The folder tree representing a 6G Library Object is presented in Figure 2. Three main folders are used, namely the private, the public and the documentation folder. Figure 3: 6G Library Object Structure Public Folder This folder contains the component public information that could be used by third parties to integrate the catalogue. • description.yaml (file): Is a descriptor file with the component public information. It contains metadata (component name, version, etc., ...) and the public variables that should be used to deploy it. • changelog.yaml (file): Is a file with the component historical evolution: new version, bug fixing, etc. Private Folder This folder contains the component private files with information and automation that will be used to deploy the component in a 6G-SANDBOX site. • values.yaml (file): Contains variables needed by automation tools to accomplish deployment and configuration • manifest.yaml (file): Contains the flow that must be followed to deploy the component • cloud_provider(folder): One folder per cloud provider where the component will be available o cac (folder): Contains files related to configuration automation ▪ pre(folder): Contains files related to configuration that should be done in advance. For example, gather some information from cloud provider. ▪ install(folder): Contains files related to component configuration ▪ post(folder): Contains files related to configuration that should be done after component set-up. For example, test execution. o Iac (folder): Contains files related to infrastructure definition Documentation Folder It contains detailed information about the component in Markdown editor format, to enable direct integration between third parties and the catalogue.
Folder structure. The CeRTNA ERDS County Administration module provides the ability to configure a base folder structure that will be used for retrieving payloads from the CeRTNA ERDS to the County and for returning payloads from the County to the CeRTNA ERDS. The folder structure can be based on physical or mapped drive letters or on UNC paths. The default configuration is based on a physical drive as follows:
Folder structure. The folder structure of a DIP containing a relational database in SIARD format is fully compliant with the folder structure of the E-ARK Information Packages described in section 4.1 of the Introduction to the Common Specification for Information Packages in the E-ARK Project.
Folder structure. The folder structure of a DIP containing relational databases in SIARD format is fully compliant with the folder structure of E-ARK Information Packages described in section 4.1 of the Introduction to the Common Specification for Information Packages in the E-ARK Project. In the case where the IP contains more than one representation of the database, the difference between the representations must be indicated in PREMIS. Different representations should be treated as different (representation) object entities belonging to the same intellectual (object) entity. The relationship between the representations can be expressed by the semantic unit (PREMIS) “relationship”. This semantic unit includes “relationshipType” and “relationshipSubType” as semantic components. In regard to the recommendation to use PREMIS, both components’ values should be taken from a controlled vocabulary. The documentation folder should include all relevant OLAP specific data which may be:
Folder structure. Within the IP geodata will be structured according to the representation-based model as shown in Figure 2 – Folder structure of the geodata DIP below: 109 Described in greater detail in the chapter 4.3 of the official deliverable D.4.3. Figure 2 – Folder structure of the geodata DIP
Folder structure. The folder structure should reflect the archival structure of the records and the piece and item levels should also be reflected in the file naming. If the records were from the series CAB 129 they should be grouped in folders as below (folder titles are in bold): • Top level folder should reflect the dept code_series number e.g. CAB_129 • The next folder should be named content (with a small 'c'): content • The next folder should reflect the piece number e.g. 179 • The next folder should reflect the item* number e.g. 7 The files for each item should be contained in the item folder to which they relate. Where there is no item the images will be contained in the piece folder to which they relate. As an example, the folder structure for the files from CAB 129/179/7 would look like this: CAB_129 (Deptcode_seriesnumber) content (folder named ‘content’) 179 (piece level folder) 7 (item level folder ) 179_7_0001.tif (file 1) 179_7_0002.tif (file 2) * The item level is optional as it depends on the collection but sub series, sub sub series and sub items should not be represented in the folder structure.
