...
- Questions/Issues/Pull requests/Announcements
- CRIS conference with VIVO track
- call for proposals extended - March 13th, 2022
- CRIS conference with VIVO track
- DSpace-VIVO integration
- The project has been started
- The February sprint - Sprint - Dynamic API based on an ontology
Notes
- Questions / announcements
DI: CRIS conference with VIVO track - call for proposals extended - March 13th, 2022.
- DSpace-VIVO integration
DI: The project has been started, MH and JO will regularly inform us at future weekend calls. MH: Working on modeling data structure which should be between DSpace and VIVO. GL: Is this moved to be a more data ingest task? DI: One of the tasks is migration of data from operable DSpace to a new instance of VIVO for institutions willing to test VIVO. The other task in the first phase of the project is unidirectional communication from VIVO to DSpace, i.e. depositing pdf files from VIVO UI to the configured DSpace repository. Stronger integration of DSpace and VIVO might be the topic of the second phase of the project.
- February Sprint / Dynamic API
DI reported to non-sprint participants the sprint progress. WW started with implementation of YAML generator based on RDF description of an action. DI has a problem to test processing of data through the action execution. WW will help in writing RESTEndpointIntegrationTest which accepts JSON at the input and produces JSON as a result. DI tested it manually via Postman, but we need integration tests. Producing response is not yet completed, the structure of the response JSON is hard-coded, not based on definition of ProvidedParameters by an action. GL will continue working on computation of parameters scopes, VM will continue working on the implementation of N3Template, in this phase N3Template operation will support only creation of triplets. BK is looking for how to detect any change in action-linked entities (step, operation, etc.). BL: it is possible by using SPARQL queries, but not so easy and effective at the moment. One suggestion might be to search for any change in entities with the dynapi prefix and reload all actions. GL suggested reloading actions and resources in pools if min/maxAPIversion data property is changed. KD suggested replacing of long prefix with short abbreviation defined by using !ENTITY XML declaration (similarly as https://github.com/vivo-project/Vitro/blob/8f81707e71ba6732daeaa79ef4c0a57e74148e7f/home/src/main/resources/rdf/tbox/filegraph/vitro-0.7.owl#L3). BL suggested not to use xml format for the ontology at all, it is not so human readable. MH suggested using triple or n3 notation. It might be easily transformed in that format, but we will wait until the end of the sprint to do that to prevent some possible conflicts for ongoing work.
...