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. Ralph O'Flinn 
  3. Georgy Litvinov (star)
  4. Nicolas Dickner 
  5. Alexander (Sacha) Jerabek 
  6. William Welling
  7. Benjamin Gross 
  8. Benjamin Kampe 

Agenda

  1. 1.12 release
    1. Issues reorganized into v1.12 and v1.13 releases in JIRA
      1. https://jira.lyrasis.org/projects/VIVO/versions/15140 (1.12)
      2. https://jira.lyrasis.org/projects/VIVO/versions/15542 (1.13)
      3. Cleaning up older "unreleased" versions and dates?
      4. Several bugs have been assigned 1.13 or 1.12, but many older issues are still not assigned a version. Anything that needs revisiting before we release 1.12?
        1. 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.

    2. Open pull requests:
      1. https://github.com/vivo-project/VIVO/pulls
      2. https://github.com/vivo-project/Vitro/pulls
    3. Blocker issues - including older issues that we should close if they are no longer reproducible.
      1. 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.

    4. Sitemap improvements
      1. Multiple linked sitemaps for >50K URLs?
      2. Retrieve items from search index to avoid submitting "hidden" persons?
  2. Future of JIRA
  3. Embracing standard approaches
    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
  4. Post-i18n priorities
    1. VIVO-in-a-box
    2. Ingest / Kafka
    3. Advanced Role Management
    4. Moving Scholars closer to core - next steps

Future topics

  1. Vitro JMS messaging approaches - redux
    1. Which architectural pattern should we take?
    2. What should the body of the messages be?
  2. 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

  1. We now have two new releases 1.12 and 1.13. Need to look at old issues. If you have a few minutes look at old issues to figure out if they are important.
  2. Overall review of 1.12 release. 

Need to look at Strange status at 15140 Weird bug between github and JIRA. Maybe that happens because of old branch to be deleted. Need also to have quick glance at TODO list.

Some forms appear to be bad according to TODO list.

Should we fix it before 1.12 release?

VIVO-1820 Does not have ability to create new individual. UI is not intuitive. Maybe describe this thing better or allow creation of new value. 

Maybe we can take a note on these issues, not to ignore these thing entirely.

One possible solution could be to change misleading label in VIVO-1820. 

VIVO-1820 should be a blocker for 1.12 release. 

  1. Existing blocker issues:

VIVO 1976 related to search reindexing. Leaky behaviour. Looks like cause was found. Caching looks fine, search indexing looks fine. Interesting code to explore. It might have other performance improvements. Solution of this could have many positive effects.

VIVO 1910 Sitemap xml. That turned out to be small issue it was trying to retrive profile for every individual. Before retriving persons Brian added 50000 limit on the query. Maybe we could split sitemap into multiple files with 50000 entries each in future.

Risk with this approach that doesn’t include actual persons and instead list persons removed from search index.Benjamin and Ralph said that it could be improved later.

VIVO-1736 marked as a blocker. The problem occurs when a user is associated with a profile, then the profile itself it deleted. I am guessing the link to the (now non-existent) profile remains and the redirect code doesn't have any logic to deal with this possibility.

This doesn’t execute redirect for some reason. Benjamin Gross will try to get some logs for this issue. We should not let this go by. 

We are close to RC1 point. 

  1. Are we happy with JIRA or we should move to github? It will be expensive to have confluence and JIRA at the same time. Lyrasis hosted JIRA going to expire by the end of october. We could move to JIRA Cloud or maybe this is the time to think of moving to Github. It is better to have only one issue tracker. Moving to Github is good option.
  2. Moving towards standard frameworks and technologies. 

Some questions arose:

What we could realistically do in short term? 

Could we create an experiment with Spring Boot?
What do we want from Spring Boot. Dependency injection, Services? 

Should we create Spring Boot controllers?

How much effort needs to rewrite it?

VIVO is hard with customization. Rewriting code with Spring Boot could be an effort but it could simplify customization.

Ralph volunteers to work on a proof of concept with Spring Boot with advice/assistance where possible from William.

Draft notes on Google Drive



  • No labels

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