-
Notifications
You must be signed in to change notification settings - Fork 531
Closed
Labels
FY26 Sprint 2FY26 Sprint 2 (2025-07-16 - 2025-07-30)FY26 Sprint 2 (2025-07-16 - 2025-07-30)GREI Re-archIssues related to the GREI Dataverse rearchitectureIssues related to the GREI Dataverse rearchitectureOriginal size: 3SPAThese changes are required for the Dataverse SPAThese changes are required for the Dataverse SPASPA.Q3.2025.2Link CollectionLink CollectionSize: 3A percentage of a sprint. 2.1 hours.A percentage of a sprint. 2.1 hours.
Milestone
Description
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.
qqmyers
Metadata
Metadata
Assignees
Labels
FY26 Sprint 2FY26 Sprint 2 (2025-07-16 - 2025-07-30)FY26 Sprint 2 (2025-07-16 - 2025-07-30)GREI Re-archIssues related to the GREI Dataverse rearchitectureIssues related to the GREI Dataverse rearchitectureOriginal size: 3SPAThese changes are required for the Dataverse SPAThese changes are required for the Dataverse SPASPA.Q3.2025.2Link CollectionLink CollectionSize: 3A percentage of a sprint. 2.1 hours.A percentage of a sprint. 2.1 hours.