...
- Architectural fly-in (Andrew, 10 minutes)
- Changes to VIVO interest groups (Julia, 5 minutes)
- Potential collaboration with Wikidata (Violeta, 5 minutes)
- VIVO in wikipedia: https://en.wikipedia.org/wiki/VIVO_(software) Volunteers to add information? (Julia, 5 minutes)
- MOU update (Julia/Mike, 5 minutes)
- Cornell news (Mike, 10 minutes)
- Other topics/questions/updates? (all)
...
- Other topics/questions/updates? (all)
Notes
1. Architectural fly-in (Andrew, 10 minutes)
AW: Achitectural fly-in meeting to be scheduled soon: https://wiki.duraspace.org/display/VIVO/2019+Architectural+Fly-in.
The team of participants has not been formalized yet. Some logistical planning has begun, no firm dates yet, and it looks like University of Florida Orlando will be the host in January [https://lakenona.ufhealth.org/]. Andrew has contacted people and some provided firm confirmations: Justin Littmann (Stanford), Jim Blake (Cornell), Richard (Duke), Benjamin Gross (Clarivate), and Alex Viggio (Colorado Boulder) will attend. There are few more people that need to confirm attendance. Andrew, Mike, and Violeta recommend Brian Lowe as an attendant. Questions around funding are raised. The idea is to have strong representation from all areas of VIVO.
Once we have firm dates and confirmed team the deliverable need to be stated.
SG thoughts:
JT: great idea to set some deliverables and that this team needs to set the deliverables.
AW: we would have a documented plan and design for re-architecting and de-coupling. Having a concrete design and plan is beneficial.
MC: recommends to focus on design and architecture.
DJ: agrees with what is already said.
Anna: sounds good.
AV: what he is seeing makes sense and the question for AW is if the identified team will need to sync up before the January meeting? Yes, they will meet virtually, email, slack.
VI: the meeting deliverables need to be in alignment with the VIVO statement on direction.
2. Changes to VIVO interest groups (Julia, 5 minutes)
Interest Groups: JT says that for the past years VIVO has had Interest Groups open calls with a leader and often with no agenda. Anyone can call in, raise questions, talk about their local implementations, etc. Those groups are:
Community and Engagement Group
Apps and Tools,
Implementation
Development
Some IGs have had no activity in a long time, with the exception of development. SG recommends to sunset the IG unless someone from the SG or the community wants to jump in and lead these groups.
The Ontology Task Force will become IG because the group is acting much like the VIVO Development group. VIVO Ontology IG will be lead by Mike Conlon, current lead on the Task Force. Calls are open to everyone and if people decide to join in they will find people at work.
Action item: Send a message to the VIVO community to let them know that we are sun setting some groups and ask the community members if someone is willing to take over and lead any of those IGs. If there is a volunteer the IG will continue to exist.
3. Potential collaboration with Wikidata (Violeta, 5 minutes)
Wikidata: VI will put Daniel Mietchen in touch with AW to schedule the talk during the VIVO Development call. Goal is to explore ways to collaborate and work together.
Scholia https://tools.wmflabs.org/scholia/
https://github.com/fnielsen/scholia
4. VIVO in wikipedia: https://en.wikipedia.org/wiki/VIVO_(software) Volunteers to add information? (Julia, 5 minutes)
Wikipedia page, who will edit the page that already exist? Alex can help if needed. JT has a contact that can work possibly with Alex. There might be other pages that we can edit, including research networking page that listed VIVO. JT will contact her acquaintance and write the document offline and then work on posting it to wikipedia.
5. MOU update (Julia/Mike, 5 minutes)
MOU is being worked on, including what the budget will look like for 2019 in respect to how DuraSpace will support VIVO. The budget needs to be itemized for clarity.