Abstract: A method comprising receiving a data insertion request, where the data insertion request includes a data reference, indicating data to be stored, and a data repository (108) indicator indicating a data repository (108), from amongst a plurality of data repositories in which the data is to be stored, and wherein at least one data repository from the plurality of data repositories is a big data system. Further, a resource type, from amongst one or more resource types, corresponding to the data repository (108), is identified based on the data insertion request. Further, a configuration element, from amongst one or more configuration elements, corresponding to the data repository (108) is determined based on the resource type. Further, an application programming interface (API) associated with the configuration element is triggered for establishing a connection with the data repository (108) for storing the data.
CLIAMS:1. A method for establishing a connection between a content management system (102) and a data repository (108), the method comprising:
receiving, by a configuration module (120), a data insertion request from a user device (104), wherein the data insertion request includes a data reference indicating data to be stored and a data repository indicator indicating a data repository (108), from amongst a plurality of data repositories, in which the data is to be stored, and wherein at least one data repository from the plurality of data repositories is a big data system;
identifying, by a processor, a resource type, from amongst one or more resource types, corresponding to the data repository (108) based on the data insertion request, wherein each of the one or more resource types corresponds to a respective data repository (108) from the plurality of data repositories;
determining, by the processor, a configuration element, from amongst one or more configuration elements, corresponding to the data repository (108) based on the resource type; and
triggering, by the processor, an application programming interface (API) associated with the configuration element for establishing a connection with the data repository (108) for storing the data.
2. The method as claimed in claim 1, wherein the content management system (102) is a JAVA based content management system.
3. The method as claimed in claim 1, wherein the determining further comprises identifying, by the processor, the data repository (108) corresponding to the resource type.
4. The method as claimed in claim 1, wherein the method further comprises:
ascertaining, by a communication module (122), a path indicating a location in the data repository (108) based on a predetermined application schema; and
providing, by the communication module (122), the data to the data repository (108) for storing the data in the location based on the path.
5. The method as claimed in claim 4, wherein the method further comprises:
receiving, by the communication module (122), a data retrieval request from the user device;
obtaining, by the communication module (122), the data stored in the data repository (108) based on the path; and
providing, by the communication module (122), the data to the user device (104).
6. The method as claimed in claim 1, wherein the data repository indicator, for the data being a metadata, indicates a java content repository (JCR) file system.
7. The method as claimed in claim 1, wherein the data repository indicator, for the data being a big data, indicates the big data system.
8. The method as claimed in claim 1, wherein the method further comprises performing at least one of a full text search and a metadata search on the data stored in the data repository (108).
9. A content management system (102) comprising:
a processor (110);
a configuration module (120) coupled to the processor (110) to,
receive a data insertion request from a user device (104), wherein the data insertion request includes a data reference indicating data to be stored and a data repository indicator indicating a data repository (108), from amongst a plurality of data repositories, in which the data is to be stored, and wherein at least one data repository from the plurality of data repositories is a big data system; and
identify a resource type, from amongst one or more resource types, corresponding to the data repository (108) based on the data insertion request, wherein each of the one or more resource types corresponds to a respective data repository (108) from the plurality of data repositories; and
a communication module (122) coupled to the processor (110) to,
determine a configuration element, from amongst one or more configuration elements, corresponding to the data repository (108) based on the resource type; and
trigger a plug-in API associated with the configuration element for establishing a connection with the data repository (108) for storing the data.
10. The content management system (102) as claimed in claim 9, wherein the communication module (122) further:
ascertains a path, based on a predetermined application schema, indicating a location in the data repository (108) for storing the data; and
provides the data to the data repository (108) for storing the data in the location based on the path.
11. The content management system (102) as claimed in claim any of the preceding claims, wherein the communication module (122) further:
receives a data retrieval request from the user device (104) for retrieving the data;
obtains the data stored in the data repository (108) based on the path; and
provides the data to the user device (104).
12. The content management system (102) as claimed in claim 12, wherein the configuration module (120) further performs at least one of a full text search and a metadata search on the data stored in the data repository (108)
13. A computer-readable medium having embodied thereon a computer program for establishing a connection between a content management system and a data repository, the method comprising:
receiving a data insertion request from a user device (104), wherein the data insertion request includes a data reference indicating data to be stored and a data repository indicator indicating a data repository, from amongst a plurality of data repositories, in which the data is to be stored, and wherein at least one data repository from the plurality of data repositories is a big data system;
identifying a resource type, from amongst one or more resource types, corresponding to the data repository based on the data insertion request, wherein each of the one or more resource types corresponds to a respective data repository from the plurality of data repositories;
determining a configuration element, from amongst one or more configuration elements, corresponding to the data repository based on the resource type; and
triggering an application programming interface (API) associated with the configuration element for establishing a connection with the data repository for storing the data. ,TagSPECI:As Attached
| # | Name | Date |
|---|---|---|
| 1 | 2097-MUM-2013-Correspondence to notify the Controller [30-01-2023(online)].pdf | 2023-01-30 |
| 1 | SPEC IN.pdf | 2018-08-11 |
| 2 | FORM 5.pdf | 2018-08-11 |
| 2 | 2097-MUM-2013-US(14)-HearingNotice-(HearingDate-08-02-2023).pdf | 2023-01-13 |
| 3 | FORM 3.pdf | 2018-08-11 |
| 3 | 2097-MUM-2013-CLAIMS [26-09-2019(online)].pdf | 2019-09-26 |
| 4 | FIGURES IN.pdf | 2018-08-11 |
| 4 | 2097-MUM-2013-COMPLETE SPECIFICATION [26-09-2019(online)].pdf | 2019-09-26 |
| 5 | ABSTRACT.jpg | 2018-08-11 |
| 5 | 2097-MUM-2013-DRAWING [26-09-2019(online)].pdf | 2019-09-26 |
| 6 | 2097MUM2013.pdf | 2018-08-11 |
| 6 | 2097-MUM-2013-FER_SER_REPLY [26-09-2019(online)].pdf | 2019-09-26 |
| 7 | 2097-MUM-2013-OTHERS [26-09-2019(online)].pdf | 2019-09-26 |
| 7 | 2097-MUM-2013-FORM 3(11-2-2014).pdf | 2018-08-11 |
| 8 | 2097-MUM-2013-FORM 3 [12-09-2019(online)].pdf | 2019-09-12 |
| 8 | 2097-MUM-2013-FORM 26(1-10-2013).pdf | 2018-08-11 |
| 9 | 2097-MUM-2013-FORM 18.pdf | 2018-08-11 |
| 9 | 2097-MUM-2013-FER.pdf | 2019-03-29 |
| 10 | 2097-MUM-2013-CORRESPONDENCE(1-10-2013).pdf | 2018-08-11 |
| 10 | 2097-MUM-2013-FORM 1(16-7-2013).pdf | 2018-08-11 |
| 11 | 2097-MUM-2013-CORRESPONDENCE(11-2-2014).pdf | 2018-08-11 |
| 11 | 2097-MUM-2013-CORRESPONDENCE(16-7-2013).pdf | 2018-08-11 |
| 12 | 2097-MUM-2013-CORRESPONDENCE(11-2-2014).pdf | 2018-08-11 |
| 12 | 2097-MUM-2013-CORRESPONDENCE(16-7-2013).pdf | 2018-08-11 |
| 13 | 2097-MUM-2013-CORRESPONDENCE(1-10-2013).pdf | 2018-08-11 |
| 13 | 2097-MUM-2013-FORM 1(16-7-2013).pdf | 2018-08-11 |
| 14 | 2097-MUM-2013-FER.pdf | 2019-03-29 |
| 14 | 2097-MUM-2013-FORM 18.pdf | 2018-08-11 |
| 15 | 2097-MUM-2013-FORM 26(1-10-2013).pdf | 2018-08-11 |
| 15 | 2097-MUM-2013-FORM 3 [12-09-2019(online)].pdf | 2019-09-12 |
| 16 | 2097-MUM-2013-FORM 3(11-2-2014).pdf | 2018-08-11 |
| 16 | 2097-MUM-2013-OTHERS [26-09-2019(online)].pdf | 2019-09-26 |
| 17 | 2097-MUM-2013-FER_SER_REPLY [26-09-2019(online)].pdf | 2019-09-26 |
| 17 | 2097MUM2013.pdf | 2018-08-11 |
| 18 | 2097-MUM-2013-DRAWING [26-09-2019(online)].pdf | 2019-09-26 |
| 18 | ABSTRACT.jpg | 2018-08-11 |
| 19 | FIGURES IN.pdf | 2018-08-11 |
| 19 | 2097-MUM-2013-COMPLETE SPECIFICATION [26-09-2019(online)].pdf | 2019-09-26 |
| 20 | FORM 3.pdf | 2018-08-11 |
| 20 | 2097-MUM-2013-CLAIMS [26-09-2019(online)].pdf | 2019-09-26 |
| 21 | FORM 5.pdf | 2018-08-11 |
| 21 | 2097-MUM-2013-US(14)-HearingNotice-(HearingDate-08-02-2023).pdf | 2023-01-13 |
| 22 | SPEC IN.pdf | 2018-08-11 |
| 22 | 2097-MUM-2013-Correspondence to notify the Controller [30-01-2023(online)].pdf | 2023-01-30 |
| 1 | search_29-03-2019.pdf |