Closed regineheberlein closed 1 month ago
This has happened twice on the server. I'm running it locally over publicpolicy only now to see what happens.
Update: running and committing locally/manually succeeds without errors.
I'll make a note to check the next scheduled export and will open a new ticket if it happens again.
Expected behavior
The lib_jobs:send_eads job sends the EAD's exported from all repositories.
Actual behavior
The lib_jobs:send_eads job skips publicpolicy files when the rake task is run manually. The files were included in the last scheduled update. The logs suggest that the exports succeeded but nothing was committed to SVN. Since the job is now exporting
dao
elements when before it wasn't, the expected behavior is that all or most of the EAD exports in repo 3 have changes, so there shouldn't be nothing to commit.Steps to replicate
bundle exec rake lib_jobs:send_eads
inlib_jobs
Impact of this bug
We are missing an important part of the snapshot. We also can't use the data as another checkpoint to count active digital objects (see #https://github.com/pulibrary/aspace_helpers/issues/614)
Acceptance criteria