Date

Call-in Information

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

To join the online meeting:

Slack

Attendees

(star)  Indicating note-taker

  1. Brian Lowe
  2. Georgy Litvinov(star)
  3. William Welling 
  4. Huda Khan
  5. Alexander (Sacha) Jerabek 
  6. Dragan Ivanovic
  7. Sandra Mierz  

Agenda

  1. Welcome Dragan Ivanovic as tech lead
  2. Mailing list issues
    1. schema.org missing authors? https://groups.google.com/g/vivo-tech/c/MAoUdgZYOwo/m/uPswpzD_AgAJ?utm_medium=email&utm_source=footer
  3. 1.12.1 status
  4. Small(er) development items for 1.13
    1. Search features related to SKOS / expertise?
      1. CRDC: https://github.com/UQAM-SB/CCRD-CRDC/ of CRDC vocabulary.  https://www.statcan.gc.ca/eng/subjects/standard/crdc/2020v1/introduction .
    2. Sprint candidates? https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
  5. Defining shapes or subgraphs for use in APIs, edit forms, indexes etc.
    1. Diagrams:
      1. existing architecture: https://docs.google.com/presentation/d/1raO98mklGUQgAc6wMMbgDEsHVk1zoCA3bq4Fyy21GjI/edit?usp=sharing 
      2. Georgy: existing versus proposed
    2. JSON entities in/out
      1. Apache Marmotta LDPath syntax https://marmotta.apache.org/ldpath/language.html
      2. JSON-LD framing: https://www.w3.org/TR/json-ld11-framing/
        1. Is round-tripping a potential benefit?
      3. Defining exercises for evaluation
    3. Ontology model for defining form behavior
  6. Moving Scholars closer to the core
    1. Build messaging system first? versus
    2. Original option of typing into existing document modifiers:
      1. "win/win" opportunity: Scholars and VIVO both eliminate some complexity
      2. converting Scholars SPARQL queries to VIVO DocumentModifiers
      3. replacing URIFinders with fast, reliable Solr lookups 

Needing reviews

    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. https://github.com/vivo-project/Vitro/pull/242
    3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

References

  1. 2019-01 Architectural Fly-in Summary#201901ArchitecturalFlyinSummary-Ingest
  2. VIVO in a Box current document for feedback:

Future topics

  1. Prioritizing and planning post-1.12 development
  2. Forward-looking topics:
    1. frameworks: Spring / Spring Boot / alternatives
    2. Horizontal scalability
    3. Deployment
    4. Configuration : files / environment variables / GUI settings
    5. Editing / form handling
    6. Adding custom theming without customizing build
  3. Post-release priorities
    1. Ingest / Kafka
    2. Advanced Role Management
    3. Moving Scholars closer to core - next steps
  4. Vitro JMS messaging approaches - redux
    1. Which architectural pattern should we take?
    2. What should the body of the messages be
  5. Incremental development initiatives
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

  1. Status of In-Review tickets

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

Welcome Dragan Ivanovic as tech lead

Dragan Ivanovic is a new tech lead. He is a full professor at the university of Novi Sad, Serbia and engineer and author of CRIS system at his university. Excited to join VIVO and collaborate in the next period. In following weeks Brian will be gradually transferring duties to Dragan in the next couple weeks. 

Mailing list issues

    1. schema.org missing authors? https://groups.google.com/g/vivo-tech/c/MAoUdgZYOwo/m/uPswpzD_AgAJ?utm_medium=email&utm_source=footer

Schema.org missing authors problem.  Strange issue. It looks like schema org with type=review Maybe no authors lead to markup errors. This issue needs more investigation. 

From chat:

https://github.com/vivo-project/VIVO/blob/main/webapp/src/main/webapp/templates/freemarker/lib/lib-microformats.ftl

https://github.com/vivo-project/Vitro/blob/4ed88b81e3738fccbf3beef677bc165bcaa37179/webapp/src/main/webapp/templates/freemarker/body/individual/individual-vitro.ftl

‘<#import "lib-microformats.ftl" as mf>’ and ‘<@mf.sectionSchema individual/>’ within the latter file calls the macro code in the former file

1.12.1 status

1.12.1 release content is ready to go. We can 1.12.1 branch from main, need to confirm that from Ralph to make sure it won’t break anything. There was weird issue with 1.12 release when glitch happened and release became broken because sonatype policy doesn’t allow replacing bad artifacts. And previously some unit tests were dependant on other unit test. We fixed that by running test alphabetically and fixed underlined (removed dependencies between tests) problem. Hopefully later this week we will be able to release 1.12.1 and fully focus on 1.13.

Small(er) development items for 1.13

    1. Search features related to SKOS / expertise?

      1. CRDC: https://github.com/UQAM-SB/CCRD-CRDC/ of CRDC vocabulary.  https://www.statcan.gc.ca/eng/subjects/standard/crdc/2020v1/introduction 

This small feature that could be added to 1.13 could add better support for reasoning in relationships with SKOS vocabulary. We can use SKOS rather it is done the way it is now. That kind of a feature could be good for everybody. We talked about reasoner plugin. Seems like an attractive thing to work on. At the same time will there be companion features that could make VIVO even more useful. 

Can we formulate that kind of feature to better rank people? Does it seem interesting and relevant? It could be more future looking thing. 

Benjamin raised a problem of boosting, because boosting was removed from Solr. We can plan that for 1.14. 

  1. Sprint candidates? https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing

Things that we find useful for our institutions. 

There was an attempt to create war file with VIVO before last release, but that wasn’t practical for that time. Changing that behaviour at that point broke behaviour. General installation approach is the same but for the next release we could do something to move towards that direction. That is one that is on the list, but this is something we need to work with. 

Making VIVO extendable online without need for editing files could be very useful. 

Adding some additional stylesheets should be simple without rebuilding the whole system.

We should also think about how to make interface development easier for custom implementations. One option is to use the third tier. Or is it could be reasonable to use default build with own overwritten files out of that installation.

On one hand we want to be standard and on other hand we want to improve user experiences. Is there a general idea of a feature to create customization that could be used on other installations? 

Decoupling frontend and backend is one of important goals for now.

Priorities should be ranked and resolved by ranks (take into consideration best practices). We could add columns to the spreadsheet and rank issues and features. 

JIRA is going to be migrated to free JIRA could. Whether or not we want to save them or use them will be discussed at the Lyrasis meeting tomorrow. 

Most of us prefer Github to JIRA. Where features will be touching VIVO and Vitro should go? 

Draft notes on Google Drive



  • No labels

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