UNIFIED REPOSITORY & TOOL INFRASTRUCTURE
A system and method are described herein that provide a repository and tool infrastructure (“RTI”) that provides common capabilities on both a client and server end based on standardized communication patterns and a unifying protocol that decouples existing repositories from multiple tools. The repository and tool infrastructure interface interacts with a single development editing tool and any repository housed on a server end and is implemented to each server or client technology if the common capabilities and communication patterns are fulfilled.
1 . A system having a unified repository and tool infrastructure to manage digital entities across repositories, the system comprising:
a user terminal, wherein a tool infrastructure component of the unified repository and tool infrastructure is situated on the user terminal;
a development tool situated on the user terminal;
a local server, wherein a repository infrastructure component of the unified repository and tool infrastructure is situated on the local server, the repository infrastructure component communicating to the tool infrastructure component through a representational state transfer interface; and
at least one repository located on the local server.
2 . The system according to claim 1 , wherein the repository infrastructure component communicates to the at least one repository through another representational state transfer interface.
3 . The system according to claim 1 , wherein the development tool is an open-source tool.
4 . The system according to claim 1 , further comprising:
a central server.
5 . The system according to claim 4 , wherein a federation infrastructure component of the unified repository and tool infrastructure is situated on the central server, the federation infrastructure component communicating to the tool infrastructure component and the repository infrastructure component through representational state transfer interfaces.
6 . The system according to claim 4 , wherein a transformation infrastructure component of the unified repository and tool infrastructure is situated on the central server, the transformation infrastructure component communicating to the tool infrastructure component and the repository infrastructure component through representational state transfer interfaces.
7 . The system according to claim 5 , wherein a transformation infrastructure component of the unified repository and tool infrastructure is situated on the central server, the transformation infrastructure component communicating to the tool infrastructure component, the repository infrastructure component, and the federation infrastructure component through additional representational state transfer interfaces.
8 . The system according to claim 6 , wherein additional repositories are connected to the transformation infrastructure component.
9 . The system according to claim 7 , wherein additional repositories are connected to the transformation infrastructure component.
10 . The system according to claim 8 , wherein the additional repositories are located on additional servers.
11 . The system according to claim 9 , wherein the additional repositories are located on additional servers.
12 . A method for managing digital entities across repositories, the method comprising:
identifying a developmental tool situated on a user terminal;
communicating from the development tool to a local server via a tool infrastructure component of a unified repository and tool infrastructure;
receiving the communication from the tool infrastructure component on the local server via a repository infrastructure component of the unified repository and tool infrastructure, the communication occurring through a representational state transfer message; and
accessing the data entities on at least one repository located on the local server.
13 . The method according to claim 12 , further comprising:
transmitting an additional representational state transfer message to communicate between the repository infrastructure component and the at least one repository.
14 . The method according to claim 12 , wherein the development tool is an open-source tool.
15 . The method according to claim 12 , further comprising:
retrieving content about requested resources from a federation infrastructure component located on a central server via an additional representational state transfer message.
16 . The method according to claim 12 , further comprising:
providing access to additional repositories through a transformation infrastructure component located on a central server via an additional representational state transfer message.
17 . The method according to claim 16 , wherein the additional repositories are located on additional servers.
18 . A method for combining subprocesses stored across multiple repositories, the method comprising:
identifying, with a unified repository and tool infrastructure, locations of the subprocesses in at least one repository;
determining, with the unified repository and tool infrastructure, a location for storage for a combined process;
retrieving the subprocesses from the at least one repository;
combining the retrieved subprocesses into the combined process; and
storing the combined process on a central server.
19 . A method for developing source code from previous releases of the source code, the method comprising:
identifying, with a unified repository and tool infrastructure, locations of systems or service containing the previous releases of the source code;
comparing, with the unified repository and tool infrastructure, the source code with each of the previous releases of the source code to determine changes made in each release; and
generating specific differences between the source code and the previous releases of the source code.
20 . A method for developing a mobile application integrating objects between distinct platforms, the method comprising:
identifying, with a unified repository and tool infrastructure, a location of middleware on different platforms to be integrated with a client platform;
accessing, with the unified repository and tool infrastructure, resources on the distinct platforms; and
federating the resources on the different platforms with the client platform to integrate with the client platform.