Date

26 Jun 2018

Call-in Information

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

To join the online meeting:

• Go to: https://duraspace.zoom.us/j/823948749
• Or iPhone one-tap :
  • US: +14086380968,,823948749#  or +16468769923,,823948749#
• Or Telephone:
  • Dial(for higher quality, dial a number based on your current location):
  • US: +1 408 638 0968  or +1 646 876 9923  or +1 669 900 6833
  • Meeting ID: 823 948 749
• International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5

Slack

• https://vivo-project.slack.com
  • Self-register at:  https://goo.gl/forms/JxQFkut4TYj4Ehww1 
    

Development Process

• See https://github.com/vivo-project/VIVO/wiki/Development-Processes

Attendees

 Indicating note-taker

1. Ralph O'Flinn
2. Tim Worrall  
3. Don Elsborg 
4. Andrew Woods 
5. Huda Khan
6. Kitio Fofack  
7. Alex Viggio
8. Benjamin Gross
9. Mike Conlon
10. Brian Lowe
11. Muhammad Javed
12. Christian Hauschke
13. Qazi Asim Ijaz Ahmad

Agenda

1. 1.10 Release Testing updates
2. Mailing list activity
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  (pr-74)
   2. Internationalization (Russian, German, French)
   3. Open Social Gadgets (JIRA ticket needed?)
   4. Error on root login
   5. New JIRA: Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   6. Does Vivo sparql update API support delete/insert operation
   7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
3. Working towards a unified VIVO technical vision
   
   1. Salient use cases
      • Standard, full-app with focus on profiles
      • Headless component of research intelligence ecosystem
      • Minimal store in support of modern, custom UIs
   2. Multi-source ingest: OpenHarvester, Combine, Reciter, etc
4. Suggested updates from Michael J. Giarlo
   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.
5. From last week
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

Draft notes in Google-Doc

1.10 Release Testing updates

1. Thanks to all people who tested so far and joined the testathon
2. This friday is the last day for testing. Everyone interested in giving a hand is warmly welcome
3. Sanity builds are OK
4. UI testing :
   1. Publication sparkline info button does not work. If you click on it it does not work. 
      1. What do we want to do with that false button?
      2. Brian : it’s suppose to be a hover instead of a button
      3. Christian: Works as before, as a hover/tooltip
      4. Mike: On Mac, too.
      5. Benjamin reports that it does not work for him.
   2. MapOfScience 
      1. Ralph : it works.
      2. Michael : Could not test it because of missing a Google Key 
      3. Is there any documentation on how to make the feature work ? Yes, 
      4. Benjamin & Ralph reports the feature works as supposed
      5. Need to switch from Google maps to OpenStreetMaps
      6. Ralph volunteers for investigating on OpenStreetMaps for VIVO
      7. Michael : Will create the JIRA ticket and assign it to Ralph
      8. Christian appreciates very much that initiative
   3. Orcid
      1. Benjamin : You need to have Orcid api account in order to be able to test the feature completely
      2. You just need an orcid account to populate data in VIVO from Orcid
      3. What should we do with this dependency that means paying 
      4. Christian will create a JIRA to decouple Orcid paying API from the free one in the application - https://jira.duraspace.org/browse/VIVO-1530
   4. Roles
      1. Huda not sure about how the feature should work
      2. Michael discovered the feature as he was testing
   5. SPARQL 
      1. Benjamin had an issue related to the javascript in the SPARQL editor
      2. Mike faced another issue that looks related to that same javascript 
      3. Benjamin: maybe a new version of that javascript library would solve the issue
5. Overall on the UI it would be good if someone other people different from Mike could test also the feature.
6. Upgrade Testing
   1. Ralph is the only one who tested so far.
   2. Ralph would like to have tests with other datasets different from sample data
7. Vagrant Tests
   1. Andrew : Since the VM is configured in TDB it can’t be considered for validating the standard VIVO which is in SDB.
8. We need more testing on almost all parts of the test plan 
9. Mike: One test that pops out of his mind as missing in the test plan is the data load with the harvester
   1. Is there anyone using the harvester 
   2. Christian will ask to Graham if he can assist with Harvester testing
   3. Kitio volunteers on upgrade testing using one large dataset available on sample data repository

Mailing list activity

1. VIVO-1527 - Providing DOI as URL Open (pr-74)
   1. Issue raised by Stefan from Germany
   2. There is a PR that will replace deprecated URL formats with https:// and append it if only the DOI is entered for the link
   3. Benjamin and Stefan disagree on what should be shown to the user. Benjamin says what has been entered by the user should be what he sees. Stefan suggests only displaying the DOI #, regardless of what prefix is in the database. Christian as librarian suggest to store and display the DOI the way that crossref does it ! 
   4. Andrew separates two issues:
      1. One related to user interface 
      2. One related to data stored
   5. We agree on following crossref recommendations on how to display a DOI
   6. All participants are welcome to take actions
2. Internationalization (Russian, German, French)
   1. Mike suggest to hire translators
   2. Christian propose to bring the translations issues to local VIVO Communities(German, Canadian …) and keep only the technical integration with the VIVO community.

Previous Actions

• Don Elsborg to document "firsttime" resolution in CU BOulder wiki, circulate this doc to email list and discuss as a team how to integrate this in VIVO documentation

Actions

• ...