...

1. Questions/Issues/Pull requests/Announcements
   1. Mike Conlon stepping away from the VIVO community 
   2. VIVO 1.12.2 release published
   3. Call for Interest: Integrating DSpace with VIVO
      1. The team selected
      2. planning to present at the Open Repositories 2022 conference
   4. CRIS conference with VIVO track
      1.  CERIF 2 VIVO mapping - https://docs.google.com/document/d/1qJgxuIdMBSdL6c_w7BADOPhazjE6UKl8I-EawdwRuqA/edit?usp=sharing
         1. submitted
2. The preparation for the February sprint
   1. Registration
      1. https://forms.gle/GKBCDznBF2KtsEQR7
   2. Date for the sprint
      1. February 21st - March 11th
   3. Goal, idea and approach - https://docs.google.com/document/d/1vtNIVEYWdBgV11N-wiPk_UNKpiFQ4sKetJ8elJ6xy2E/edit#heading=h.k389x4cotzuw
   4. Specification - https://docs.google.com/document/d/1n7gSf_cSDS5mbTI4HwVGj-2sQd5if0177Nrdtri9BtM/edit?usp=sharing
      1. Ontology
         1. https://webprotege.stanford.edu/#projects/b7ebb822-2a8d-4fd3-ba36-5b9e8bd3f400/edit/Classes
         2. https://drive.google.com/file/d/1Wou_KWJfAm9cwRVALoV5QvDiRD3mnYQW/view?usp=sharing
      2. The use case examples
         1. https://app.diagrams.net/#G176In5cQ-tWecx0aP0ILBTODuCoiYk-0o
            1. https://drive.google.com/file/d/14oVxX2xVMdvMAc0lTc7hUJYnKJUPXUTY/view?usp=sharing
         2. https://github.com/matthiasluehr/vivo-custom-forms/tree/master/mentoring
   5. Implementation of proof-of-concepts
      1. https://github.com/litvinovg/Vitro/tree/dynapi
   6. Project board - https://github.com/orgs/vivo-project/projects/2/views/1
   7. Branching strategy - Branching strategy for a sprint using GitHub
   8. Commit and PR messages conventions - https://github.com/vivo-project/VIVO/blob/main/.github/PULL_REQUEST_TEMPLATE.md
   9. Pre-sprint meetings

Notes

Mike Conlon, one of the first VIVO developers is stepping down from VIVO community

New release, 1.12.2 is published. Installation should work, Dragan tested it.

Candidates for VIVO-DSpace integration are selected, and the first results will hopefully be presented in June. Abstract for the CRIS conference was submitted as well.

Extra meetings will be held tomorrow, Thursday and Friday to prepare for next week's sprint. Dragan may miss Friday's meeting. In that case someone else, Georgy perhaps, should lead the meeting. Same Zoom link will be used for these meetings. Project board on GitHub is already created, but new issues will be added. A Wiki page for branching strategy is also added. Here are also commit message conventions that should be discussed further with William. Georgy suggested these commit conventions: https://www.conventionalcommits.org/en/v1.0.0/

Georgy added example code for Actions (prototype REST endpoint). Test resource should point to the RPC, which then points to the action name that should be executed. Bindings between RDF classes and Java classes also exist. More then one validator can be added to the parameters, in that case addValidator method will be called multiple times. Parameter types will also be defined within .n3 files. It is possible to define non-primitive parameter types such as Researcher or Grant. We can add constraints on how many values each parameter type should contain. All CRUD actions will be available at the same URL, just with different HTTP methods. Custom actions though will require additional info within the URL. ServletContextInitializer for DynamicAPI is also implemented. Two big parts of DynamicAPI are the REST part, which maps HTTP requests to Actions defined within our DynamicAPI. Endpoint for Actions (creating, modifying, deleting etc) could also maybe be implemented in this sprint.

Sprint participants should check specifications, github code and github examples, so that if there are any suggestions or questions we can discuss them before the sprint starts.

William: Some default actions should exist after this sprint. But if we do it just by loading actions from the triple store (RDF) upon initialization, we are just adding more technical depth. We should probably have a separate service with crud operations for managing those actions. Some type of DAO/Repository should be implemented to bridge the gap between REST HTTP request (REST controller) and the triple store.

Georgy: There should be an action for creating/updating/delete new actions.

Commiters should review Georgys Vitro PR before the sprint starts.

Draft notes on Google Drive

...

•  Dragan Ivanovic to work on definition of tasks
•  Georgy Litvinov to work on definition of tasks
•  All sprint participants - to review/update Sprint - Dynamic API based on an ontology wiki pagecomment Specification
•  All sprint participants - to consider to register and participate in the sprint. Registration is here: pre-sprint meetings - Wednesday, Thursday, Friday at 10am ET (4pm CET) - https://forms.gle/LQjiyMFd1NL3B63v5
•  All - Add comments to Georgy's document
•  All - Add comments to Specification
• lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09
•  VIVO committers team - to review PR - https://github.com/vivo-project/Vitro/pull/253