Currently we rely on metadataextractor subplugins to define concrete models for metadata tables which include a set mapping of metadata keys to look for and map into a metadata class instance.
It would be good if we could create an interface for admins to define and add custom metadata fields for any metadata class based on their organisations needs.
I am thinking something along the lines of an optional customdata field in the metadata abstract class which subplugin developers can use (or not) which stores any of these additional fields in a JSON encoded string in the customdata field, so it has no size limit and prevents making changes to the tables themselves.
Currently we rely on metadataextractor subplugins to define concrete models for metadata tables which include a set mapping of metadata keys to look for and map into a metadata class instance.
It would be good if we could create an interface for admins to define and add custom metadata fields for any metadata class based on their organisations needs.
I am thinking something along the lines of an optional
customdatafield in the metadata abstract class which subplugin developers can use (or not) which stores any of these additional fields in a JSON encoded string in thecustomdatafield, so it has no size limit and prevents making changes to the tables themselves.