...

1. Ralph O'Flinn 
2. Brian Lowe 
3. Huda Khan 
4. Michel Heon
5. Julia Trimmer Steven McCauley 
6. Andrew Woods
7. María Amalia Flórez HuertasRobert Nelson
8. Benjamin Gross
9. Mike ConlonKristina Heinrich
10. Don Elsborg

Agenda

1. Community updates

Michel Heon from UQAM has been working with the i8ln effort. He says it’s been easy to move the static messages but the dynamic content is harded and will require some code changes. Michel says that ontology changes are necessary but he is planning to do himsefl. Andrew would like to see the i8ln effort highlighted by the core development team.

...

2. Release Testing - 1.11.0 ends on Friday
   1. Issues

      1. 
         

         Expand
         Jira server DuraSpace JIRA jqlQuery filter=15100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

         Do Ralph or Don or others need help on anything in particular?
         Ralph: everything without a green mark or hasn’t been tested yet. For everyone older than 1.10, do a mock upgrade with the Jena components.
         Julia: I will ask Harry Thakker and let Andrew and Ralph know.
         Ralph: Anyone want to test the Harvester?
         Benjamin: I can look at that.
         Andrew: Have the acceptance tests been tweaked for 1.11?
         Benjamin: No but I add a comment about how to get them working with 1.11. Not sure if they work for me on 1.10. Link is here: https://github.com/vivo-community/vivo-acceptance-tests/issues/14
         Don: Are we testing 1.11 with Elastic?
         Ralph: Both ElasticSearch and BlazeGraph should be tested.
         Don: I will set up 1.11 with ElasticSearch. Would be great if CINECA could test BlazeGraph.
         Andrew: I will reach out to CINECA. Ralph, if we have all green check marks and everyone is celebrating, then how do we proceed?
         Ralph: I’ll be at the Symplectic conference next week and will get everything pushed out soon after.
         Andrew: I’ll be traveling next week as well.
         Benjamin: Re: the test suites,Jim’s repository is archived – should it stay archived or fork it?
         Andrew: Let’s get in touch with Jim and see if we can transfer ownership. If not, we can fork it.
         Ralph: Is this a real module and separate or a compile-time module to include in the build script? Or neither? I’d lean towards the compile-time module with the codes in VIVO Project (not VIVO community) with compile time option. This was discussed at the conference.
         Andrew: So we propose moving the test suite into the VIVO Project repo and adding it as compile-time option.
         Ralph: I’d prefer the option to include it as a flag rather than a config option.
         Andrew: Let’s explore via a ticket.
         Benjamin: For 1.11, if someone wants to use it, we should be proactive to see if we can edit the documentation in Jim’s repo or transfer ownership. Also, I ran into problems for how SOLR reads schema.xml so do we need to make changes?
         Andrew: we need more documentation since we externalized SOLR. I don’t think we have documentation in the wiki. Here’s the readme for the VIVO SOLR GitHub: https://github.com/vivo-community/vivo-solr/blob/master/README.md
         We need installation to be as turnkey as possible. But it’s reasonable for people to be able to install commodity components. But to configure SOLR further, and how to subsequently update that configuration . . .
         Benjamin: seems like we’re telling people halfway.
         Ralph: I can update that doc to add some info about setting it up. Please everyone look at the documentation and look at the developer channel to make a list with links to make it easy to find things.
         Benjamin: I know how to do it now but I can’t edit the 1.11 documentation pages.
         Andrew: Let’s give everyone the ability to edit the documentation. I’ll take the action item to give the VIVO committers write access to the documentation.

         
         

3. Sprint planning meeting
   1. Proposed topics
      1. Create ingest workflow tooling
         1. Use VIVO entity "shapes" defined in sprint-2019-06
         2. Include validation of ingested entities
         3. Allow for ingest of JSON entities (tooling to map JSON to RDF)
         4. Include optional curation step (disambiguation, reconciliation of entities)
      2. Provide an orientation to VIVO Scholar for community developers, setting up the environment, and introducing existing documentation
      3. Updating Scholars Discovery defaults for specific institutions such as TAMU including branding, look and feel etc.
      4. Based on the VSTF definitions of data shapes for VIVO and Scholars Discovery: 
         1. Updating the Scholars Discovery to include changes to the data shapes
         2. Updating SPARQL queries to pull in data
      5. Continue work on cross-linking (more info later . . .)
      6. Externalizing the triple-store in line with modularizing/decoupling (more info later . . .)
      7. i18n?
      8. Bringing in current UI improvements?
      9. Other topics?
4. Special topics for future dev calls?
5. Anyone seeing this? 

   Jira
   server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1702

6.  In-review tickets

   1. 
      

      Expand
      Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

...