Date

Call-in Information

    • Time: 10:00 am, Eastern Time (New York, GMT-04:00)

      To join the online meeting:

      • https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09

        Meeting ID: 843 7861 5572
        Passcode: 556561
        One tap mobile
        +16699006833,,84378615572#,,,,*556561# US (San Jose)
        +19292056099,,84378615572#,,,,*556561# US (New York)

        Dial by your location
                +1 669 900 6833 US (San Jose)
                +1 929 205 6099 US (New York)
                +1 253 215 8782 US (Tacoma)
                +1 301 715 8592 US (Washington DC)
                +1 312 626 6799 US (Chicago)
                +1 346 248 7799 US (Houston)
                877 853 5257 US Toll-free
                888 475 4499 US Toll-free
        Meeting ID: 843 7861 5572
        Passcode: 556561
        Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4

      Slack

Attendees

  1. Dragan Ivanovic 
  2. Benjamin Kampe 
  3. Veljko Maksimovic 
  4. Georgy Litvinov 
  5. William Welling 
  6. Kevin Day 

Resources

Agenda

Notes 

  • Organization improvements

DI: The sprint meetings will be organized on March 2nd, 4th, 7th, 9th, 11th at 10am Eastern Time.  

We went through Project board Track 1, 2 and 3. 

Track 1 is related to development of Dynamic API ontology and expressing actions in this notation.  Definition of the ontology is an iterative process, it might be that we notice some mistake in the design of the ontology when we try to implement that or apply that to a real use case. In that case we will come back for modification/extension of the ontology. It seems as a completed task, except for the GitHub issue https://github.com/vivo-project/VIVO/issues/3657. GL will help in the description of this issue. Basically, an RDF class for API should be added in the ontology, it should have data properties for description of API and version. WW: Do we need a link between a class representing an API and resources available through that AP? GL: Probably yes. This class will be used only for Generating OpenAPI specification for REST api for certain groups of resources. ML will try to define real examples of custom actions, probably for this custom form (menthoring) - https://github.com/matthiasluehr/vivo-custom-forms/tree/master/mentoring. At the moment, he might only validate loading of the action, the N3Template operation is not functional yet.  DI will write a draft version of documentation of Dynamic action ontology at wiki - https://wiki.lyrasis.org/display/VIVODOC112x/Dynamic+API+ontology. DI: do we need a BlockStep for conditional step and iterative (loop) step. GL: No, it might be implemented by nextStep property for conditional steps, and GL will provide an example of how a set of steps might be in the body of loop step. Moreover, GL reminded us about BL suggestion to make possible integration of a complete action as a part of step (the action is implementing Operation interface). 

Track 2 is related to loading of rdf classes to java representation.  ConfigurationBeanLoader was getting stack overflow while trying to instantiate objects with relation loops. It is fixed (see https://github.com/vivo-project/VIVO/issues/3675), and that was necessary to be fixed for implementation of loading loop steps. Java beans (https://github.com/vivo-project/VIVO/issues/3619)  and mappings of data and object properties by using annotation Properties (https://github.com/vivo-project/VIVO/issues/3660) have been almost completed. It should be extended with LoopStep, maybe some customization for ConditionalStep and N3Templates are still needed. Role class will probably be postponed for the next sprint. Resource and Action pools have been implemented. We might consider reorganizing code after the sprint, i.e. it might be that generic root such as AbstractPool might be used in some other segments of Vitro application (at the moment it is part of the dynapi package, we might consider moving to other package and refactoring that class if needed for reusage).BK is working on the implementation of ChangeActionListener. 

Track 3 is related to execution of a dynamic action. VM is finishing implementation of the SolrOperation. GL is hoping to finish the issue of computing parameter scopes in the next two days, and after that will implement ConditionalStep. VM will work on N3Template, BL should be a supervisor for that task. GL: Validation of provided data (https://github.com/vivo-project/VIVO/issues/3623) should be performed at the beginning before starting execution of the steps. The action is executed only in the case provided data are valid. Authorization will be postponed for the next sprint. We didn’t discuss the last one issue in this track (https://github.com/vivo-project/VIVO/issues/3663), and will continue at the next meeting.  

Draft notes on Google Drive


Task List


  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.