2023.03.23 Meeting notes

Date

23 Mar 2023
Time: 9:00 am, Eastern Time (New York, GMT-04:00)

Meeting link https://tib-eu.webex.com/tib-eu-en/j.php?MTID=m2cd81cffb4414b48ad2d1a5218c62af1

Attendees

• Benjamin Kampe 
• Brian Lowe 
• Veljko Maksimovic 
• Georgy Litvinov 
• Mark Vanin 
• William Welling
• Dragan Ivanovic
• Miloš Popović 
• Ivan Mrsulja 

Agenda

• Announcements
  • Meeting time slot
  • New task force group members
• Current state of Dynamic API
  • Merged PR https://github.com/vivo-project/Vitro/pull/364
  • Rebase code base onto 1.14 release once it is published
• Dynamic API continuous development efforts
  
  • Dynamic forms
    • Create semantic description for forms
      • https://docs.google.com/document/d/1jIIr90vTpI4l5KZeM30f_gOc-TpmlgKol-2oOEaU2Is/edit?usp=sharing
    • Generate json from description
    • Angular-based universal form generator
  • New dynamic api endpoints
  • Replacing backend endpoints with dynamic api
    • Create and link controller
    • Web of science
    • Direct web remoting (edit this individual page)
  • HTTP Query component to access external services
  • Cache SPARQL ResultSets/RowSets
  • Parameter mappers
  • SPARQL Generate library
    • Substitutions for SPARQL queries
    • N3 generation from json data
• A brief update on Role management in Vitro and VIVO

Meeting notes

1. DSpace notation for representing generic forms

   1. DTD - https://github.com/DSpace/DSpace/blob/main/dspace/config/submission-forms.dtd

   2. XML example - https://github.com/DSpace/DSpace/blob/main/dspace/config/submission-forms.xml
   3. there is also item submission which is describing steps - https://github.com/DSpace/DSpace/blob/main/dspace/config/item-submission.dtd, https://github.com/DSpace/DSpace/blob/main/dspace/config/item-submission.xml
2. SPARQL Generate library link: https://triply.cc/docs/yasgui/
   1. Main module called Yasgui: has SPARQL editor called Yasqe and result visualizer called Yasr.
      1. Brian note (ex post facto): YASQE is used in VIVO's SPARQL Query admin page
   2. Based on codemirror: https://codemirror.net/ - library to style the editor, deciding from the data input you have.
3. Role management
   1. There has been talk over the years of being able to grant permissions to edit entities based on relationship to editor, e.g.
      1. Head of organization can edit details and working titles within organization (but perhaps not positions and official titles that can only be edited by HR)
      2. PI/Co-PI of grant can edit grant details (but perhaps not certain properties like internal ID or award amount that can only be edited by someone from the research administration)
   2. Would be nice to specify these paths and behavior using ontology instead of code.
   3. Performance of complex rules is always a challenge because they to lead to multiple small queries to triple store to check permissions.  Will need to be appropriately batched/cached to work well with external triple stores.

Action items