Date

Call-in Information

Time: 12:00 pm, Eastern Time (New York, GMT-04:00)

To join the online meeting:

  • https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09

    Meeting ID: 843 7861 5572
    Passcode: 556561
    One tap mobile
    +16699006833,,84378615572#,,,,*556561# US (San Jose)
    +19292056099,,84378615572#,,,,*556561# US (New York)

    Dial by your location
            +1 669 900 6833 US (San Jose)
            +1 929 205 6099 US (New York)
            +1 253 215 8782 US (Tacoma)
            +1 301 715 8592 US (Washington DC)
            +1 312 626 6799 US (Chicago)
            +1 346 248 7799 US (Houston)
            877 853 5257 US Toll-free
            888 475 4499 US Toll-free
    Meeting ID: 843 7861 5572
    Passcode: 556561
    Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4

Slack

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic 
  2. Brian Lowe    
  3. Michel Héon 
  4. William Welling 
  5. Georgy Litvinov (star) 

Agenda

    • When
      • 20.02.23 - 10.03.2023
    • The topic
      • semantic web - https://github.com/orgs/vivo-project/projects/5/views/1
        • Jena upgrade
          • get rid of SDB code (Jena 4 is not supporting SDB)
          • fix live backup of TDB
        • External triple store performance improvement
          • analysis, not implementation
            • find bottle neck and identify how it should be improved
        • Implement a new owl-reasoner (maybe https://github.com/stardog-union/pellet)
          • analysis, not implementation
      • Deployment/installer - https://github.com/orgs/vivo-project/projects/6/views/1
        • VIVO-Installer review depending on the target user: developer, infra architect, corporate/institutional evaluator, etc.
        • decoupling building and deployment
        • deployment for testing by including sample data
        • deployment for production
          • specification of tdb backup parameters ???
      • (New proposal  2023-02-14 - Michel Héon) Addition of a new expertise vocabulary
        • To apply for a grant, Canadian researchers must classify the area of their research according to the Canadian federal government's standard taxonomy called Canadian Research and Development Classification (CRDC) 2020 Version 1.0. For this sprint we would like to port the code already developed internally to the vivo core
        • work already done https://github.com/michel-heon/CCRD-CRDC
        • Deliverables for this proposal
          • The RDF/S representation of the CRDC vocabulary in English and French
          • The Java code allowing the use of the CRDC by VIVO
          • Review the documentation that appeared to be incomplete (Configuring External Vocabularies)
          • Explore the possibility of introducing a vivo:Expertise class instead of using a skos:Concept to describe an expertise 

Notes

Dragan: I got access to VIVO website and updated pages about Vitro, VIVO and contact page. I suggest to change link to wiki documentation. I changed recipient address of the form. It is working! If you find some information is inaccurate, please inform me.
Dragan: Second point is about question from Slack: SPARQL Update get error if triple contains & symbol.
Brian: That makes no sense. Normally you put content in POST body, maybe parameter wasn’t escaped. As long you doing request properly, there shouldn’t be any problem.
Dragan: There was an extension to send data inside POST body by Benjamin Gross. I can respond to this question in Slack. I suppose escaping ampersand in URL parameters is also possible.
Dragan: About VIVO release preparation I merged i18-redesign into Vitro and VIVO. I have 2 points for discussion:
PR from Michel and subsequent VIVO PR from William with cleanups.
Another question is for Vitro PR Vitro-365. Why is that important?
Michel, why you decided to change that?
Michel: I changed it to make sure we have the same code.
William: Filter changes are good, but removing context property changed to function in which hardcoded language en-US was passed.
Dragan: Maybe we changing something that is not affected. If we don’t have a scenario to test then, let's not do that. Let’s merge that for the VIVO, but leave another one.
Michel: If it is not important we can remove fake class.
Brian: it has references from short view service. It is unclear if it is in use.
William: it appears to be used in other classes.
Dragan: I am not sure how to investigate that. If we merge only VIVO fixes, will issue of working with Neptune be resolved?
Michel: I don’t think it is an important class for Neptune.
Dragan: It looks the same to me.
Brian: it is something that needs to be changed at some point. We have fake app ontology, which provides data getters for browsing. There is extra hardcoded data getters in FakeApplicationOntologyService.
Dragan: Do you remember why you have decided to change it?
Michel: The problem is when you are at level of this class you need to know at which language context you need to be to make sparql query.
With i18n we need lang tag to do the query. This is the way that I found to retrieve language tag to put language tag into query.
Dragan: Can we use langCtx to use langMatches?
William: previously it was just a sparql template to substitute language context. If we use hardcoded string, then i18n wouldn’t work.
William I can push changes to fix that.
Dragan: William, please try to fix it.
William: I can do that.
Dragan: Thank you very much.

Dragan: Is there any chance you could try that again?
Michel: I am not in it right now, but I can try it with Neptune.

Dragan: If it works, please confirm it in Github.
It should be the last contribution for this release. After that I will prepare release candidate.
Michel: I am going to do that tomorrow morning.
Dragan: regarding the sprint I created 2 project boards.
1. Semantic web improvements

  1. Improvement of deployment procedure.


William: I am not used to have two sprint boards for one sprint.
Dragan: at the moment we are able to make triple store backups from web interface, but we might reuse it make it scriptable. It is better if we could offer some other way to make backups.
Then we discussed a couple more points. We can at least analyze implementation of pellet reasoner and performance of external triple stores.
It is really necessary to work on installer (decouple building and deployment).


I will try to continue to work on this project boards this week.
William: VIVO-1143 is going to be the main one ticket related to resolving installer issue.
Dragan: The last point here is added by Michel. How could it be important for non-Canadian instances?
Michel: For Canadian it is a must, because all researchers are have to tag their expertise. I as know this taxonomy is referred to international specification. I know that Sweden and France refer to this taxonomy. I implement that in a local VIVO instance and we have all the code for that. It came from CSV format converted to rdf/rdfs format in respect to taxonomy classification. We were able to make VIVO manage it. We can continue to overlay that to integrate that taxonomy inside VIVO because many institutions in Canada are interested in it.
Dragan: is it just RDF or some java code changes?
Michel: java changes are required too.
Dragan: Can we change the data to make it only language specific data. I think hard coding Canadian vocabulary doesn’t look good.
Does it work in a meaning that if you switch to other language you are able to define degrees for other languages.
Michel: last point about proposal. Each term is a skos concept and you can include it, but right now it is a skos concept and we have to create a class that specify vivo:Expertise. Conceptual it is a mistake to identify concept as skos concept. If you say knowledge management is a skos concept, but idea is a skos schema.
Dragan: May it is a configuration of four vocabularies, but this is an external vocabulary.
William: it is a wrong way to do it. We should generalize that.
Brian: If you use other ones external services allow you to import some items, not import the whole vocabularies. It looks like proposal of importing Canadian is different, but it is seems that it is fundamentally different.
Dragan: it might be interesting to discuss it.


Draft notes in Google Docs

Task List

Previous Tasks 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.