Skip to content
This repository has been archived by the owner on May 14, 2022. It is now read-only.

Spawn a background export job when a new export is created #21

Merged
merged 1 commit into from
Jan 24, 2017
Merged

Conversation

escowles
Copy link
Member

No description provided.

@coveralls
Copy link

coveralls commented Jan 24, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 16f2d2f on spawn into a87b128 on master.

@@ -37,7 +38,7 @@ def set_export
# Only allow a trusted parameter "white list" through.
def export_params
params.require(:export).permit(:pid, :job, :status, :last_error, :last_success, :logfile,
:page)
:page, :ark)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will ARKs work as the unique key (I assume that's what this is for)? If we plan to export before the object is finished in some cases (didn't we?) If we don't mint an ARK until the object is "finished"...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're passing the ARK here so it can get passed to the export job and added to the Bag metadata. We use the pid as the unique key for retrieving the object from Fedora.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, OK.

@jpstroop jpstroop merged commit d9e6920 into master Jan 24, 2017
@jpstroop jpstroop deleted the spawn branch January 24, 2017 17:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants