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. Huda Khan 
  3. Rachid Belkouch
  4. William Welling 
  5. Andrew Woods
  6. Alexander (Sacha) Jerabek 
  7. Brian Lowe (star)
  8. Ralph O'Flinn
  9. Michel Héon

Agenda

  1. Announcements
    1. Andrew Woods on holiday next week
  2. VIVO Roadmapping
    1. Product Direction for 2020
    2. Driving priorities
      1. Lowering barriers to adoption and contribution
      2. Modernizing architecture and administration
      3. Improving front-end user experience
    3. Focal areas
      1. i18n
      2. Ingest
      3. Improved frontend
      4. APIs (JSON data)
      5. Messaging
      6. Installation
      7. Upgrades
      8. Documentation
      9. Modularity
      10. Publication claiming
      11. Advanced role management
  3. Next i18n sprint - Aug 24 - 28
    1. Necessary pre-sprint work?
  4. Data ingest task force
    1. Slack: #dataingest
    2. Wiki landing page?
  5. VIVO Scholars - next steps
    1. Indexing into core Solr index... with Scholar entities
    2. Tying into existing core indexing pattern
    3. Will allow for layering Scholar's REST-API, GraphQL endpoint, and UI over core Solr index

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. Renaming of 'master' branch? (ZDNet, BBC)
    1. Guidance from GitHub 
    2. DSpace has done it
    3. Fedora has done it
    4. Samvera is doing it
  3. 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 

Attendees

  • Andrew Woods
  • Brian Lowe
  • Rachid Belkouch
  • Michel Heon
  • Ralph O’Flinn
  • Benjamin Gross
  • Alexander (Sacha) Jerabek
  • William Welling
  • Huda Khan


Notes

  • Andrew is on holiday next week (11 August meeting)
    • will create page with blank agenda; we’ll take it from there.
  • Agenda item 2 (VIVO Roadmapping):
    • Andrew: currently thought of as an approach to iii. (improved front end).
    • Ralph: Scholar Discovery and UI are two totally different things; UI is optional.
    • William: UI is probably of less universal interest than the API.
    • Andrew: Scholar is addressing both iii. (front end) and iv. (APIs).
    • Andrew: combing through the documentation and making it better; not complete rewrite.
      • Documentation is a way for non-developers to get involved. Could have documentation sprints to bring in non-developers.
      • Could also be useful to put out call to community about what they find lacking in documentation.
      • Avoid answering repeated questions in mailing list / Slack.
    • Ongoing disconnect between governance and development; little overlap in participation in these two spheres.
    • Attempt under way to reschedule leadership meeting so that it doesn’t conflict with the development call.
    • Estimating effort / providing additional information about items in 2c could help leadership group.
    • Sacha: where does VIVO Scholar fit in?
    • Michel: What’s involved in the documentation item?
  • Next sprint in three weeks: get branch into master. Also overdue for 1.12 release.  Primary feature of release will likely be i18n work.
  • Data ingest task force
    • Notes from Slack are a good starting point for populating the wiki.
    • My goal is to come up with one good way of automating data entry with some sanity checking, using a technology that many people do or can understand, which we can support.
    • Michel: First part of effort should be documentation; compile recipes for how people can ingest from a variety of technologies.
    • Possibility of using simple, tabular database ahead of triplification.
    • Ralph: if people can get their data into our simple table format, we can turn it into triples.
    • William: Are there proposals for more generalized approaches?
      • Ralph: want to make sure that whatever gets produced doesn’t feel heavy and is something that the person starting out can easily use.
    • Andrew: common pattern to normalize data into database tables that reflect VIVO entities. Would be good to compare those tables and get to a “supported” set of database schemas for the staging area.
      • Have supported tooling for these schemas
    • William: another database schema is another barrier to entry.
    • Brian: My priorities for data ingest would be built-in tools to build a VIVO from publicly-available data sources (ORCID, PubMed, CrossRef, etc.) before worrying about simplifying the process of transforming your own institutional data.
    • William: this is a tall order; Symplectic Elements already does a lot of this.
    • Rachid: not everyone can afford Elements.
    • Elements Harvester is open source (the harvester from Elements to VIVO)
    • Ralph: wiki landing page coming in the next day or so.

William’s thoughts on integrating Scholar into existing indexing: https://docs.google.com/document/d/1yZk8MkeygfzWjjr0lUkLRx-i-OOi1mw0c2QQKkjt1g4/edit

Draft notes in Google-Doc 

Actions

  •  



  • No labels

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