Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: Architectures and Techniques for Record Protection and Field Management. A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: Architectures and Techniques for Record Protection and Field Management. A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: A user-centric computing system that includes a mobile storage device (“MSD”) capable of interfacing with a client personal computer (“PC”) for the purpose of using certain resources available through the client PC to access user programs, applications, data, and settings stored on the MSD. The user-centric computing system may also include a software management program configured to select the user programs, applications, data and settings to be stored on the MSD from the user programs, applications, data, and settings installed on a user's PC and to interface with the client PC. A method of providing mobility to a user PC by selecting programs installed on the user PC and storing the selected programs on an MSD and interfacing the MSD with a client PC is also provided.