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. Benjamin Kampe 
  3. Georgy Litvinov 
  4. Michel Héon 
  5. William Welling 
  6. Benjamin Gross 
  7. Ralph O'Flinn (star)
  8. Don Elsborg 

Agenda

  1. Mailing list / Slack discussion
  2. Announcements / updates
    1. VIVO in a Box status / update proposal doc
    2. VIVO WCAG 2 A/AA  accessibility audit results from Deque
  3. Moving Scholars closer to the core : continuing discussion from last committers' meeting
    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
  4. Speeding up / simplifying our processes: how do we turn out releases more quickly?
  5. 1.12.0 RC1 issues to test/merge:
  6. 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.

  7.  Testing / results: Release Testing - 1.12.0

Future topics

  1. Prioritizing and planning post-1.12 development
    1. https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
  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

  1. Bruce will take notes
  2. VIVO-In-A-Box - Bruce is asking the Developers to answer the following questions:

What are the development tasks that are needed in the short term. (Create user stories?).

How can these tasks align with long term goals

Assume we want the VIAB project done in a year, is the project feasible?

  1. Discussion of the VIAB Proposal:

Wasp to VIVO - CLarivate tool for data ingest from WOS.

William talked about the issue of disambiguation and deduping.

Allowing faculty input is very important as most external data sources, like Web of Science, because these external sources of data rarely have equal coverage across all disciplines.  

Issues with dependencies between different groups - community has both long term and short term goals.  How to align all of these goals, the efforts of the different tasks forces, and the needs of the community.

The Developers need to know what Clarivate is willing to commit to such as hosting and how much it costs.

Bruce will improve the VIAB proposal in terms of the different customers that would use the system.

Michel discussed internationalization of VIVO to support recruiting new VIVO implementations in non-English speaking countries. 

Brian emphasized using existing VIVO successes as much as possible.  Michel talked about the difficulty of creating the interface that presents the simplified user profile.

Bruce should not be taking notes.…..

Brian mentioned other topics:

  1. Issues with the release.  There is still a need for testing and evaluating.  Please do what you can so we can merge the code release.
  2. VIVO 1999: this version number got missed.  Brian put in a request to update the versioning numbers.  https://github.com/vivo-project/Vitro/pull/239

Draft notes on Google Drive



  • No labels