Nick Clemens
e5f251a709
This patch allows for selection of framework to use when overlaying records - by default it is set to keep the initial framework To test: 1 - Create some records using one framework 2 - Export the records 3 - Edit the records to add fields not in original framework 4 - Stage records using a rule that will find matches 5 - Import 6 - Note records contain new fields on display, but they are lost on edit 7 - Apply patch 8 - Stage records again 9 - Select a framework that contains the new fields on import 10 - Import records 11 - Note records now use selected framework and are displayed/edited correctly Signed-off-by: Andrew Fuerste-Henry <andrewfh@dubcolib.org> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> |
||
|---|---|---|
| .. | ||
| BatchCancelHold.pm | ||
| BatchDeleteAuthority.pm | ||
| BatchDeleteBiblio.pm | ||
| BatchDeleteItem.pm | ||
| BatchUpdateAuthority.pm | ||
| BatchUpdateBiblio.pm | ||
| BatchUpdateBiblioHoldsQueue.pm | ||
| BatchUpdateItem.pm | ||
| CreateEHoldingsFromBiblios.pm | ||
| MARCImportCommitBatch.pm | ||
| MARCImportRevertBatch.pm | ||
| StageMARCForImport.pm | ||
| UpdateElasticIndex.pm | ||