...
- Questions/Issues/Pull requests/Announcements
- ElasticSearch and VIVO - https://vivo-project.slack.com/archives/C8SDQQYJ2/p1657313614605709
- Documenting reconcilation API
- Permissions for editing faux property values - https://vivo-project.slack.com/archives/G9DEV4WF6/p1657117526065229
- VIVO dynamic API demo meeting
- Roadmap for development of VIVO
- VIVO 1.13.0 Release candidate 2
- The next sprint
- When?
- 19.09. - 07.10.
- What?
- Improvement of expressiveness of notation
- Iterative steps
- Operation data
- Improvement of UI
- Support for more rich structure of entities
- Notation for UI layouting
- Completion of authorization and authentication
- Extension of SHACL rules
- Editor for definition of a dynamic action
- VIVO based on dynamic actions
- Improvement of expressiveness of notation
- Who?
- When?
- Summer vacation period
- 05, 12, 26 of July, 2022
- 09, 23, 30 of August, 2022
Notes
- Questions/Issues/Pull requests/Announcements
- ElasticSearch and VIVO -https://vivo-project.slack.com/archives/C8SDQQYJ2/p1657313614605709
Dragan: for my best knowledge is using Solr, it should also work with ElasticSearch.
Benjamin Matkin: I am doing some scoping for projects including VIVO. We didn’t invest time to run VIVO with Elastic Search but.
Dragan: You should be able start with Solr, but Elastic search should also work
Benjamin Gross: University of Colorado using Elastic search but feeds it in different way, in newer versions of VIVO Andrew Woods tried ElasticSearch as a concept, but overall nobody uses it in production.
Benjamin Matkin: there was open source facet repo and we interested in that, but we will be happy to use Solr
Benjamin Matkin from the chat: https://github.com/vivo-community/facetedsearch
Benjamin Gross from the chat: Colorado page with facets powered by Elasticsearch:https://experts.colorado.edu/people
- Documenting reconciliation API
- Permissions for editing faux property values -https://vivo-project.slack.com/archives/G9DEV4WF6/p1657117526065229
- The next sprint
Last week a Demo meeting was held. You can check the video, link should be available at the wiki page.
As part of discussions on the meeting. Christian Hauschke proposed to use reconciliation api. We should document it. Also from that meeting Bruce Herbert said it would be nice if we have a roadmap for further development of VIVO. It would be nice if we have a description of the benefits and advantages compared to other RIS.
I think we don’t have that clearly stated in documentation. Bruce expressed his willingness to work on that document and because of that I created a Google document, but it is not ready for serious reviewing.
Release candidate 2 was published and ready for testing. We are lacking in people and it would be great if you could test it.
Dragan: last week's issue was resolved so maybe we should close this PR.
Benjamin Gross: Yes, if the issue is resolved then this PR should be closed.
Dragan: let's keep it for some time until it is all tested.
- When?
- 19.09.22 - 07.10.22
Dragan: The next Sprint should be on 19 of September. Three weeks for the sprint. People who have expertise in semantic web as well as technical people are welcome.
The plan for the third sprint was to fix some small i18 issues and start working on data ingestion.
Dragan: My suggestion is to have another Dynamic API instead of Data ingestion.
Let's discuss what should be the topic for the next sprint.
- What?
- Improvement of expressiveness of notation
- Iterative steps
- Operation data
- Improvement of UI
As most of the development is currently done by William it would be great to have somebody helping him.
- Support for more rich structure of entities
- Notation for UI layouting
Dragan: We have a description of ontology in dynamic action. Should we have classes for layouting of UI.
It is a question for each specific Dynamic action. Part of that could be localization.
- Completion of authorization and authentication
Dragan: We might start with some simple solution, but later we might need some additional checks for permissions
- Extension of SHACL rules
Dragan: There is an engine, but rules are not ready yet. We will need some additional SHACL rules to validate that.
- Editor for definition of a dynamic action
Dragan: If we have to develop in N3 files but it is not easy to edit N3 files. It would be great if we could create a nice editor for that purpose. At the moment we have to define a lot of other lines to do that in N3, which is error prone.
- VIVO based on dynamic actions
Dragan: Would you like to extend this list with some other topics? Last time we had a lot of discussions, we should try to move this part. Dynamic API could be used to replace N3 Generators, but I think it could be used for other purposes. We need some strategy for that.
If you are super satisfied with the list of topics, just click on the form and subscribe for the sprint.
Next week we will miss the meeting.
- Summer vacation period
In the middle of July we will have biweekly calls
- 05, 12, 26 of July, 2022
- 09, 23, 30 of August, 2022
Salm: I am trying to bring VIVO as a solution for search. We have a Brazilian national database. We use VIVO as searching and visualization technology. We maintain legacy systems, but I was wondering if anyone knows about using large datasets. We have 7.5 million researchers (users). Is VIVO capable of working with large data sets. Does anyone know about big data stores, that would be great?
Benjamin Gross: I don’t have any documentation. Brian Lowe should be able to answer this question.
Dragan: We can ask Brian.
Salm: He was developing a project for national search, if he could help that would be great.
Benjamin Gross from the chat: UFL used to be the largest:https://vivo.ufl.edu/
Dragan: I will put it on the agenda for the next meeting.
Salm: Thank you for the link
...