Date

Call-in Information

Time: 10:00 am, Eastern Daylight Time (New York), 4:00 pm Central European Summer Time

To join the online meeting:

Calendar invitation - ICS file

Slack

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic (star)  
  2. Svetlana Rastegina 
  3. Georgy Litvinov  
  4. Brian Lowe 
  5. Miloš Popović 
  6. Gazi Yucel  
  7. Christian Hauschke
  8. Bridget Almas 
  9. Benjamin Kampe 
  10. Jessica Farrell

Agenda

Notes  

Community Supported Technologies Interoperability Project

Jessica presented on the Community Supported Technologies Interoperability Project, which she has been consulting on since October-November. She outlined two main user stories for Vivo: depositing publications in institutional repositories and receiving updates when linked publications undergo status or metadata changes. Jessica explained that she is developing specifications for these enhancements, with functional requirements to be completed by the end of June, and suggested using the SWORD protocol and COAR notify for repository integration, with DSpace as a potential proof of concept. She invited team members to provide feedback on the evolving documentation through GitHub comments.

The team discussed implementing SWORD API functionality in VIVO, focusing on two main scenarios: depositing publications from VIVO to DSpace and syncing metadata from external repositories. Bridget clarified that the current project scope only covers one-way deposits from VIVO to other repositories, not bi-directional deposits. The discussion highlighted technical considerations around supporting different SWORD protocol versions (SWORD2 and SWORD3), with DSpace currently supporting an older version. Jessica outlined key behavior scenarios including creating objects with binary files, retrieving service documents, and handling authentication, while questions remained about the level of metadata interface to provide users in the VIVO interface.

The team discussed the process for uploading publications to a repository from VIVO. Christian suggested using the existing metadata in VIVO and transferring it via SWORD protocol to the repository, rather than creating a separate metadata upload mechanism. Dragan advocated for modifying metadata directly in VIVO before depositing files to the repository. Brian proposed a streamlined approach where users could confirm and augment existing metadata in one form before submitting, ensuring it updates both the VIVO graph and the repository submission.

The group also explored the possibility of allowing users to select multiple repositories within the VIVO system, though Dragan indicated that a one-to-one repository configuration might be more common initially, with the option to add multi-repository support later if needed.

Christian highlighted the need for researchers to submit to both institutional and discipline-specific repositories. Bridget suggested focusing on the best-case scenario for specifications, including support for multiple SWORD versions and loose coupling for future protocol additions. Jessica outlined the proposed workflow where VIVO sends metadata and files to a SWORD-compliant repository, which then responds with information like ETAG, file URL, and status document. The discussion concluded with questions about what additional actions VIVO should take with this information, including potential background jobs and in-progress deposit options.

The team discussed object deletion, they decided to remove this feature as repositories typically don't allow deletion but only make objects invisible, and the team couldn't identify a clear use case for supporting deletion. For the CORE Notify scenario, the team identified several open questions about the relationship definition between VIVO profiles and linked publications, leading to a decision to focus on defining the SWORD deposit scenario more thoroughly rather than rushing the notification system. 

New issues and other topics

The conversation ended with updates on various pull requests and tickets. There is a question from Tatiana “Is it possible to hide the "Edit this individual" link (next to Admin Panel in the profiles) for specific roles like for e. g. editors ?” Georgy will be in communication with her about this question, it might be that it can be resolved by customization of permissions. There is a lot of outdated information at wiki pages, Christian and Brian will work on that. 

Draft notes in Google Docs

Task List


  • Dragan Ivanovic 
    • Continue work on wiki documentation for VIVO 1.16
      • Review wiki documentation produced by Georgy
    • Check and fix outdated documentation identified by Christian and Folke
      • Review and respond to any wiki page changes made by team members
    • Start intensive reviewing of Milos's accessibility guideline pull requests after VIVO 1.16 release
  • Folke Meyer 
    • Add data ingestion section to Docker installation documentation
    • Continue work on Docker setup instructions
  • Brian Lowe 
    • Work on first two tickets from new issues list
    • Document additional bugs noticed in VIVO
      • Create issue ticket for Jenna library sorting bug affecting Solar sort fields
  • Georgy Litvinov 
    • Rename custom browse filter page to clarify it covers custom page creation with filters
    • Add documentation for user roles management as paragraphs 
    • Create separate page for data distribution API with screenshots and detailed descriptions
    • Consider adding documentation for reporting features
  • Benjamin Kampe 
    • Investigate and resolve security vulnerabilities flagged in ORCID pull request
    • Fix failing build in ORCID pull request
  • Christian Hauschke 
    • Review and remove outdated documentation for VIVO versions prior to 1.6
  • Miloš Popović 
    • Convert remaining two draft pull requests on VIVO side to ready for review

Previous Tasks 

  • Dragan Ivanovic 
    • Create Wiki/Confluence accounts for Folke, Muthuraj, Svetlana, and Gazi
    • Share poll via Slack for new meeting time slot
    • Follow up with Washington about contributing visualization work, Muturaj to follow up discussion
    • Create release candidate for VIVO 1.16
    • Announce release candidate to the community 
    • Contact Jose again regarding OAI-PMH component
    • Share information with Amin about euroCRIS/4Science project on equipment description
    • Update the wiki documentation to reflect the release of 1.14.4 and 1.15.1 and include information about patching.
    • Convert the VIVO-ORCID pull request to "ready for review" status once notified by Ivan.
    • Merge XSS fixes to the VIVO main branch
    • Release a patch for VIVO 1.15 and 1.14.
    • Contact Jose Ortiz again regarding Crosswalk work
  • Georgy Litvinov 
    • Create new pull request from scratch for Elastic Search connection pooling solution and notify Dragan when pull request is created
    • Help with instructions in google forms about testing word and excel reporting
    • Investigate why the JSON configuration file for the branding VIVO pull request is not being copied to the expected Apache web folder
  • Brian Lowe
    • Create GitHub issue for CSV to RDF model selection bug
    • Merge approved pull requests for UI labels improvements
  • Bridget Almas 
    • Create VIVO 1.17.x documentation space with restricted acces
    •  
  • Miloš Popović 
    •  Complete work on second pair of pull requests for accessibility guidelines
  • Ivan Mrsulja 
    • Add a "refresh configuration" button to reload JSON configuration without restarting, implement full locale support in translations (not just language codes), and open pull request for VIVO Harvester
    • Implement centralized dashboard for scheduled tasks (VIVO-Harvester)
    • Add edit functionality for scheduled tasks
    • Change "wordiness" label to "log level" for clarity
    • Continue VIVO harvester refactoring work and consider renaming files to use standardized names instead of source-specific names
    • Complete the VIVO-ORCID pull request (layout issue of some buttons) and inform Dragan when it is ready for review
  • Folke Meyer 
    • Move Docker installation instructions from draft wiki page to 1.17 private documentation space
    • Begin VIVO installation and testing using Docker
    • Document installation process and share feedback via Slack
    •  
  • Benjamin Kampe 
    • Create pull request for ORCID authentication implementation (next week after Eastern vacation)
    • Complete ORCID sign-in integration work
  • Jessica
    • Create project repository for CST interoperability specifications and give VIVO team commenting privileges
  • No labels

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