Package io.goobi.viewer.dao.update
package io.goobi.viewer.dao.update
Database migration and update classes that apply structural and data-level changes to the Goobi viewer
database schema during application upgrades, coordinated by the central
DatabaseUpdater.-
ClassDescriptionDatabase migration step that removes the obsolete
main_titlecolumn from thebookshelf_itemstable.Converts all Tags and Classifications from previous viewer-cms versions to theCMSCategorysystem.Helper class used during the CMS page migration that converts raw legacy database rows into typedCMSContentobjects.Convertscms_media_items.link_urlfrom the LONGBLOB datatype (URI in java) to TEXT (String in java).Convertscms_media_items.link_urlfrom the LONGBLOB datatype (URI in java) to TEXT (String in java).Database migration step that converts CMS pages from the legacy content-item/language-version schema to the current component-based schema, including template creation and table cleanup.Extends cms_record_notes table by row 'note_type' which discriminates between the implementing classes.Database migration step that ensures the static "all comments"CommentGroupexists in the database, creating it if it is missing.Management tool to updated deprecated viewer database setups to the one required by the viewer. to be run at viewer start, right after initializing the dao Appplies a fixed list ofIModelUpdatesto theIDAOwhich are responsible to make the required changesDatabase migration step that converts the legacy flat GeoMap structure into the feature-set model and migrates theaggregate_resultscolumn to thesearch_scopefield.Interface for classes which manipulate the database to conform to the setup required by the viewer.Database migration step that removes the obsolete crowdsourcing-campaigns license type and drops the deprecatedconditionscolumn from thelicense_typestable.Database migration step that migrates existing licenses to the newLicenseRightsHoldermodel and removes obsolete columns from thelicensestable.Database migration step that performs miscellaneous housekeeping tasks, such as dropping obsolete tables that are no longer used by the application.Database migration step that renames the legacyTEMPLATEIDcolumn incms_pagestopage_template_idand clears stale template ownership references on CMS components.Database migration step that renames the legacyrolestable touser_roles, handling the case where EclipseLink may have already created the new table.Migrates migrates data from the deprcated table cms_sidebar_elements to the new table cms_page_sidebar_elements, which backsCMSSidebarElement.Database migration step that renames thesubtheme_discriminatorcolumn tosubthemein bothcms_pagesandcms_page_templates, migrating data where both columns coexist.Database migration step that renames the legacyvaluecolumn totranslation_valuein all translation tables that still use the old column name.