...
- Brian Lowe
- Dragan Ivanovic
- Georgy Litvinov
- Benjamin Kampe
- Andreas Czerniak
- Veljko Maksimovic
- Michel Héon
- Benjamin Gross
...
- Questions/Issues/Pull requests/Announcements Call for Interest: Integrating DSpace with VIVO
- Reviews scheduled. Selection is ongoing.
- CRIS conference with VIVO track
- CERIF 2 VIVO mapping - https://docs.google.com/document/d/1qJgxuIdMBSdL6c_w7BADOPhazjE6UKl8I-EawdwRuqA/edit?usp=sharing
- Formal description is part of abstract. Mostly modeling.
- May be some technical parts
- Others are invited to join, and provide comments.
- May still be an in-person conference but may move to virtual still
- Call for Interest: Integrating DSpace with VIVO
- CRIS conference with VIVO track
- The preparation for the February sprint (Dynamic API)
- Registration
- Date for the sprint
- February 21st - March 11th
- We have made some progress thanks to @Georgy
- Goal, idea and approach - https://docs.google.com/document/d/1vtNIVEYWdBgV11N-wiPk_UNKpiFQ4sKetJ8elJ6xy2E/edit#heading=h.k389x4cotzuw Specification - https://docs.google.com/document/d/1n7gSf_cSDS5mbTI4HwVGj-2sQd5if0177Nrdtri9BtM/edit?usp=sharing
- Ontology - https://webprotege.stanford.edu/#projects/b7ebb822-2a8d-4fd3-ba36-5b9e8bd3f400/edit/Classes
- In this spec we also have a link to the ontology app that will enable us to work on it.
- The use case examples
- https://app.diagrams.net/#G176In5cQ-tWecx0aP0ILBTODuCoiYk-0o
- https://github.com/matthiasluehr/vivo-custom-forms/tree/master/mentoring - thanks for sharing @Matthias` Form for thesis and advisor relationships. Georgy was able to model using his proposed process.
- Changes?
- Conditional - Dragan requests an example where it might be used. E.g. would a form be dependent on the result of the conditional check?
- Should be reusable - checks for parameters, but also checks for current state of Solr etc.
- Dragan - will there be a specific language for the condition? Or a sub-hierarchy of conditional elements that link to a java class?
- Check something with triplestore - create SPARQL
- Check something related to parameters - predefined checks
- For first implementation, it might not include a conditional
- The generators for custom forms are hard to understand
- Walked through diagram:
- Get request to create person or individual via a REST request.
Using name or ID or individual? - Mapping to an http verb to an action (e.g. create a person)
- That mapping/action will be described in RDF
We will load appropriate action based on request verb (plus resource name) + mapping- Then go step by step
- For person example, first is set first and last name
- Validate. If all goes well, go to next step
- If end, respond with results
- Using name or ID or individual?
- We will load appropriate action based on request verb (plus resource name) + mapping
- Then go step by step
- Class for each step?
- Georgy - yes, class for each step, plus class for template
- Search index refresh is not part of this… there will still be listeners
- How about when we need to get individuals? E.g. suggestions for autocomplete
- This is coming out of the search index
- Dynamic API will have a special function to get data the same way.
- Dragan - I believe there are issues with multilanguage search
- Brian - fundamental issue is the search index doesn’t distinguish between languages. So you will get results in multiple languages, but you can’t get them in just one language
- Georgy - could theoretically swap out Solr with SPARQL using dynamic API
- Any additional deficiencies with ontology at the moment?
- owl:Thing > Action, Conditional, Parameter, Role, SPARQLQuery, SolrQuery, Step, Template, Validator
- @Georgy - nothing at the moment
WebProtege - what prefix should we use for dynamic API? - There are some old prefixes for the application but they have mannlib in the URI. We no longer have access to the mannlib web spaces, and limited participation from Cornell.
- Brian- perhaps http://vivoweb.org/ontology/api/ or http://vivoweb.org/ontology/dynamicapi/
- If we want to make it clear it’s a vitro, we could do something like https://vivoweb.org/ontology/vitro-dynamic-api/
- Michel - we should bring the suggested prefixes to the ontology group
- Registration
- Date for the sprint
- We have made some progress thanks to @Georgy
- Goal, idea and approach - https://docs.google.com/document/d/1vtNIVEYWdBgV11N-wiPk_UNKpiFQ4sKetJ8elJ6xy2E/edit#heading=h.k389x4cotzuw
- Specification - https://docs.google.com/document/d/1n7gSf_cSDS5mbTI4HwVGj-2sQd5if0177Nrdtri9BtM/edit?usp=sharing
- Changes?
- The generators for custom forms are hard to understand
- Walked through diagram:
- How about when we need to get individuals? E.g. suggestions for autocomplete
- Any additional deficiencies with ontology at the moment?
- WebProtege - what prefix should we use for dynamic API?
- Dragan - The complexity is mostly in the action pool section
- Georgy - yes, the plans are big!
- Meeting again next Tuesday, same time and place
...