Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Andrew: this exercise in general is helpful in teasing out how we can plan  for next sprints. There is a need for a higher level discussion that needs to happen, some of these initiative are focused on the core VIVO and some are for a new VIVO. Work of the Product Evolution Group needs to be consulted.  of the work that product evolution has been doing and what vivo can be - look at product evolution TG.   We are at a crossroads and need to take a position how are we supporting, or not, potentially two application; the new one and the existing one.

Christian: Not clear how can we serve two applications. Decoupling the architecture is to too vague.

Paul:  Not sure that our users, care about distributed search. Ann 

Ann: all opinions are expressed by Mike’s comments and summary as she was part of the scoring group.

Tom: decoupling makes a lot of sense and resonates with what Stanford is already doing. It will intersect with their work formalizing APIs and broader VIVO. In terms of the presentation leyers, visualizations, can be swapped across different tools, but their focus is on research intelligence. Not sure how the work of the Product Evolution group is aligned. He wouldn’t rank VIVO Cross-Site search as a top priority, but VIVO Combine is their priority and he agrees with that and also agrees with the assessment of the scoring group that this is a grantable project.

Mike: thinks that all Qs raised during this discussion need to be conveyed to the community as some artefact, a statement to keep the community informed. This should be the next step following the conversation.

FredericoFederico: for Chinecathem, multi language and presentation technology (leyerlayer) are very important and already supported. They can commit development support after the end of October. 

Anna : agrees with the scoring results results since she is part of the discussion.

DoughDoug: he agrees with decoupling the architecture - display is a main issue for them, if they ecouple decouple the arch architecture they can tie everything in the backend.

Christian: we they will ut commit some manpower on multi language support and elasticsearch

Violeta: agrees with the scoring results results since she is part of the discussion.

Muhammad Javed: cross site search not important for each institution but important overall to the community and can also be grant supported. He believes we can support two different apps and decoupling is important. VIVO combine Combine is a key part.

DJ Lee: agrees with the scoring group report.

...

Alex Viggio: He agrees with the priorities that are identified, multilanguage, accessibility, modernizing presentation tech, decoupling tech, elasticsearch, visualizations, reports. VIVO combine Combine will be a good value to the community and they are devoting time of one developer to the work.

Erin: amount of people that are contributing the resources - people is very good. The idea of going after a grant for vivo combine VIVO Combine is great aso this direction is very helpful. 

Joe Zucca: the main ideas are supported, architectural concepts are important, VIVO  combine Combine idea is great. Anything that improves workflow gets a huge thumbs up from UPenn.

...