18060150. CROSS ORGANIZATIONAL METADATA MIGRATION simplified abstract (Honeywell International Inc.)
Contents
- 1 CROSS ORGANIZATIONAL METADATA MIGRATION
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 CROSS ORGANIZATIONAL METADATA MIGRATION - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
CROSS ORGANIZATIONAL METADATA MIGRATION
Organization Name
Inventor(s)
Eric Hartye of Oak Ridge TN (US)
CROSS ORGANIZATIONAL METADATA MIGRATION - A simplified explanation of the abstract
This abstract first appeared for US patent application 18060150 titled 'CROSS ORGANIZATIONAL METADATA MIGRATION
Simplified Explanation
The abstract describes a system for managing metadata between organizations within an enterprise, where code features are received, tagged, stored, and provided based on requests.
- Code features are received from a first organization and tagged with code feature tags.
- Tagged code features are stored in a repository accessible by a second organization.
- Requests for features are checked to see if they are tagged code features, and if so, provided to the requester.
Potential Applications
This technology could be applied in software development environments where multiple organizations collaborate on projects and need to manage and share code features efficiently.
Problems Solved
1. Efficient management of metadata between organizations within an enterprise. 2. Streamlining the process of requesting and providing code features based on tags.
Benefits
1. Improved collaboration and communication between organizations. 2. Enhanced organization and accessibility of code features. 3. Increased efficiency in sharing and utilizing code resources.
Potential Commercial Applications
"Enterprise Metadata Management System for Efficient Code Sharing and Collaboration"
Possible Prior Art
There may be existing systems or tools that facilitate code sharing and collaboration between organizations within an enterprise, but specific prior art would need to be researched to determine any overlap with the described technology.
Unanswered Questions
== How does the system handle conflicts between different organizations tagging the same code features differently? The abstract does not address how conflicts in tagging code features between organizations are resolved. This could be a potential challenge in ensuring consistency and accuracy in metadata management.
== What security measures are in place to protect the repository and the tagged code features from unauthorized access? The abstract does not mention specific security measures implemented to safeguard the repository and the tagged code features. Ensuring data security and access control would be crucial in maintaining the integrity of the system.
Original Abstract Submitted
Various embodiments described herein relate to managing metadata between organizations within an enterprise. In this regard, a set of code comprising one or more code features is received from a first organization. The one or more code features are tagged with one or more code feature tags to associate each of the one or more code features with the one or more code feature tags. The one or more tagged code features are stored in a repository based on the one or more code feature tags. The repository is at least partially accessible by a second organization. Based on a request received from a requestor for one or more features, it is determined if the one or more requested features are tagged code features. Further, one or more of the tagged code features are provided to the requester based on the requested features having been tagged as tagged code features.
