This space is used for issues and documentation (until a canonical documentation place has been defined) of data ingestion as part of Fairicube WP5 work.
In a nutshell, data needed by the Use Cases will be imported into the FAIRiCUBE HUB to form datacubes. These make data access easier as they are homogenized in structure and access (if you ever had to go through different data repositories and harvest data, followed by own homogenization work, you will see that pushing that work "behind the curtain" by automating access is a big advantage). Of course, in order to provide data in such a "beautified" manner the homogenization work still needs to be done by somebody. In FC, that is: us. Tools like the data request form and the rasdaman ETL suite assist greatly, but for the final homogenized datacubes human caring hands are still necessary given the vast divergence of data; improving life of data wranglers is a key mission of the project, actually.
Contents of this space:
- How to Get Data Added
- Choosing the right pixel type
- Details on the Coverage range type, as inherited from SWE Common
- Connecting catalog with datacubes
- Finding data ingested, datacube access how-to
- Use case specific modeling and access
- complete rasdaman documentation
See also the list of requirements agreed with the Use Cases
As data ingest is tightly connected with metadata management, use of data, etc., consider also these related spaces:
-
metadata-editor WebGUI: to provide and edit metadata to be shown in the data catalog (STAC-fastapi)
-
resource-metadata: in addition to the issues providing metadata for resources, also used to discuss technical details on resource metadata
-
Fairicube Hub: for general FAIRiCUBE topics
A hitherto unsolved problem is the project's policy for data and processing access management. Preliminaries: