Versions Compared

Old Version 3

changes.mady.by.user Mike Conlon

Saved on

compared with

New Version 4

changes.mady.by.user Mike Conlon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. I18n updates.  UQAM working on i18n.  Suggestion that VIVO Scholars use the language files that VIVO currently uses.  All the data should have language tags.
  2. Release 1.11 is ready to come out
  3. Acceptance tests run for 1.10 and 1.11.  From run to run different results are obtained.  Selenium results may be about timing. Tests are not ready to be relied on.  Need work.
  4. Andrew will work on documentation for standing up Solr.
  5. Benjamin may work on custom fields documentation for 1.11.  He has worked through the details.
  6. Sprint has started. See  https://wiki.duraspace.org/display/VIVO/2019-10+Sprint for objectives.
    1. Scholar needs some kind of neutral look
    2. Scholar should be able to customize scholar without complex development
    3. Support for external triple stores
    4. Support for externalizing triple pattern fragments
    5. Messaging service to be added to Vitro
    6. NEMO -- Responsive freemarker templates
  7. ORCiD
    1. Sheila Raybun, a LYRASIS person, ORCiD US Consortium representative, has interest in VIVO/ORCiD integration.
    2. Kristina -- interested in saving the access token acquired through the integration.  This would allow the update of the ORCiD record with data from VIVO, and pull down data from ORCiD.  Access tokens have scopes. Authentication, update personal details, updating work. Kristina has code that requests the work update access token.
    3. Maria Amalia -- Anna, ORCiD Mexico, is interested in helping.  ORCiD interested in integration of additional fields -- professional background, educational background.
    4. Mike -- does the planned integration require an institutional member key?  Yes, it does.  
    5. What could be done in this sprint?  Store the keys.
    6. The public API key is a subset of the member key.  May or may not be sufficient for applications.
    7. OpenVIVO pulls publications from ORCiD using the open API.
  8. TDB/SDB
    1. Brian, Graham, William, Andy Seaborne from Jena required.
    2. Create a pros and cons
    3. Some likely outcomes for each option
  9. Perhaps Brown’s editing work as a special topic for developers

Actions

  •   Organize a TDB/SDB special topics conversation
  •  Organize a session on Brown's work on editing

...