...
- Review agenda (Julia, 5 minutes)
- Congrats to Erin! (Julia, 5 minutes)
- Erin - moving forward, VIVO MOU development, budget development
- how to increase investment, innovation, propel projects forward
- Cornell news (Javed, 5 minutes)
- ScholarWorks going away December 31
- Turning down VIVO instance
- we plan to remain engaged with VIVO community
- What will happen to the data? we plan to archive all the data
- discussions related to decision
- Development sprint in December (Julia/round table discussion, 20 minutes)
- Short sprint - December 3rd thru 7th
- opportunity for developers to meet, orientation
- ideas, suggestions are welcome
- Alex - integrate Elastic Search into VIVO, mitigate Cornell impact
- Terrie - continue to work on functionality that matters to all, easier to install, improved user interface
- Julia - product evolution tasks
- Hanna - 1-2 persons will participate, basic understanding of developer community, plus one for Elastic Search
- Ginny - modernize interface, responsive themes, cross-site searching, Elastic Search
- John - make interface friendlier, more accessible, customize sub-branding at unit level - Engineering, Medical, etc.
- Mark - improve interface, accessibility
- DJ - supports what has been said
- Javed - we define what to work on, list of people who will be working on it
- Violeta - supports what has been said, ontology work
- Christian - ontology tasks that could be relevant from ontology group, multi-language support, modeling of identifiers, elastic search is high priority, sprint open to new developers with specific tasks, such as visualizations
- Doug - supports what has been said, add 1 developer to sprint, plan to do more work in spring, faculty profiles
- Anna - improving interface, easier installation
- Federico - excited about sprint, will contribute developers
- Tom - no specific objectives, general code base
- Rob - nothing to add
- Ann - elastic search, staff members can help with that
- Paul - product evolution, rough draft of data model, populate, integrate with GraphQL
- Introduction to RIALTO (Tom, 15 minutes)
- Link to Slides: https://docs.google.com/presentation/d/1SY4ArfNmIzYOjIKbyg9-euhU0XqohLO_b2iu3mRWl3o/edit#slide=id.g47bf1470e8_0_71
- RIALTO - Research Intelligence System
- What is our research output?
- Data Sources - Stanford organizations, researchers, funded projects, publications - Stanford API, Web of Science API
- Database - Neptune (Amazon acquired and re-branded BlazeGraph), cloud-native environment in Amazon AWS
- Short Demo
- Top Use Cases - Office of Int'l Affairs, trends in areas of research, impact of cross-disciplinary institutions, assess ROI, which publications resulted from which grants, other use cases captured
- Q. Where does data come from - profile data from existing Stanford Profile System - running for about a decade, not global, publications from Web of Science
- Q. enlist users to help improve quality of data - yes, need to capture and relate faculty members into system, such as high-perf computing faculty
- Steering Group offline work for November (Julia, 10 minutes)
...