-
Notifications
You must be signed in to change notification settings - Fork 542
Manage Guestbook API: Edit guestbook and Responses table #12386
Copy link
Copy link
Open
Labels
FY26 Sprint 23FY26 Sprint 23 (2026-05-06 - 2026-05-20)FY26 Sprint 23 (2026-05-06 - 2026-05-20)GREI Re-archIssues related to the GREI Dataverse rearchitectureIssues related to the GREI Dataverse rearchitectureSPAThese changes are required for the Dataverse SPAThese changes are required for the Dataverse SPASize: 30A percentage of a sprint. 21 hours. (formerly size:33)A percentage of a sprint. 21 hours. (formerly size:33)Type: Featurea feature requesta feature request
Metadata
Metadata
Assignees
Labels
FY26 Sprint 23FY26 Sprint 23 (2026-05-06 - 2026-05-20)FY26 Sprint 23 (2026-05-06 - 2026-05-20)GREI Re-archIssues related to the GREI Dataverse rearchitectureIssues related to the GREI Dataverse rearchitectureSPAThese changes are required for the Dataverse SPAThese changes are required for the Dataverse SPASize: 30A percentage of a sprint. 21 hours. (formerly size:33)A percentage of a sprint. 21 hours. (formerly size:33)Type: Featurea feature requesta feature request
Type
Fields
Give feedbackNo fields configured for issues without a type.
Overview of the Feature Request
According to native API guestbook, comparing with what we need for support SPA, we need some endpoints for guestbook management
Existing APIs to use:
New / enhanced APIs needed:
`curl -PUT -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/{ID}" -d "$JSON"
What kind of user is the feature intended for?(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
What inspired the request?
Manage Guestbook page is a must-have for SPA
Any open or closed issues related to this feature request?
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?