...
Attendees
Resources
...
Goals:
- Surface any fundamental issues
Sprint logistics / scheduling
- Daily stand-up report in Slack - #dynamic-api-sprint-may-2022 channel
- Regional kickoffs for: final ticket assignments, dev env setup, dev process, etc
- European kick-off meeting: 9am CET - same Zoom North American kick-off meeting: 10am ET - same ZoomA bi-daily meeting (Monday, Wednesday, Friday) at 10am Eastern Time (4pm CEST)
- Branches
- Test datasets
- General, manual Integration tests
- Development processes
- Dev environment... please take as first task to establish this
Tickets - https://github.com/orgs/vivo-project/projects/2/views/1
Documentation - VIVO Dynamic API
- Ontology
- RDF representation of dynamic actions and resourceAPIs
- Binding
- Binding to Java objects representation
- Execution
- Execution of a dynamic action
- RCP Endpoint
- REST Endpoint
- Security
- Definition of dynamic action roles
- Authentication (endpoint and UI)
- Authorization
- JWT
- Do we need OAuth2 or OpenID Connect ???
- Validation
- syntax,
- over the ontology,
- generic SHACL rules for all dynamic actions
- custom SHACL rules for specific dynamic actions ???
- UI for running a dynamic action
- Angular & Angular Material
Some notes regarding angular from William Welling .
- I would recommend against using a openapi specification generator
- it likely does not take into consideration angular universal for SEO, central state management, or i18n
- it is not likely to be a long lived dependency, popular, or actually work well with the dynamism of custom actions
- choose between the server side module (both express and angular universal)
- consider a central state management up front
- choose i18n library (important to know whether we want runtime or build time i18n)
- http://www.ngx-translate.com/
- https://ngneat.github.io/transloco/
- https://angular.io/guide/i18n-overview
- adopt a style guide and have it enforced using linting
- have github action check code styles
- protect main branch against style guide violations
- incorporate best practices and have test coverage in initial commit
- have github action that performs code coverage
- protect main branch for code coverage decrease
- CRUD operations for custom actions
- UI for management of custom actions
- Exploitation
Slack stand-up template
Panel |
---|
[VIVO Dynamic API Standup] |
...