Actions2
- Search Actions
Search → Get by PID
AI-generatedOverview
This node interacts with the Dikda digital archive (Slovak National Library digital archive) to perform search operations. Specifically, the 'Get by PID' operation allows users to retrieve a document by its Persistent Identifier (PID/UUID). This is useful for fetching precise documents when the unique identifier is known, such as retrieving a specific archived document by its UUID.
Use Case Examples
- Retrieve a document from the Dikda archive using its UUID to get detailed metadata or content.
- Fetch a specific record by PID for integration into a larger workflow that processes archival data.
Properties
| Name | Meaning |
|---|---|
| PID (UUID) | The Persistent Identifier (PID/UUID) of the document to retrieve, e.g., uuid:99a11ca9-9872-4f89-a682-432e6b54da53. This is required to specify which document to fetch. |
| Rows | Number of results to return, typically 1 for PID lookup. Controls how many matching documents are returned. |
| Fields | Comma-separated list of fields to return from the document. Leave empty to return all fields. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings. |
Output
JSON
response- The JSON response from the Dikda API containing the search results or document data.
Dependencies
- Dikda API endpoint at https://dikda.snk.sk/search/api/client/v7.0/
Troubleshooting
- Ensure the PID is correctly formatted, starting with 'uuid:' if not already included, to avoid query errors.
- If no results are returned, verify the PID exists in the archive and the 'Rows' parameter is set appropriately.
- Timeout errors may occur if the server is slow or unreachable; adjust the 'Timeout' setting or check network connectivity.
- SSL certificate errors can be bypassed by enabling 'Ignore SSL Issues' but use with caution due to security risks.
Links
- Dikda API Documentation - Official API documentation for the Dikda digital archive search client.