...

Attendees

 Indicating note-taker

1. Rachid Belkouch
2. William Welling 
3. Brian Lowe 
4. Andrew WoodsDon Elsborg 
5. Alexander (Sacha) Jerabek 
6. Ralph O'Flinn
7. Benjamin Gross
8. SanthoshMichel Héon
9. Huda Khan

Agenda

1. Announcements
2. What has happened in the last two weeks?
   1. Mailing list activity
      1. Updating URIS via Database.
   2. Additions to ontology, looking for quick review/merge: PR-165
   3. Setting default tab on Article view... per user
3. Renaming of 'master' branch?
   1. Update: "GitHub to replace 'master' with 'main' starting next month"
4. Sprint update: i18n
   1. Needing review:

      Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1848

   2. Wrap-up call Friday... 11am ET?
5. Moving Scholars closer to core - next steps
   1. SelectQueryDocumentModifier
   2. Entities: Collection, Concept, Document, Organization, Person, Process, and Relationship
   3. Configuring Solr
6. Moving Data Ingest Task Force forward
7. Simplifying Solr auto-configuration -

   Jira
   server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752

...

Draft notes in Google-Doc 

Announcements, updates:

RoF continued testing from last sprint, versions of Solr, did not find anything new, also looking at CSS

Aw: should coordinate with Mathias about CSS

Aj: problems installing, running VIVO, permissions issues and others

RoF: have a procedure to get it going on WSL on Windows

Bg: seem to be more issues with permissions, variations on java, tomcat installations.

RoF: various distributions do things differently, if you install everything to ‘home’ you should not have permissions problems.

Aw: should not be this hard to install VIVO,

RoF: see full development VM setup in developers wiki

Aw: should be a .war file and take build out of picture, and just drop a .war file into webapps directory, with prereqs as tomcat and solr. More advanced installs can be done, but there should be a simpler option. Are there other concerns with the simple .war file option?

Bg: .war file does not solve problem of permissions, variations of tomcat installations may be better to have a docker option.

Aw: we discussed docker previously, for now it is not a option for default version

Mh: we had many reasons to install VIVO, and various versions dev, test, different environments. The VIVO dev environment we created has everything bundled and works. Not reasonable to have a common use case of installations.

Bg: we did have a previous version with tomcat included in a zip file, compiled and deployed. Only thing needing to be configured is where tomcat is, and how solr is set up. 

Aw: we used to have regular ‘install fests’, this may be a longer term goal. May be worthwhile to have 3 versions: quickstart, production, development. Any other ideas for low hanging fruit for installation problems?

Bl: could have better error messages to catch maven issues that aren’t flagged when build fails. Jim did a lot of work in smoke tests to alert when things were amiss. Should double check that everything works as expected. For simpler process, we should make sure smoke tests, verifications, error messages work and are adequate.

Aw: also, should look into auto-configure solr, can be avoided with apis.

Mh: UQAM dev project is designed for non-java devs who need to work with VIVO, lot of automatisms built in, maven functions, etc.

Questions coming out of the community

2.a.i: Updating URIS via Database

2.b.: additions to ontology, PR-165, by this week

2.c: is there a simple way to set it so that click on Article goes to view all? (RoF has answered this)

I18n update:

Mh: do we have a need to move all ontology files into TTL format? Too many different formats right now.

Bg: this should be easier to do now that ontology files have moved into firstime.

Mh: problem of firstime is affected by TTL formats.  

Aw: in serialization comments were lost, and if we re-serialize it all local changes get disassociated from source files. Wary of addressing re-serializiation in context of i18n.

Bl: change introduces a huge risk for minimal benefit

Mh: I don’t think the risk is that severe. But yes, you do lose the comments in the ontologies, so this is a drawback.

Bg: some risks are for those with third-tier, overwriting files that no longer exists result in duplicate triples.

Bl: it is a big maintenance headache when you go to upgrade, lots of potential chaos.

Bg: messy solution is to change them all to turtle.

Mh: we only change the extension not the filename.

Bl: yes we could address this by omitting file extensions. But not significant enough benefit for effort required.

Mh: for i18n it becomes important since files get translated and this is more difficult with rdf format, we had to translate them into more human readable ttl format. So those who want to create a new language, they will change formats to ttl.

Bl: rather focus on moving translation away from rdf syntax

Aw: maybe we put on hold re-serialization, until afterwards.

Aw: relatively pressing issue (VIVO-)1918? Can anybody handle this?

Bl: can do it, but no time in september?

Aw: for those who have time during this sprint, can we have a wrap up call this friday and finish up on outstanding tickets? Will send out an invite.

Actions