Dynamic API Task Force - VIVO - LYRASIS Wiki
VIVO
Pages
Space shortcuts
VIVO Project Charter v 1.1
Besprechungsnotizen
VIVO Leadership Group
Page tree
Browse pages
tachments (0)
Page History
Page Information
Resolved comments
View in Hierarchy
View Source
Export to PDF
Export to Word
Export to PDF
Jira links
Dynamic API Task Force
Created by
Dragan Ivanovic
, last modified by
Georgy Litvinov
on
Dec 01, 2023
Background
In 2021 Dynamic API proposal was created as one of solutions to a better Vitro|VIVO architecture.
In February and May of 2022 Sprints took place, which became the basis for new API.
Resources
Dynamic API proposal
Specification
Parameters validation slides
ashboard
Deliverables
Powerful flexible API that makes it easy to extend back-end functionality by creation of new data configurations.
Web interface that simplifies manipulations with data configurations by using visual programming.
Migration of VIVO|Vitro services on new API
Dynamic forms
Dynamic API cache
Suggested schedule
Develop charter, assemble task force
4 weeks
week of TBD
Begin regular meetings
week of TBD
Task force development work
50 weeks
complete by TBD
Revise deliverables, final review
4 weeks
complete by TBD
Members
Georgy Litvinov
(TIB) - facilitator
Brian Lowe
Dragan Ivanovic
William Welling
Benjamin Kampe
Mark Vanin
Miloš Popović
Ivan Mrsulja
Always looking for additional members and developers!
Meeting Times
Fridays 15:00 (CET)
Communication Channels
Please join our new slack channel
#dynamic-api Slack Channel
- contact
Georgy Litvinov
for more information
Updates from the task force will be available in
VIVO Updates
Child pages to this page will contain meeting notes
taskforce
Overview
Content Tools
All content on the LYRASIS Wiki is licensed under the
CC BY (Attribution) license
, unless otherwise noted.
Atlassian Confluence Open Source Project License
granted to LYRASIS.
Evaluate Confluence today
Atlassian Confluence
8.5.31
Printed by Atlassian Confluence 8.5.31
Report a bug
Atlassian News
Atlassian
{"serverDuration": 73, "requestCorrelationId": "55aa3e7833af5455"}