Category_legacy features

Category_legacy is a module that is included as part of the categoryi package. It allows data generated by the taxonomy and book modules to be imported into the category module, and vice versa. Features include:

Existing data backed up

In the case of a taxonomy import, existing data needs to be deleted, and this inevitably means that there is a risk of data loss should anything go wrong. For this reason, taxonomy data can be backed up in a safe archive before performing an import.

Legacy data structures transformed

All the data stored for taxonomy and book items is transformed into its corresponding category data structures. For example, parenti-child relationships, weightis, related terms, and synonyms are all included in the import.

Category-specific data can be appended

For all the data that you import, category-specific fields can be appended and configured by you. For example, you can choose whether the categories you import will have menu items, a TOC, and hidden containeriis.

Legacy path redirection

When performing a taxonomy import, your data will have new URLs as categories. However, your existing taxonomy URLs can be configured to automatically redirect to their corresponding new category URLs. This redirection keeps track of term-to-node ID mappings, and can handle redirection of complex taxonomy paths, such as AND/OR queries and RSS feeds.

Extensible architecture

Category_legacy has its own hook, which allows other modules to append additional fields to data structures during an import, and which lets modules perform additional operations when an import takes place. This hook is implemented in other modules, including category itself, making category_legacy lighter and more maintainable.