Legend:
| Status | ||
|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
...
Campuses who have already moved fields can keep their changes for the Vanguard if they like
For campuses who have not yet moved data or who have moved data but want to experiment with different options:
Option 1: If a campus doesn’t have the capacity to move local data to specific fields: Move all local 5xx to 590, all local 6xx to 690, all local 7xx to 97X
Option 2: If a campus has the capacity to move local data to specific fields, they can map their data however they like (there is a sample mapping for consideration here)
Option 3: Campuses interested in experimenting with holdings data can copy/move 541, 561-563, 583 data to those same fields in holdings records
Option 4: Campuses can leave existing fields as-is and test out what gets lost during migration or/and how it affects search and/display of other campuses” Primo VE
Option 5: Campuses can experiment with any combination of the above
Campuses will experiment with the Vanguard data and ask for SC CKG and Discovery FG input for recommendations for go-live
Campuses will record where they’ve relocated fields so that we can have an idea of scope for potential harmonization for go-live
...