The VIVO architectural fly-in will be focused on bringing an architecturally-minded team together who individually represent distinct VIVO stakeholder constituencies for the purpose of developing architectural approaches required to address the direction of the project. The primary goal of the two-day face-to-face meeting will be to assess and document a plan for improving the VIVO application architecture towards enabling and realizing the technical efforts defined in the "Statement on VIVO's Product Direction for 2019".
The success of this effort relies on balancing the perspectives of:
- Research Intelligence
- Modern web interface
- Semantics and ontology
- Modern development tools and practices
- Performance / Scalability, and
- Existing VIVO architecture
- January 29th - 30th, 2019
Orlando - "Research and Academic Center - Lake Nona"
To be developed
Thoughts / Notes / Resources
Components to decouple
- Search index
- Searching and indexing can be separate components
- Reasoners - ABox and TBox
Interfaces for decoupled components
- What endpoints / services are required by UI?
- Starting point: Classes with @WebServlet annotations
Not all components are easily compartmentalized, like APIs or TripleStores
- Consider Authentication, which includes:
- back-end business logic,
- data model storage,
- UI elements
- If we wanted to support a new authentication scheme (say, two-factor authentication), we would need changes in all of these areas.
- Back-end code can be delivered in a JAR file
- How is front-end code delivered?
- What about mixed components?
- University X develops a new Triplestore component, called newTriple
- University Y wants to use newTriple
- One possibility is to wait for VIVO central to adopt newTriple into the core distribution. Then University Y can upgrade their system to the latest release, to get newTriple
- What are other possibilities?
- This leads back to packaging.