...

1. Questions/Issues/Pull requests/Announcements
   1. Ansible role VIVO - https://github.com/smierz/ansible-role-vivo
      1. Sandra Mierz invited to join the initiative - https://vivo-project.slack.com/archives/C8RL9L98A/p1641319536176400
   2. Reminder - Call for Interest: Integrating DSpace with VIVO 
2. The preparation for the February sprint
   1. Wiki page
      1. 2022 - VIVO Sprints
         1. https://forms.gle/GKBCDznBF2KtsEQR7
   2. Date for the sprint
      1. February 21st - March 11th
   3. Georgy's document - https://docs.google.com/document/d/1vtNIVEYWdBgV11N-wiPk_UNKpiFQ4sKetJ8elJ6xy2E/edit#heading=h.k389x4cotzuw

Notes

1. Questions/Issues/Pull requests

1. 1. Ansible role VIVO -https://github.com/smierz/ansible-role-vivo
      1. Sandra Mierz invited to join the initiative -https://vivo-project.slack.com/archives/C8RL9L98A/p1641319536176400Helps with installing VIVO the same way on multiple servers.  Checks underlying OS and chooses the appropriate tasks.  Skips tasks that have already been performed, so it’s faster to make minor changes.  Still new but starting to be used in production.
   2. Call for participation in DSpace integration project

1. 1. 1. Write directly to Dragan with any questions, or to email listed on call for participation:  email will be answered by Dragan or Laurie Arp.
      2. Estimation of total project is around 150 hours.  50 to 75 hours per person over the course of 3 or 4 months, assuming 2 to 3 persons participate.
      3. Follow-up project is planned, which will have a budget and estimated hours roughly double this project.  Those who participate in the first project will have priority in the second.
2. The preparation for the February sprint

1. 1. Wiki page
      1. 2022 - VIVO Sprints
         1. https://forms.gle/GKBCDznBF2KtsEQR7
   2. Date for the sprint
      1. February 21st - March 11th
   3. Georgy's document -https://docs.google.com/document/d/1vtNIVEYWdBgV11N-wiPk_UNKpiFQ4sKetJ8elJ6xy2E/edit#heading=h.k389x4cotzuw  
   4. Discussion:
      1. Dragan: How should calls be organized leading up to the sprint?  Separate interest group?
         1. Georgy:  If we use only the time during the regular calls, other topics may suffer.
      2. Dragan:  [given lack of interest in separate interest group] We should probably use time on the Tuesday calls to start with.
      3. Use signup form (above).  Includes some questions in addition to availability.
      4. Dragan:  In other work I have used a business process language.  There is an open-source Java library, Camunda, that may have concepts that would be defined in the ontology for the dynamic API. 
         1. We can develop our solution from scratch, but can check things like Camunda to see if there are concepts we missed.
         2. Georgy: I thought about creating processors that would process messages on the fly. If there will be a lot of interactions with the API, we should think about the effectiveness of this.  If we don’t have to process RDF on each request it will be much more efficient.  There is already something like this in Vitro.  We can reuse components.  We can create buses in Java that represent the components, and for each message flow processing chain, we can use those components.
         3. Dragan:  Will there be multiple endpoints?
         4. Georgy:  Thought about splitting the problem into multiple parts.
            1. Represent the functionality that already exists in VIVO/Vitro.
            2. Map processors to the RESTful API.
         5. Georgy:  Richardson Maturity Model is a good way to go.
         6. Dragan:  Agree; not necessary to be in complete compliance with all REST principles.
         7. Georgy:  Some APIs should be hidden from certain clients for security reasons.  Endpoints will only be available internally.
         8. Dragan:  Why not use just basic Java invocation for the internal APIs?
            1. Georgy:  Hard to know up front what will only be useful internally.  REST API is important for decoupling, so working on it accomplishes two tasks at once.
         9. Dragan:  For the first sprint, a good goal is to keep the same Freemarker UI, but feed it from the REST API instead of Java object template models.
         10. Georgy:  Need more examples, more complicated cases, more components to flesh out existing workflow diagrams.  Custom entry forms are a good starting point because they are a pain.
             1. Dragan:  Matthias and Christian have added some form examples to the document.
         11. Dragan:  How can we organize, work in parallel?  Need list of issues and can organize them in the project board.  Are we ready now to create issues?
             1. Need some proof of concept with the ontology, maybe not with all concepts.
             2. Simple example with one or two actions.
             3. Add to project board; someone can take that issue in the sprint.
         12. Georgy:  I will go over my document and identify any remaining theoretical issues to be resolved.
         13. Dragan:  Important to have a realistic goal for the sprint.
2. Other topics

1. 1. 1. 1. 1. Georgy:  More about Ansible roles.  Work with different distributions?  
               1. Sandra:  Different roles: Tomcat role and Solr role are reused from different sources.  Can set variables if you already have a user, etc. you want to use.  Roles list the distributions they support.  Not all distributions will be supported, but many will.
               2. Georgy:  What constraints or limitations are there if you want to, for example, create a new theme?  
               3. Sandra:  Can run it multiple ways. Default values come from the role and are listed on the GItHub pages, but you can override them.
            2. Dragan:  VIVO conference.  WIll likely be online, sometime in June or July.
               1. CRIS conference will have a VIVO track.  Planned for on site in Dubrovnik, with deadline in February. 
            3. Parting comments:  Please register for sprint, DSpace project.

Draft notes on Google Drive

...