-
Notifications
You must be signed in to change notification settings - Fork 0
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
Decide on migration path for avalon 4-6 (data + metadata #15
Comments
@csyversen and @carrickr I'll have you two help @mbklein out with this. The go live date is critical. |
I believe we should identify a subset of items for a targeted test migration. Maybe 25-30 items covering 2-3 collections. |
It is my hope that Avalon itself will be stable enough to start doing iterative test migrations within a few days, whether using the generic or NU skin. |
Right, I think we can test migrations without the skin. In fact having data will help Adam in his quest...
… On May 2, 2017, at 4:43 PM, Michael B. Klein ***@***.***> wrote:
It is my hope that Avalon itself will be stable enough to start doing iterative test migrations within a few days, whether using the generic or NU skin.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AElKnk7Lkosl0a-PG0cjofedelumyxTuks5r16N5gaJpZM4MdLUm>.
|
@mbklein Do we want to try some course reserve items? They have full movies in there which seems to the biggest and also comes with a boatload of permissions regarding classes. |
@carrickr it looks like we have a plan. Can you write up an extra technical issues and through them in the current sprint? |
@carrickr can you add a link or drop in the thoughts you wrote up directly here?
The text was updated successfully, but these errors were encountered: