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

Non-Copy Datastream Migrations #39

Open
barmintor opened this issue Mar 21, 2015 · 1 comment
Open

Non-Copy Datastream Migrations #39

barmintor opened this issue Mar 21, 2015 · 1 comment

Comments

@barmintor
Copy link
Contributor

I'm working on a fork that would allow registration of Mover classes for content migrations by attached_file name, and wanted to open a conversation here. The idea is that, for a target class that (<>ldp:contains 'foo','bar'), the ObjectMover has a map (defaulting to DatastreamMover) of Mover impls that might perform some arbitrary action for the migration of that content. For example, it may go grab the contents for 'foo' from another object that won't be migrated, or just insert default content.

@mjgiarlo @Cam156 @awead

@barmintor
Copy link
Contributor Author

@awead awead removed their assignment Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants