...
Agenda
- Slack questions
- Non-volatile triple stores and Docker?
- Things to update/clarify in Documentation
- Let's get RC1 shipped:
- Blocker issues
Jira server LYRASIS JIRA jqlQuery project = VIVO AND fixVersion = v1.12 AND priority = Blocker AND (status = Open OR status = "In Review" OR status = "In Progress" ) serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
- Blocker issues
- Defining a "VIVO in a Box" project
- Latest description / draft diagram:
View file name VIVOInABoxProjectOutline1.pptx height 250 - Discussion / questions / refining the idea:
- Feedback to provide to Leadership group later in April?
- Keeping it simple for both users and developers
- Technical aspects:
- Integrating Scholars Discovery
- Simplifying editing forms?
- Scalability of triple store
- Multi-source ingest
- Overlap with other interests/initiatives
- Resources and time frame
- Latest description / draft diagram:
- Other topics?
...
Status of In-Review tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Notes
- Docker and VIVO
- Requires vivo-home be in a persistent volume
- Likely need more documentation how to use Docker or docker-compose
- VIVO/docker-compose.yml at main · vivo-project/VIVO (github.com)
- vivo-project/VIVO: VIVO is an extensible semantic web application for research discovery and showcasing scholarly work (github.com)
- How to make it easier?
- Improve documentation
- Standardize on one docker approach to avoid confusion after release
- How to get release out the door?
- Blocker issues
- in review - single review required *ready to merge
- [VIVO-1976] Memory leak in RDFServiceGraph.createRDFServiceModel() - LYRASIS JIRA
- in review - merged
- [VIVO-1973] Site admin users cannot edit pages - LYRASIS JIRA
- in review - merged
- in review - Benjamin Gross self requested review
- in review - single review required *ready to merge
- [VIVO-1820] i18n: unable to add 'governing authority'from Contacts tab - LYRASIS JIRA in review - Georgy will test
- Documentation available when RC1 released
- VIVO in a Box
- Data Ingest - ReCiter harvester
- Require external data
- Pubmed
- Web of Science
- Scopus
- Proquest (CDI)
- EBSCO (EDS)
- Issues with ReCiter
- Primary and foundation bein Pubmed with additional overlay sources of Scopus
- No harvester for Web of Science, Proquest, EBSCO, ORCID, etc.
- Problem Space
- Real-time streaming ingest using Kafka
- Name disambiguation
- Affording various/agnostic data sources
- Institution Data - LDAP, Active Directory
- Profile Editor
- Faculty input
- TDB scalability
- Discovery
- Integrate scholars-discovery core into VIVO core
- Scholars-discovery next release
- Question
- Is it goal to move RDF to relational database?
- Yes/No
- How to produce a better architectural diagram?
- Is VIVO in a Box an appropriate name?
- It is more than just VIVO?
- Is it moving VIVO away from the semantic web?
- Issues
- Relational data to triplestore
- Visualizing/Viewing/Navigating graph
- Understanding/Customizing ontology
- Alternative uses of VIVO to increase adoption
...