Skip to end of metadata
Go to start of metadata

Date

Call-in Information

Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)

To join the online meeting:

Slack

Attendees

(star)  Indicating note-taker

  1. Ralph O'Flinn 
  2. Andrew Woods
  3. Brian Lowe 
  4. Don Elsborg 
  5. María Amalia Flórez Huertas 
  6. Huda Khan (star)
  7. Benjamin Gross
  8. William Stanley Welling

Agenda

  1. Community updates
  2. VIVO 1.11.0 release candidate planning (and testing)
    1. If there is interest in getting this functionality into 1.11.0, please help review
      1. VIVO-1630 - Getting issue details... STATUS
        1. Pending response from alessandro galasso
      2. VIVO-1670 - Getting issue details... STATUS
        1. Should be ready to go once we get "member" credentials for final testing
      3. VIVO-1415 - Getting issue details... STATUS
        1. Need to re-verify integrity of commit merges
      4. VIVO-1287 - Getting issue details... STATUS
        1. Need one more VIVO committer to test/merge
    2. These Docker-related tickets should be closeable by the next person who can verify spinning up the MariaDB / Solr / VIVO environment
      1. VIVO-1679 - Getting issue details... STATUS
      2. VIVO-1680 - Getting issue details... STATUS
      3. VIVO-1682 - Getting issue details... STATUS
      4. For the above, username/password
    3. Code-freeze: Friday, Aug 9th
      1. Release candidate to be published: Monday, Aug 12th
  3. VIVO Cross-linking
  4. RDF-Delta-TDB (the diff)
  5.  In-review tickets
    1.  Click here to expand...

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh

Tickets

  1. Status of In-Review tickets

     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

  2. Received

     Click here to expand...
     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

    1. VIVO-1666 - Getting issue details... STATUS

      1. (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design

    2. VIVO-1665 - Getting issue details... STATUS
      1. Should be low-hanging
    3. VIVO-1663 - Getting issue details... STATUS

      1. Where does this stand? What is needed to add more person identifiers to VIVO?

    4. VIVO-1644 - Getting issue details... STATUS
      1. Mike Conlon : thoughts on where this stands?
  3. Bugs (1.11)

     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

Notes 

Draft notes in Google-Doc  


Not observations to the agenda for today.

  1. Not community updates for today.
  2. VIVO 1.11.O release

2a. i. It’s in progress.

  1. ORCID (1670) Step 2 “member” credential. It’s going to be a screencast. ADAGGIO will also check VIVO 1670 to test the integration with sandbox credentials. 
  2. PubMed and CrossRef (VIVO 1415).  Ralph will test it to confirm it behaves as ORCID works.

Don mentions the functionality could be activated by the provider instead of VIVO leading the connection.

Iii. 1287 will be done today.

2b. Docker tickets

Huda mentioned it's still in process. It could be a port issue connecting with local instead of the docker one.

Don asked if the images must be burned. The answer is that it has to be done.

ADAGGIO will take a look of Docker at Slack channel, specifically images usage and storage.

2c. Ralph brings up the Ontology update. There are some changes added to the ticket. 

Don will do the changes, push and test them. It will be done today. It refers to Honors and Awards sub-class. It doesn ́t relate to EVENTS.

Release candidate will be published on Monday or Tuesday. Ralph will let the community know.

  1. Huda shared cross-linking information. It worked before for Cornell instance and the project done before. It should be working now. It could be a better mechanism than the one described there. Huda will include documentation to link to SolrDB.

ADAGGIO is still pending to bring testing “linking process” results.

  1. RDF-Delta 

Huda includes 2 parts of the code with Json and then some queries..

William mentioned his testing results and he finds it ́s important to synchronize the index online. He is looking forward to include the integration achieved at the VIVO vitro. TDB is faster than SDB which has a lot of wrap arounds.

Andrew summired the result is kind of a red flag for the University. 

William invites attendees to test it out to find a better way.

Actions

  •  

Previous Actions

  •  


  • No labels