Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Valkyrie Characterization and File attachment #5321

Merged
merged 4 commits into from
Jan 11, 2022
Merged

Valkyrie Characterization and File attachment #5321

merged 4 commits into from
Jan 11, 2022

Conversation

no-reply
Copy link
Contributor

adds valkyrie upload handling and characterization, based on the hydra-works service class, to allow characterizing file uploads of Valkyrie objects.

replaces #5303.

@samvera/hyrax-code-reviewers

@no-reply no-reply changed the title Valk char Valkyrie Characterization and File attachment Jan 11, 2022
tamsin johnson added 2 commits January 11, 2022 12:18
ValkyrieCharacterizationService was initially ported in from Hydra::Works and
lightly modified to work with Valkyrie. the ported code was a little messy, and
in want of cleanup.

the public interface on `#run` is changed here to use named parameters, and some
of the private methods are rewritten to harden them up. references to OM, which
was removed from the Hyrax dependency tree in 2019, are removed. unused and
opaque behavior around "proxied terms" is removed entirely. `#send`s are changed
to `#public_send` to avoid accidentally calling private behavior (which could be
injected by manipulating the mapping hash).

we also add a test for publishing the metadata updates on the metadata node, and
add the implementation for that.
@@ -34,6 +34,9 @@ def save(resource:)

resource_factory.to_resource(object: af_object)
rescue ActiveFedora::RecordInvalid, RuntimeError => err
raise "more serious and helpful error message" if
Copy link
Contributor

Choose a reason for hiding this comment

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

were you going to replace this message?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants