michael-wynne-wsu
commented
7 months ago Confirmed that Labels DO migrate from v3 as @nick-deer described.
Questions/concerns:
1) The migrated "legacy" label projects are functional in v4, in that they can be applied to new content, and content using them can have those fields modified. The hope was that they would be completely unavailable for ongoing use. Discussion needed (it might be limited enough to still meet our needs).
2) The expected user action is that they will replace the legacy projects with active LC Hub projects. We don't know if their projects would be exactly the same or if they'll be shuffling things around as the begin work with LC. I can think of a few possible workflows (none assessed for reality yet):
- a) Add projects as needed, then "manually" (in-site or batch) add new project/label info to items, remove old info, then delete legacy projects. Tedious, but allows for per-item review if needed.
- b) Build a system to add new projects, then identify which Hub project replaces with legacy project and automate the replacement. If their projects are very different from the v3 label use this might not be practical.
@alexmerrill
Is there a system for migrated (from v3) legacy labels to be converted into v4 Hub-compliant labels?