Versions Compared

Old Version 2

changes.mady.by.user Dragan Ivanovic

Saved on

compared with

New Version 3

changes.mady.by.user Benjamin Gross

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Dragan Ivanovic 
  2. Brian Lowe  
  3. Georgy Litvinov 
  4. Michel Héon
  5. Benjamin Gross (star)
  6. Benjamin Kampe
  7. Veljko Maksimovic 
  8. José Ortiz
  9. Andreas Czerniak
  10. Mark Vanin
  11. Nicolas Dickner 
  12. William Welling 
  13. Huda Khan 

Agenda

  1. Questions/Issues/Pull requests/Announcements
    1. Conferences
      1. CRIS 2022 - program
      2. OR 2022 -  program
    2. Self-registration for Slack - http://bit.ly/vivo-slack
      1. fixed
    3. New issues and PRs
      1. Performance issue - https://github.com/vivo-project/VIVO/issues/3695
      2. Exporting data - https://github.com/vivo-project/VIVO/issues/3696
        1. PR - https://github.com/vivo-project/Vitro/pull/291
      3. The license issues - https://github.com/vivo-project/VIVO/issues/3690, https://github.com/vivo-project/VIVO/issues/3692
        1. discussed at VIVO LG
        2. Action - establish communication with Cornel University
      4. Spring dependency - https://github.com/vivo-project/VIVO/issues/3686
        1. PR - https://github.com/vivo-project/VIVO/pull/3697
    4. Slack discussion
      1. A reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
      2. Migration of permissions - https://vivo-project.slack.com/archives/C8RL9L98A/p1651831688329669
  2. DSpace-VIVO integration
    1. DSpace-VIVO integration task force
    2. a 15 minutes presentation
  3. The next sprint
    1. date
      1. May 30th - June 17th
    2. Registration
      1. please register until May 15th, 2022 
      2. link
      3. Two registered participants so far
    3. Infrastructure
      1. Wiki page - Sprint - Dynamic API based on an ontology 2
      2. Slack channel created
      3. Project board
        1. We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
          1. but extend it with new issues (features, bugs)
    4. Topics 
      1. Update the ontology
        1. GET all and GET one - two dynamic actions or one
      2. Implement more complex workflows
        1. iteration step,
        2. conditional step
        3. Implement N3Template deletion and modification
      3. User interface for execution of a dynamic action
      4. User interface for definition of a dynamic action
      5. Validation of dynamic action
      6. Authorization - roles
    5. Selection of the frontend technology/framework
      1. spreadsheet
  4. Publishing of a minor release 
    1. Completion of PR reviews and merging
    2. Preparation of a release candidate
    3. Updating of technical documentation - VIVO 1.13.x Documentation 
      1. Uploading files associated with individuals
      2. Developing a New Interface Language for VIVO
      3. SPARQL Update API
      4. Minimum Configuration
    4. Testing
      1. Standard features test - https://forms.gle/BsAz3ongzU1BR5nE7
      2. Advanced features test - https://forms.gle/BX7o8gwwVfCujWes5
      3. New Features test - https://forms.gle/35hNEjMnfcYC1ZpMA

Notes

  1. Questions/Issues/Pull requests/Announcements

    1. Conferences
      1. CRIS 2022 - program
      2. OR 2022 -  program
    2. Self-registration for Slack - http://bit.ly/vivo-slack
      1. Fixed
      2. Backlog of people have been added
      3. They will be added to dev channel
    3. New issues and PRs
      1. Performance issue - https://github.com/vivo-project/VIVO/issues/3695
        1. Brian: fairly big issue, should be done sooner rather than later if it can be reproduced
        2. Have not had chance to look at it yet
        3. Did not affect admin or root users
        4. Might be related to permissions checks 
      2. Exporting data - https://github.com/vivo-project/VIVO/issues/3696
        1. PR - https://github.com/vivo-project/Vitro/pull/291
        2. Submitted by Christian, resolved by Benjamin G
      3. The license issues - https://github.com/vivo-project/VIVO/issues/3690, https://github.com/vivo-project/VIVO/issues/3692
        1. discussed at VIVO LG
        2. Action - establish communication with Cornell University
        3. Had to find right person
        4. It might be complicated, he’s not sure. Fork code?
      4. Spring dependency - https://github.com/vivo-project/VIVO/issues/3686
        1. PR - https://github.com/vivo-project/VIVO/pull/3697
        2. Brian has submitted the PR to resolve
    4. Slack discussion
      1. A reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
        1. Creating a problem with building URLs
        2. Likely an issue with using a proxy other than AJP (e.g. a normal HTTP proxy)
        3. Would it make more sense to allow a custom URL be defined in runtime.properties?
        4. Setup of modern Tomcat a little more complicated than in the past for security, so maybe less likely that people are using AJP
      2. Migration of permissions - https://vivo-project.slack.com/archives/C8RL9L98A/p1651831688329669
        1. Question references advance role management. Do they store permissions in a different place?
        2. Brian: Since the introduction of faux properties, it’s more complicated 
    5. Overall, we’ve done a good job of cleaning up old pull requests. Still not sure what will we do with the very old, very large PRs, like advanced role management.
  2. DSpace-VIVO integration
    1. DSpace-VIVO integration task force
    2. a 15 minutes presentation from Michel
    3. ETL notes
      1. Using the Dspace-VIVO exchange data schema (DVExDS)
      2. Source database > extract source data > transform target data > load to target database
      3. Data structure in Dspace: REpository > community > collection > Item > (type, e.g. BitStream)
      4. Everything gets a freestyle ID (as a string), not unambiguous unique IDs
    4. Within VIVO, all metadata from Dspace is brought over
    5. Mapped to type via dc:type, plus asserted as a ‘DSpace item’ 
    6. Must consider how to map people in DSpace (who have many non-unique records) to a single unique record in VIVO
    7. Copies keywords from DSpace documents into ‘research areas’ for people in VIVO
    8. Population of VIVO can come from multiple DSPace sources
      1. Example use case: Departments at university have their own DSpace. Can merge into a single VIVO
    9. Capability maps work 
    10. Many people in DSpace -> 1 VIVO
      1. Could add metadata into DSpace that has VIVO URI. Not great because it needs to be done for every record.
      2. Could have x-walk registry. A link between VIVO URI and all possible name variants in Dspace.
      3. Could have governance rule within university that requires names in Dspace be written exactly in the right way
      4. Dragen: Will unfortunately require some manual effort in every approach
    11. Another tough point: classification of DSpace item in VIVO. You can extend the item types in DSpace, so can’t account for random custom types in crosswalk to VIVO automatically.
  3. The next sprint
    1. date
      1. May 30th - June 17th
      2. Pre-sprint meetings the week before 
    2. Registration
      1. please register until May 15th, 2022 
      2. Link (https://forms.gle/whYvMwgpbo7q6DgC9)
      3. Two registered participants so far

Draft notes in Google Docs

...