Versions Compared

Old Version 4

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Woods

Saved on

Key

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

...

  1. Benjamin Gross 
  2. Nicolas Dickner 
  3. Huda Khan 
  4. Don Elsborg 
  5. Rachid Belkouch
  6. William Welling (star)
  7. Andrew Woods
  8. Alexander (Sacha) Jerabek
  9. Jeff Tyzzer
  10. Brian Lowe
  11. Ralph O'Flinn

Agenda

...

Draft notes in Google-Doc 

Mini-sprint focused on VIVO committer review/refactor

  1. Where did things land?
    1. Understanding changes. Heading in the right direction. 
  2. Follow-on sprint(s)
    1. Number of blockers still in progress. Andrew will put out a Doodle poll for sprint in August. 

The tale of the undesired langString data type

  1. Pull request merged: https://github.com/vivo-project/Vitro/pull/175 . 
  2. Relates to backend individual and label editing form (JSP land). 
  3. Message on email list: https://groups.google.com/d/msg/vivo-tech/bjBcAJo8ldE/kOyLHoFnCQAJ refers to not being able to edit language-tagged label in 1.10 UI so had to use the backend JSP. 

Scheduling VIVO Scholar technical iteration meetings

  1. How to move VIVO Scholar forward? Coordinate technical conversation on how to bring back into the core. Parallel conversation in leadership board. Doug will bring up during the next leadership call.
  2. May require its own call to go into depth. Architectural? Technical design? 
  3. Proposal 1: VIVO natively populates its Solr index in a way that VIVO Scholar is able to consume.
  4. Any benefit of having multiple Solr instances? Not necessarily. Could host multiple collections in a single Solr instance. Avoid multiple indexing methods/strategies. Analyze how VIVO core indexes and how VIVO Scholar indexes and attempt normalizing to be done only by VIVO code.
  5. Priority? Messaging or homonogize indexes?
  6. Attempt to deliver concrete features and avoid generalization that may take too long to design and develop. 
  7. May require investigation for level of effort to produce collection by VIVO code and consume by VIVO Scholar.
  8. Proposal 2: Messaging first and synchronizing VIVO Scholar.
  9. Initial exploration to see how configurable VIVO core indexing and evaluate possibility to extract indexing into a separate module.
  10. Follow up meeting to better understand VIVO core and VIVO Scholars to assist in next decision steps.
  11. Brian shared this link: https://wiki.lyrasis.org/pages/viewpage.action?pageId=68059316 

Actions

  •