Abstract: A computer system identifies an information set stored at a data store. The computer system then identifies first metadata that includes first instructions indicating how the information set is to present a plurality of data items, and second pre-existing metadata that includes second instructions indicating how the information set is to present the plurality of data items. The computer system determines that a portion of the first metadata will override a portion of the second metadata, to create combined metadata. The computer system provides the combined metadata to the information set, including combining the second metadata with the first metadata by at least overriding the second instructions of the second metadata with the first instructions of the first metadata. The computer system presents the plurality of data items in accordance with the second metadata, at least as modified by the first instructions of the first metadata.

Abstract: A computer system identifies an information set stored at a data store. The computer system then identifies first metadata that includes first instructions indicating how the information set is to present a plurality of data items, and second pre-existing metadata that includes second instructions indicating how the information set is to present the plurality of data items. The computer system determines that a portion of the first metadata will override a portion of the second metadata, to create combined metadata. The computer system provides the combined metadata to the information set, including combining the second metadata with the first metadata by at least overriding the second instructions of the second metadata with the first instructions of the first metadata. The computer system presents the plurality of data items in accordance with the second metadata, at least as modified by the first instructions of the first metadata.

Abstract: A computer system identifies an information set stored at a data store. The computer system then identifies first metadata that includes first instructions indicating how the information set is to present a plurality of data items, and second pre-existing metadata that includes second instructions indicating how the information set is to present the plurality of data items. The computer system determines that a portion of the first metadata will override a portion of the second metadata, to create combined metadata. The computer system provides the combined metadata to the information set, including combining the second metadata with the first metadata by at least overriding the second instructions of the second metadata with the first instructions of the first metadata. The computer system presents the plurality of data items in accordance with the second metadata, at least as modified by the first instructions of the first metadata.

Abstract: Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. In one scenario, a computer system receives a data item request that identifies which data items are to be reported. The computer system accesses a relational data store to determine which information sets are to be used for reporting the requested data items. Based on the determination, the computer system accesses those information sets that are to be used in the reporting the requested data items. The computer system then determines that metadata has been provided for at least one of the accessed information sets. The metadata includes instructions at least partially indicating how the data items are to be reported. The computer system also reports the data items according to the instructions in the provided metadata, regardless of how the data items are to be reported using the existing information sets.

Abstract: Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. Embodiments include a computer system receiving a database query including a request to edit one or more data items in the database. The computer system determines which data items would be affected by the requested data item edit. Based on the determination, the computer system accesses those data items that would be affected by the requested data item edit. The computer system retrieves metadata for each data item that would be affected by the requested data item edit. The metadata includes information at least partly indicating how the edit is to be performed. The computer system also performs the edit to affect the data items according to at least a portion of the retrieved metadata, regardless of how the edit would otherwise have been performed based on existing knowledge about the affected data items.

Abstract: In one embodiment, a computer system generates a view of entities associated with varying data types for presentation on a generic viewer. The entities and data types have relationships as defined in a corresponding schema. The schema is stored as data in a repository with the data types. The computer system receives an edit request configured to change various selected entities, where each entity has an associated data type, queries the repository to determine various properties of the selected entities corresponding to the received edit request including the data type, and determines, based on the schema, that the edit is valid based on relationship information stored in the schema. The computer system also sends the validated edit information to the generic viewer for presentation. The generic viewer has no prior knowledge of how to handle the selected entities and corresponding data types.

Abstract: Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. In one scenario, a computer system receives a data item request that identifies which data items are to be reported. The computer system accesses a relational data store to determine which information sets are to be used for reporting the requested data items. Based on the determination, the computer system accesses those information sets that are to be used in the reporting the requested data items. The computer system then determines that metadata has been provided for at least one of the accessed information sets. The metadata includes instructions at least partially indicating how the data items are to be reported. The computer system also reports the data items according to the instructions in the provided metadata, regardless of how the data items are to be reported using the existing information sets.

Abstract: Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Abstract: Methods, systems, and computer program products are provided for securing resource stores with claims-based security. From policy information, a resource store populates a security table of permissions. The permissions authorize resource access based on received claims. Sessions submit claims to the resource store. The resource store accumulates claims for a session into a claims list. From the claims list and the security table, the resource store filters out a subset of metadata including resource IDs for resources the session is authorized to access. Since the metadata corresponds to the session, any application using the session is given similar access to resources at the resource store.

Abstract: Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Abstract: In one embodiment, a computer system performs a method for providing repository item information from one or more different perspectives using virtual repository items within a customizable presentation scheme. A computer system accesses a user-defined presentation scheme that describes a manner in which repository items are to be presented. The computer system generates virtual repository items for actual repository items based on the user-defined presentation scheme. The virtual repository items are generated for presentation along with their actual repository items. The computer system maps the virtual repository items to different virtualized sets of repository items according to the user-defined presentation scheme. The virtualized sets comprise at least one of actual repository items and virtual repository items. The computer system presents the virtualized sets of repository items in one or more different perspectives within the user-defined presentation scheme.

Abstract: Methods, systems, and computer program products are provided for securing resource stores with claims-based security. From policy information, a resource store populates a security table of permissions. The permissions authorize resource access based on received claims. Sessions submit claims to the resource store. The resource store accumulates claims for a session into a claims list. From the claims list and the security table, the resource store filters out a subset of metadata including resource IDs for resources the session is authorized to access. Since the metadata corresponds to the session, any application using the session is given similar access to resources at the resource store.

Abstract: The present invention extends to methods, systems, and computer program products for securing resource stores with claims-based security. From policy information, a resource store populates a security table of permissions. The permissions authorize resource access based on received claims. Sessions submit claims to the resource store. The resource store accumulates claims for a session into a claims list. From the claims list and the security table, the resource store filters out a subset of metadata including resource IDs for resources the session is authorized to access. Since the metadata corresponds to the session, any application using the session is given similar access to resources at the resource store.

Abstract: Embodiments and principles described herein relate to software repositories for common languages. Embodiments include maintaining database schema and structures which comprise application framework information and provides for the storage, querying, and retrieval of an abstraction of a namespace corresponding to an application framework. Embodiments also provide for the storage, querying and retrieval of information corresponding to parameters of methods within an application framework. Embodiments also include the storage, querying and retrieval of information corresponding to type information for constructed types within an application framework.

Abstract: Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Abstract: The present invention extends to methods, systems, and computer program products for securing resource stores with claims-based security. From policy information, a resource store populates a security table of permissions. The permissions authorize resource access based on received claims. Sessions submit claims to the resource store. The resource store accumulates claims for a session into a claims list. From the claims list and the security table, the resource store filters out a subset of metadata including resource IDs for resources the session is authorized to access. Since the metadata corresponds to the session, any application using the session is given similar access to resources at the resource store.

Abstract: Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. Embodiments include a computer system receiving a database query including a request to edit one or more data items in the database. The computer system determines which data items would be affected by the requested data item edit. Based on the determination, the computer system accesses those data items that would be affected by the requested data item edit. The computer system retrieves metadata for each data item that would be affected by the requested data item edit. The metadata includes information at least partly indicating how the edit is to be performed. The computer system also performs the edit to affect the data items according to at least a portion of the retrieved metadata, regardless of how the edit would otherwise have been performed based on existing knowledge about the affected data items.

Abstract: In one embodiment, a computer system generates a view of entities associated with varying data types for presentation on a generic viewer. The entities and data types have relationships as defined in a corresponding schema. The schema is stored as data in a repository with the data types. The computer system receives an edit request configured to change various selected entities, where each entity has an associated data type, queries the repository to determine various properties of the selected entities corresponding to the received edit request including the data type, and determines, based on the schema, that the edit is valid based on relationship information stored in the schema. The computer system also sends the validated edit information to the generic viewer for presentation. The generic viewer has no prior knowledge of how to handle the selected entities and corresponding data types.

Abstract: Embodiments and principles described herein relate to software repositories for common languages. Embodiments include maintaining database schema and structures which comprise application framework information and provides for the storage, querying, and retrieval of an abstraction of a namespace corresponding to an application framework. Embodiments also provide for the storage, querying and retrieval of information corresponding to parameters of methods within an application framework. Embodiments also include the storage, querying and retrieval of information corresponding to type information for constructed types within an application framework.

Abstract: The present invention extends to methods, systems, computer program products, and data structures for software repositories. Embodiments of the invention permit a user to group software related items from a software repository in repository container versions such that software related items can be accessed and processed together. A user has wide discretion on how software related items are grouped in repository container versions to facilitate efficient access and processing in varied computing environments. In some embodiments, software related items are grouped in the same repository container version based on component version such that all the software related items for a specified version of an application, framework, or service can be accessed and processed together. Accordingly, operations (e.g.