Retrieve data
Singularity provides a user-friendly way to browse and retrieve the dataset using URI paths, similar to filesystem paths.
This guide describes retrievals using the Singularity tool only. Filecoin retrievals are an evolving space, with projects working on fast CDN-type retrievals. See https://retrieval.market/
Prerequisites
Singularity has completed the replication of a dataset.
SPs have sealed the dataset and deals are active on-chain.
IPFS daemon service is started.
Create dataset index
To create the index for a dataset:
If your dataset contains a larger numbers of files that exceed default index soft-limits, you should increase the default parameters.
The dataset's index is written to an IPFS CID. Retrieval operations using the Singularity client will lookup this IPFS index.
Lookup the index using a user-friendly DNSLink name
To make the IPFS path more user-friendly, a DNS TXT record for DNSLink can be published that contains the IPFS path, providing an easy logical name to reference the index.
E.g. If your organization owns the domain "mydata.net", and the dataset is named "mydatasetname" the DNSLink subdomain record can be:
Consult your DNS provider for specific instructions to update the TXT record.
Alternate ways to reference the index IPFS path
If you do not have access to update the DNS provider of your organization, an alternative way is to use environment variables, aliases, or other indirection methods to dereference the IPFS path.
List data
Using DNSLink name:
Using the IPFS path.
Retrieve data
Copy a file from a specific path in the dataset to a local path.
Using DNSLink name:
Using the IPFS path.
Ref: Indexing and Retrieval in the Singularity getting started doc.
\
Last updated