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

Agenda

  1. Mini-sprint focused on VIVO committer review/refactor: July 14-16th
    1. Next i18n sprint? - July 24th? Aug 24th?
    2. Scrum board
    3. Needing review / merge:
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    4. Concerns:
      1. Homogenize design for filtering languages between frontend and backend approaches
      2. Upgrading... reorganization of firsttime/everytime
      3. Resolution on split-out of language files:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  2. 2020-07-15 - Special Topic - VIVO Scholar Next Steps
    1. What is your opinion?
  3. Renaming of 'master' branch? (ZDNet, BBC)
    1. DSpace has done it
    2. Fedora has done it
  4. Moving priorities forward: Data ingest
    1. Task force!
      1. Deliverables?
      2. What are the use cases?
    2. Tools:
      1. RML-Mapper
      2. Ingest Tools - Who Is Using What
    3. Entities (scholars-discovery model) (fly-in discussion):
      1. Person, Grant, Publication, Authorship, ...

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
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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 

Draft notes in Google-Doc 

Mini sprint for i18n

Core discussion on regression test framework.

Team has exercised tests on all of the different pages.

For team to do a merge committer team needs awareness of the changes in the i18n branch.

Ideally do some refactoring. A merge this week isn’t likely but we can progress.

Aside - last week discussion re: next sprint - 24 might have meant July 24 ( Fri) or Aug 24 ( Monday)

Decisions on next sprint??

Ben - no more time this month, same for Don and Brian, Sacha

August 24th sprint? - does bump into school return

Andrew thinks this next sprint is i18n

Wants to fix some of the outstanding issues - firsttime/everytime file shifts, depending on analysis of this week's micro sprint

Next sprint would be to finish tickets identified as blockers for Beta. So these tickets would be moved through, committed to i18n branch

Ralph, it’s been a while since we had a non i18n sprint, have next sprint topic be more open. Eg ingest. Don agrees

Don wants the minimum amount of work possible to merge i18n branch into master.

Sacha mentioned that there was reluctance to introduce buggy code.

Ben - issue is that as we move on to different things we never come back to fix the bugs.

Ralph - have a new i18n sprint along with focus on data ingest

Andrew - jira scrum board does have the blockers

https://jira.lyrasis.org/secure/RapidBoard.jspa?rapidView=36

Next steps - can we do data ingest and close out i18n

Which tickets are the minimum for i18n

In todo and in progress - it’s the bugs

In review - this has been done, 

1848 is an improvement and not a bug, do we have to do this then

Brian - thinks this is already in it. 

Andrew , Ben - no

So perhaps we punt

Brian is checking compares in git, seeing strange changes like comments and missing comments. Wants to ensure that junk doesn’t get introduced.

So with .n3 files, if things are removed, want’s to verify why things are removed. Verifying suspicious changes in code. Then not committing known bugs.

Andrew - summary - focus on this sprint is:

  • Team understanding what’s there
  • Identify blockers besides bugs. Are there things that surface which qualify as blockers
    • Understanding in general what’s there for comfort
  • Working additional bugs in todo column

Once we do all of this, as individuals pick up tickets and resolve this, concern is we don’t have the bandwidth that the resolved ticket isn’t taken across the finish line.

Don - will continue testing with 3rd tier build not using i18n features

Andrew - as people continue with i18n, he release languages to maven central, made some fixes, 

Should complete 1903 for Don to continue because this has Andrews fixes for the pom and maven central lib dependencies such that Don does not have to do any extra work for this testing persona.

Special topic call

What do we as a community want to see to move it forward?

Current pattern ( slurp data ) out of vivo, stuff in index, expose to graphql

Goal is to have VIVO create the necessary SOLR index for vivo scholar.

This will make it easier for existing institutions to add on vivo scholar.

William - agrees but this is easier said than done. Didn’t think up front on integration because initial scope was just to harvest VIVO data and create an read only index.

Don wants graphql schema to be a reference spec

Andrew - can this be used for ingest

Willam - perhaps, issues arise with lists of nested objects, but the schema can be

William - as part of index rebuild, would like to have it be message based. 

Andrew - would a messaging pattern simplify things

William - it’s not the same code base which does the transformation. Events and messaging would make it more Enterprise based. So we can avoid the monolith this way.

Should new indexing be i18n. William - yes. 

Don wants to do this to expand the dev group for new indexing.

Andrew - i18n jira solr ticket - https://jira.lyrasis.org/browse/VIVO-1770

Renaming master branch - github issue - when do we do this.

Ralph - could start looking anytime. Ben - have done it before, so not a big deal for him. Did github change default. 

Andrew/Don - not yet

Ben concerned about new repo’s being created with old master naming convention

Jeff Tyzer - interested in ingest approaches. 

Andrew wants to see someone move ingest forward.

Ralph is moving this forward. Pulling together old artifacts and working on wiki page.

Actions

  •  



  • No labels

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