...

 Indicating note-taker

1. Dragan Ivanovic 
2. Brian Lowe  
3. Georgy Litvinov 
4. Michel Héon
5. Benjamin Gross 
6. Benjamin Kampe
7. Veljko Maksimovic 
8. José Ortiz
9. Andreas Czerniak
10. Mark VaninNicolas Dickner 
11. William Welling
12. Huda Khan 
13. Rolf Guescini

Agenda

1. Questions/Issues/Pull requests/Announcements
   
   1. Conferences
      1. CRIS 2022 - report
      2. OR 2022 -  program
   2. New issues and PRs
      1. A reverse proxy (redirecting) - https://github.com/vivo-project/VIVO/issues/3698 
2. The next sprint
   1. date
      1. May 30th - June 17th
   2. Registration
      
      1. link
      2. Five registered participants so far
   3. Infrastructure
      1. Wiki page - Sprint - Dynamic API based on an ontology 2
      2. Slack channel created
      3. Project board
         1. We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
            1. but extend it with new issues (features, bugs)
      4. Starting point
         1. backend
            1. https://github.com/vivo-project/Vitro/tree/sprint-dynapi-2022-feb-staging
            2. https://github.com/vivo-project/Vitro/tree/sprint-dynapi-2022-feb
         2. frontend
            1. https://github.com/vivo-project/Vitro-angular/tree/sprint-dynapi-2022 
            2. https://github.com/vivo-project/Vitro-angular/tree/sprint-dynapi-2022-staging   
   4. Specification
      1. Link to specification - https://docs.google.com/document/d/1n7gSf_cSDS5mbTI4HwVGj-2sQd5if0177Nrdtri9BtM/edit#
      2. Topics 
         1. Update the ontology
            1. GET all and GET one - two dynamic actions or one
         2. Implement more complex workflows
            1. iteration step,
            2. conditional step
            3. Implement N3Template deletion and modification
         3. User interface for execution of a dynamic action
            1. Selection of the frontend technology/framework
               1. spreadsheet
         4. User interface for definition of a dynamic action
         5. Validation of dynamic action
         6. Authorization - roles
      3. Cleaning up not completed work at previous sprint
         1. https://github.com/vivo-project/Vitro/pull/285
            1. GET all and GET one - two dynamic actions or one ?
         2. https://github.com/vivo-project/Vitro/pull/286
            1. deletion and modification
         3. https://github.com/vivo-project/Vitro/pull/287
         4. Transforming xml notation of Dynamic API ontology to turtle/n3 notation
         5. Introducing new jena model for dynamic actions
         6. Cleaning up issues at  https://github.com/orgs/vivo-project/projects/2/views/1

Notes

1. Questions/Issues/Pull requests/Announcements
   1. CRIS 2022 - report
   2. OR 2022 -  program
   1. A reverse proxy (redirecting) - https://github.com/vivo-project/VIVO/issues/3698 
1. Conferences
2. 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)

1. The next sprint
   1. May 30th - June 17th
   1. link
   2. Five registered participants so far
1. date
2. Registration

Dragan:

Please register for dynamic API sprint, https://forms.gle/whYvMwgpbo7q6DgC9

Will prepare for the sprint in the next two weeks.

1. Infrastructure
   1. We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
   1. but extend it with new issues (features, bugs)
   1. backend
   1. https://github.com/vivo-project/Vitro/tree/sprint-dynapi-2022-feb-staging
   2. https://github.com/vivo-project/Vitro/tree/sprint-dynapi-2022-feb
   2. frontend
   1. https://github.com/vivo-project/Vitro-angular/tree/sprint-dynapi-2022 
   2. https://github.com/vivo-project/Vitro-angular/tree/sprint-dynapi-2022-staging
1. Wiki page - Sprint - Dynamic API based on an ontology 2
2. Slack channel created
3. Project board
4. 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

Georgy: Can we use standard interface and afford extensions?

William: Do we need two front ends? If dynamic, what is the difference?

Dragan: Will we need Vitro/VIVO separation after dynamic API fully supported to just two different sets of RDF?

Georgy: Planned language translations be expressed in RDF and be in the graph.

Dragan: Should all translations be served up from the backend?

William: Should consider using angular cli to initial angular front end.

Angular - CLI Overview and Command Reference

Possibly consider, nestjs/ng-universal: Angular Universal module for Nest framework (node.js) 🌷 (github.com)

1. Specification
   1. Update the ontology
   1. GET all and GET one - two dynamic actions or one
1. Link to specification - https://docs.google.com/document/d/1n7gSf_cSDS5mbTI4HwVGj-2sQd5if0177Nrdtri9BtM/edit#
2. Topics 

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)

1. Implement more complex workflows
1. iteration step,
2. conditional step

Georgy: We should not have cycles in our action ‘pipelines’ because it will be hard to calculate which parameters are required and which are provided by the action

Georgy is also working on scope computation before the sprint starts

1. Implement N3Template deletion and modification

Veljko is working on this feature and also expects to finish it before the sprint starts

1. User interface for execution of a dynamic action
   1. spreadsheet
1. Selection of the frontend technology/framework
2. User interface for definition of a dynamic action
3. Validation of dynamic action
4. Authorization - roles

1. Cleaning up not completed work at previous sprint

Dragan: 3 PRs from last sprint are not finished (and merged). It would be nice to have those PRs done before this upcoming sprint.

1. https://github.com/vivo-project/Vitro/pull/285
1. GET all and GET one - two dynamic actions or one ?
2. https://github.com/vivo-project/Vitro/pull/286
1. deletion and modification
3. https://github.com/vivo-project/Vitro/pull/287
4. Transforming xml notation of Dynamic API ontology to turtle/n3 notation

Dragan: Maybe this xml notation should be done before the sprint.

1. Introducing new jena model for dynamic actions
2. Cleaning up issues at  https://github.com/orgs/vivo-project/projects/2/views/1

Dragan: Pre sprint week (meetings every day) should be repeated for this sprint as well. I will contact people before the sprint starts to arrange these meetings.

Draft notes in Google Docs

...