Many library catalog system have a catalog record and a separate set of instances of that record, so that certain fields and information are not duplicated. Our library data in not structured in this way, but it is ideal to reduce the duplication of data especially when data gets out of sync for multiple copies of the same book. A compromise to this, since rearchitecting the entire library database wasn't feasible, was to introduce a main record + copy record system, enabling a record to be attached to another record and inherit many of it's fields from it. Editing either main or copy record will sync its data from the main/with copies.
In this PR:
Adds a gibbonLibraryItemIDParent field to the Library table in the database
Adds an option to attach library items via ID in Edit Record
Adds an alert to library items that are main records or copies
Adds actions to easily view and modify main records and copies
Fixes empty timestamp field in gibbonLibraryItem table that caused errors on update
Improves the display of the the Manage Catalog search
Adds a confirmation step to replace the name of books using Google Book Data
How Has This Been Tested?
Locally and in production
Many library catalog system have a catalog record and a separate set of instances of that record, so that certain fields and information are not duplicated. Our library data in not structured in this way, but it is ideal to reduce the duplication of data especially when data gets out of sync for multiple copies of the same book. A compromise to this, since rearchitecting the entire library database wasn't feasible, was to introduce a main record + copy record system, enabling a record to be attached to another record and inherit many of it's fields from it. Editing either main or copy record will sync its data from the main/with copies.
In this PR:
How Has This Been Tested? Locally and in production
Screenshots