Feature/harvester integration#4136
Open
ivanmrsulja wants to merge 10 commits into
Open
Conversation
…tion and granular URL generation.
…wing and general import process manipulation.
…. Added configurable log directory.
…ion labels. Fixed some issues.
milospp
force-pushed
the
feature/harvester-integration
branch
from
March 4, 2026 20:39
8ede5d9 to
313f042
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue 4105
Linked Vitro PR
Linked VIVO-Harvester PR
What does this pull request do?
Implemented VIVO - VIVOHarvester integration using configuration file and dynamic form rendering.
What's new?
How should this be tested?
In
runtime.properties, the following should be set:harvester.directory=directory where VIVOHarvester is installedharvester.configuration=example-scripts/bash-scripts/full-harvest-examples/examples/export-config/export-config.jsonworkflow.scheduler.scan=0 * * * * * - for testing only, once per day in production environmentsworkflow.log.directory=/tmpAdditionally, VIVOHarvester should be built from this PR and Vitro should be built from this PR.
After that, simply logging in as
adminand navigating to/etlWorkflowsshould present all relevant functionality to you (task running, scheduling, scheduled task CRUD and current/scheduled task log CRUD).Interested parties
@chenejac
Reviewers' expertise
Candidates for reviewing this PR should have some of the following expertises: