Page History

...

• 2018-01-10-vivo-fly-in-planning.mp3

Questions / Observations for Straw-chitectures

vivo_arch_v1.png

1. VIVO is separate from read-only sites
2. Triplestore is central to VIVO
3. Difference between Source Systems and staging/loaders?
4. External Solr gets loaded by a loader?

vivo_arch_v3.png

1. Scalable ingest
2. No focus on refactoring VIVO
3. How are loaders triggered?
4. How are updates managed, from the UI?

VIVO Product Evolution Straw

1. Similar to above
2. No focus on refactoring VIVO

Screen Shot 2018-12-20

1. Focus on VIVO refactoring
2. How is performance and scale addressed?
3. Is the frontend decoupled from the APIs?
   • Server-side or client-side frontends?

Future VIVO Example

1. Focus on VIVO refactoring
2. Maybe config does not need to be in a triplestore

VIVO 2.0 Arch

1. Focus on VIVO refactoring
2. Similar to above

arhitectura-vivo

1. Addresses updates from UI and other sources
2. Can service layer become the core VIVO app w/ content sources externalized?

VIVO arch brainstorming-2

1. No focus on refactoring VIVO
2. Similar to Duke?
3. Loader model
4. What is the interation between webapps and content stores? API?
5. What does deployment look like?
6. Where does the VIVO ontology come into the picture?

ACTIONS

Collection of existing architecture diagrams / resources

...