data.gv.at (Open Government Data Austria) Identifiers API

openapi: 3.2.0
info:
  version: 3.3.1
  title: piveau hub-repo service Identifiers API
  description: The API simplifies the management of datasets, adhering to the DCAT-AP standard for structured data descriptions. It integrates seamlessly with Virtuoso, an efficient database server and Triplestore, making dataset management more accessible. The DCAT-AP standard ensures consistent, comprehensive data descriptions, enhancing data sharing and discovery. The API simplifies the process of making datasets accessible to a wider audience. This promotes transparency, knowledge sharing, and collaboration. This introduction lays the groundwork for exploring the hub-repo Open API. Detailed information on authentication, API endpoints, error handling, and practical examples can be found in the subsequent sections to gain a comprehensive understanding of the API's functionality.
  x-logo:
    url: images/logo
servers:
- url: ''
tags:
- name: Identifiers
  x-displayName: Identifiers
  description: Create persistent identifiers for data artifacts.
paths:
  /identifiers/datasets/{datasetId}:
    parameters:
    - $ref: '#/components/parameters/DatasetId'
    put:
      description: This function is reserved for internal use only and is not part of our public API offerings. This endpoint allows to create a persistent identifier for a dataset, that will be stored in the adms:identifier property. Choose value "mock" for the query parameter type if you need it for simulation purpose.
      summary: Create a persistent identifier for a dataset
      operationId: createDatasetIdentifier
      tags:
      - Identifiers
      security:
      - ApiKeyAuth: []
      - BearerAuth: []
      parameters:
      - name: catalogue
        deprecated: true
        in: query
        description: The the catalogue id to which the dataset belongs
        schema:
          type: string
      - name: type
        in: query
        required: true
        description: The type of the persistent identifier
        schema:
          type: string
          enum:
          - eu-ra-doi
          - mock
      responses:
        '200':
          description: Identifier created, details in the response body
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '404':
          description: Dataset not found
        '422':
          description: Unprocessable Entity, details in the response body.
          content:
            application/json:
              schema:
                type: object
  /identifiers/datasets/{datasetId}/eligibility:
    parameters:
    - $ref: '#/components/parameters/DatasetId'
    get:
      description: This function is reserved for internal use only and is not part of our public API offerings. As an authorized user you can check if the specified dataset has all required elements ("creator", "publisher" etc.) to obtain an identifier. Send a GET request to the specified API endpoint URL with the resource path "/identifiers/datasets/{datasetId}/eligibility" added at the end of the URL, set the unique ID of the dataset as {datasetID} element of the URL. Choose value "mock" for the query parameter type if you need it for simulation purpose.
      summary: Check if an identifier can be issued for the given dataset
      operationId: checkIdentifierEligibility
      tags:
      - Identifiers
      security:
      - ApiKeyAuth: []
      - BearerAuth: []
      parameters:
      - name: catalogue
        in: query
        description: The the catalogue id to which the dataset belongs
        schema:
          type: string
      - name: type
        in: query
        description: The type of the persistent identifier
        schema:
          type: string
          enum:
          - eu-ra-doi
          - mock
      responses:
        '200':
          description: Eligible or not
        '404':
          description: The dataset was not found
components:
  parameters:
    DatasetId:
      name: datasetId
      description: The dataset id
      in: path
      required: true
      schema:
        type: string
        pattern: '[a-z,0-9,\-,~]+'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT