Skip to content

API : List Dataverse Collection Links #11633

@g-saracca

Description

@g-saracca

I wanted to suggest a small refactor for the API response format in the List Dataverse Collection Links API endpoint.
Refactoring this would greatly benefit both the SPA and other API consumers, as the current response can be a bit tricky to work with.

Current response example:

{
  "status": "OK",
  "data": {
    "dataverses that the germn-saracca-collection dataverse has linked to": [
       "germn-saracca-collection-2"
   ],
   "dataverses that link to the germn-saracca-collection": [],
   "datasets that the germn-saracca-collection has linked to": []
  }
}

I'm not entirely sure about the best naming conventions, I believe that using single-word, non-dynamic property names would significantly improve the usability and testing of the API.

Metadata

Metadata

Assignees

No one assigned

    Labels

    FY26 Sprint 2FY26 Sprint 2 (2025-07-16 - 2025-07-30)GREI Re-archIssues related to the GREI Dataverse rearchitectureOriginal size: 3SPAThese changes are required for the Dataverse SPASPA.Q3.2025.2Link CollectionSize: 3A percentage of a sprint. 2.1 hours.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions