...
- Don Elsborg
- Ralph O'Flinn
- Andrew Woods
- Mike Conlon
- Jim BlakeBenjamin Gross
- Steven McCauley
- Alex Viggio
- Jim Blake
Agenda
Two In-Review tickets that need a push forward:
- Benjamin Gross ?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1641 - Cineca's BlazeGraph integration depends on this
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1661 - Latest and greatest from TIB translations
- Acceptance tests moved to vivo-community, thanks Jim Blake
- https://github.com/vivo-community/vivo-acceptance-tests
- How to run it?
Search index: approaches for configuration and processes
When Androids Dream (codename: androdies) - Huda Khan (PPT version) ( Relegated to next week but feel free to review/give feedback on slides)
Mailing list messages
- Some triples not getting deleted in VIVO?
- How can I backup the custom Pages that have been created?ORCID login on vivoweb.org return with error
- ORCiD Integration - Sync - Muhammad Javed suggesting Jim Blake has clues
Issues with VIVO 1.9.3 and activating the ORCID integration - (do we have contact with Metcalfe House, Delhi?) - input data Vivo last version
- Some triples not getting deleted in VIVO?
- Next Week: When Androids Dream (codename: androdies) - Huda Khan (PPT version) ( Relegated to next week but feel free to review/give feedback on slides)
Status of In-Review tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Soft balls
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1659 - Low-hanging, documentation - Mike Conlon, can you give this one a review?
- Regular balls
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1675 - New
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1670 Kitio Fofack ? Orcid and i18n
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1656 - Is this feature of broader interest?
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1643 - Andrew Woods to look into
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1642 - Mostly trivial, with conversation around Tomcat version support
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1641 - Relatively straight-forward bug fix
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1661 - An important step for i18n... resolves many other open issues
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1630 - Kitio Fofack to review?
Received
Expand Expand Jira server DuraSpace JIRA jqlQuery filter=14802 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1666 (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1665 - Should be low-hanging
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1663 Where does this stand? What is needed to add more person identifiers to VIVO?
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1644 - Mike Conlon : thoughts on where this stands?
Bugs (1.11)
Expand Jira server DuraSpace JIRA jqlQuery filter=14702 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
Among those present, Benjamin and Jim are limited participants.
Ralph is starting work with search tasks
Andrew starting work with Docker tasks
Mike: Thoughts on documentation for new installation process?
Ralph: The new process is much more straightforward. Mike: A button would be good. Ralph: Not quite.
This is for 1.11 correct? Yes.
Thoughts on when 1.11 may be released? By conference?
Andrew: Rumblings in community that we may have enough content to make a release now. 1.10.1 or 1.11 up for discussion. The dockerization and search updates would definitely be for 1.11.
Mike: If integration testing could be done for the next version, that’s a huge step forward
Ralph: Could use just a little time for the community to play with it more, test it. Especially with big changes like Docker.
Mike: Maybe a release candidate for conference? Or soon, so it’s ready/released for conference? Would like to have the tools to run tests.
Andrew: If we achieve goals of merging search branch and complete dockerization (VIVO, Solr, MariaDB containers) we should have a release candidate.
Don: Looking at doing Maven build via Docker, begin with normal 2 stage (VIVO + Vitro) build.
What are expectations for skills needed to build and deploy for sysadmin vs dev ops? Don: Most people seem to be a combo, should be fine with using Docker and git.
Andrew: You can point Docker toward your modified runtime.properties which gets us toward a single command spin up
Andrew: Ralph, you need any support? Ralph: Nope!
Tickets that need addressed: https://wiki.duraspace.org/display/VIVO/Design+-+External+Search
Two In-Review tickets that need a push forward:
VIVO-1641 - Replace afn:localname / afn:namespace with cross-platform equivalent IN REVIEW - Benjamin Gross ?
Cineca's BlazeGraph integration depends on this
Benjamin and Ralph to review https://github.com/vivo-project/VIVO/pull/96
VIVO-1661 - Merging VIVO-DE community translations into code base IN REVIEW
Latest and greatest from TIB translations
Andrew: this is a classic at this point. Pushes us way forward on i18n support. Kitio left his position for another position at a company :*(
Benjamin: Any tips on how to test this?
Observation: the only files touched that affect anything but the german language is the pom.xml files.
Benjamin: Will check for missing all.properties strings that have been added in english since the time of this pull request
Acceptance tests moved to vivo-community, thanks Jim Blake
How to run it?
Jim: Doing some additional work to make it more useful for the next person that gives it a shot
Jim: I’ve made considerable progress
Search index: approaches for configuration and processes
Huda added this…? Calling out Jim. Jim: Can we use existing code to populate multiple search indexes? Internal + external. Brian Lowe called it hacky, but at least Jim could finish it. Huda said it was silly that application setup code is sitting in the display graph (search indexer configuration). Jim to talk to Huda more about it.
Mailing list messages
ORCiD Integration - Sync - Muhammad Javed suggesting Jim Blake has clues
- Is this a very old version of VIVO? Hard to help until we know.
Next Week: When Androids Dream (codename: androdies) - Huda Khan (PPT version) ( Relegated to next week but feel free to review/give feedback on slides)
Status of In-Review tickets
Benjamin: to answer the question posed for VIVO-1656, yes it is of broader interest because it is a prereq for https://jira.duraspace.org/browse/VIVO-1415
Actions
-
- Brian Loweis reviewingJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1667 -
- Mike Conlon, can you give this one a review?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1659
- Benjamin Gross to reviewJira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1661
- Benjamin Gross to re-reviewJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1641