...
Indicating note-taker
Agenda
- Questions/Issues/Pull requests/Announcements
- Conferences
- CRIS 2022 - report
- OR 2022 - program
- New issues and PRs
- A reverse proxy (redirecting) - https://github.com/vivo-project/VIVO/issues/3698
- Conferences
- The next sprint
- date
- May 30th - June 17th
- Registration
- link
- Five registered participants so far
- Infrastructure
- Wiki page - Sprint - Dynamic API based on an ontology 2
- Slack channel created
- Project board
- We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
- but extend it with new issues (features, bugs)
- We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
- Starting point
- backend
- frontend
- https://github.com/vivo-project/Vitro-angular/tree/sprint-dynapi-2022
- https://github.com/vivo-project/Vitro-angular/tree/sprint-dynapi-2022-staging
- Specification
- Link to specification - https://docs.google.com/document/d/1n7gSf_cSDS5mbTI4HwVGj-2sQd5if0177Nrdtri9BtM/edit#
- Topics
- Update the ontology
- GET all and GET one - two dynamic actions or one
- Implement more complex workflows
- iteration step,
- conditional step
- Implement N3Template deletion and modification
- User interface for execution of a dynamic action
- Selection of the frontend technology/framework
- User interface for definition of a dynamic action
- Validation of dynamic action
- Authorization - roles
- Update the ontology
- Cleaning up not completed work at previous sprint
- https://github.com/vivo-project/Vitro/pull/285
- GET all and GET one - two dynamic actions or one ?
- https://github.com/vivo-project/Vitro/pull/286
- deletion and modification
- https://github.com/vivo-project/Vitro/pull/287
- Transforming xml notation of Dynamic API ontology to turtle/n3 notation
- Introducing new jena model for dynamic actions
- Cleaning up issues at https://github.com/orgs/vivo-project/projects/2/views/1
- https://github.com/vivo-project/Vitro/pull/285
- date
...
- Questions/Issues/Pull requests/Announcements Conferences
- CRIS 2022 - report
- OR 2022 - program
New issues and PRs- A reverse proxy (redirecting) - https://github.com/vivo-project/VIVO/issues/3698
- Conferences
- New issues and PRs
Dragan:
CRIS conference was great.
Good to meet Rolf and Bruce in person.
Slides will be available online.
4 presentations on VIVO.
No new news on OR 2022. In person in three weeks.
New issue to support base URL (context path)
- The next sprint date
- May 30th - June 17th
Registration- link
- Five registered participants so far
- date
- Registration
Dragan:
Please register for dynamic API sprint, https://forms.gle/whYvMwgpbo7q6DgC9
Will prepare for the sprint in the next two weeks.
- Infrastructure Wiki page - Sprint - Dynamic API based on an ontology 2
- Slack channel created
- Project board
- We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
- but extend it with new issues (features, bugs)
Starting point- Wiki page - Sprint - Dynamic API based on an ontology 2
- Slack channel created
- Project board
- Starting point
William: No need for staging any longer as already diverged from head development.
Dragan: Will rename to dynamicapi and feature branch from that.
Dragan: Attempt to get DSpace developer to contribute to VIVO frontend. We should likely adopt Angular even though it is losing popularity.
Dragan: Vitro angular frontend and will eventually need VIVO front end.
William: What will be the comparison between VItro and VIVO frontends?
Benjamin: Should maintain the same functionality as Vitro/VIVO. Is the Vitro UI used?
Dragan: TIB uses the Vitro UI
...
Angular - CLI Overview and Command Reference
Possibly consider, nestjs/ng-universal: Angular Universal module for Nest framework (node.js) 🌷 (github.com)
- Specification
- Update the ontology
- GET all and GET one - two dynamic actions or one
- Link to specification - https://docs.google.com/document/d/1n7gSf_cSDS5mbTI4HwVGj-2sQd5if0177Nrdtri9BtM/edit#
- Topics
- Update the ontology GET all and GET one - two dynamic actions or one
Dragan: When there is ‘onGet’ property inside dynamic API, two endpoints should be generated within API documentation (one for get and another for get/id)
...
- User interface for execution of a dynamic action
- Selection of the frontend technology/framework spreadsheet
- User interface for definition of a dynamic action
- Validation of dynamic action
- Authorization - roles
...