WO2015127495A1

WO2015127495A1 - System and method for processing content on an enterprise content management system

Info

Publication number: WO2015127495A1
Application number: PCT/AU2015/000102
Authority: WO
Inventors: James Raymond FOX; Carmeron Clayton Jade DWYER; Colin John WOOD
Original assignee: Scinaptic Communicastions Pty Ltd
Priority date: 2014-02-27
Filing date: 2015-02-26
Publication date: 2015-09-03
Also published as: WO2015127495A8

Abstract

A method for identifying and presenting locations and content to efficiently access and save content on an Enterprise Content Management (ECM) platform is disclosed. The method includes creating a profile including definitions of at least one location item or content item. The location items provide mechanisms for presenting locations within the ECM platform and the content items provide mechanisms present content.. The method further includes creating and applying authorization and/or membership information to the profile, publishing the profile into a central repository, displaying the profile along with the at least one location or content item through a user interface based on user authentication, and accepting a selection of one of the at least one location or content item. Furthermore, the method includes retrieving results, from the ECM platform, based on the selection. The retrieved results include artefacts that the end user is allowed to access. The method also includes displaying the results on the user interface.

Description

SYSTEM AND METHOD FOR PROCESSING CONTENT ON AN ENTERPRISE CONTENT MANAGEMENT SYSTEM

TECHNICAL FIELD

[0001 ] Aspects of the present disclosure are generally related to content management systems and more particularly to methods and systems for processing content on enterprise content management systems.

BACKGROUND

[0002] Businesses are increasingly employing enterprise level content management solutions, typically called Enterprise Content Management (ECM) systems, to manage the creation, storage, access, and collaboration of content/data. A typical implementation of an ECM solution is an Electronic Document and Records Management System (EDRMS), with other examples including digital asset management systems, legal case management systems, and project management systems.

[0003] ECM platforms provide efficient management of information with capture, classification, security, workflow, collaboration, and access to content. The underlying information architecture for each ECM solution generally varies based on business requirements, technology constraints, and the experience of personnel responsible for the creation for the ECM solution. For example, in one scenario, a case management solution on an ECM technology platform, such as SharePoint* may contain a site collection for each customer, a site for each case, and a number of libraries/lists and document sets to save content. Alternatively, the same case management solution could be implemented with a SharePoint* site library representing the case management system at the highest level, a folder within the library for each customer, one or more document sets representing each customer matter and a series of folders within each document set for storing different types of content. In a similar vein, the same solution could again be architected differently on an alternate ECM technology platform such as Lotus Notes^®, or even a Window^® Explorer File System.

[0004] Regardless of the technology and information architecture implemented to meet the business requirement, an end user often finds saving and accessing content from a particular location cumbersome, time consuming, and ultimately, disengaging. This may be attributed to sheer volume of data present on the ECM system or to inefficient and excessively complicated user interfaces or user experience (UX).

[0005] Accordingly, there exists a need for a method and system to allow end users to save and access content in an enterprise content management system in a streamlined manner with relative ease. SUMMARY

[0006] It is an object of the present disclosure to substantially overcome, or at least ameliorate, one or more disadvantages of existing arrangements.

[0007] According to one aspect of the present disclosure, a computer-implemented method for processing content on an Enterprise Content Management (ECM) platform is presented. The method includes creating a profile including definitions of at least one location item or content item. The location item provides a mechanism for presenting locations from the ECM platform that are pertinent to a user of the created profile, while the content item provides a mechanism for presenting content from the ECM platform pertinent to the user of the created profile. The method further includes creating and applying authorization and/or membership information to the profile, publishing the profile into a central repository, and displaying the profile along with the at least one location and/or content item through a user interface based on user authentication. The method further includes the steps of accepting a selection of one of the at least one location and/or content item, retrieving results, from the ECM platform, based on the selection, where the retrieved results comprising artefacts pertinent to the user and available to the user to access; and displaying the results on the user interface.

[0008] According to another aspect of the present disclosure, a system for processing content on an Enterprise Content Management (ECM) platform is provided. The system includes a profile module configured to create a profile. The profile includes definitions of at least one location item and/or content item pertinent to the user. The location item provides a mechanism for presenting locations within the ECM platform, and the content item provides a mechanism for presenting content within the ECM platform. The profile module is further configured to create authorization information associated with the profile, and publish the profile along with the authorization information in a central repository. The system further includes a user interface configured to display the profile and at least one of the location and/or content item associated with the profile based on user authentication and accept a selection of one of the at least one location and/or content item. Furthermore, the system includes an input/output module configured to provide the selection to the ECM platform; and retrieve results, from the ECM platform, based on the selection, the retrieved results comprising artefacts that an end user is allowed to access; and display the results on the user interface.

[0009] According to another aspect of the present disclosure, a computer-implemented method for processing content on an Enterprise Content Management (ECM) platform is presented. The method includes creating a profile including definitions of at least one search location or shortcut location. The search location provides a search based mechanism for presenting locations within the ECM platform and the shortcut location provides a mechanism to use a hierarchical structure for browsing physical structure of the ECM platfonn. The method further includes creating and applying authorization information to the profile, publishing the profile into a central repository, displaying the profile along with the at least one search location or shortcut location through a user interface based on user authentication, and accepting a selection of one of the at least one search location or shortcut location. Furthermore, the method includes retrieving results, from the ECM platfonn, based on the selection. The retrieved results include artefacts that an end user is allowed to access. The method also displays the received results on the user interface.

|0010] According to yet another aspect of the present disclosure, a system for processing content on an Enterprise Content Management (ECM) platform is presented. The system includes a profile module configured to accept inputs for creating a profile. The profile includes definitions of at least one search location or shortcut location, where the search location provides a search based mechanism for presenting locations within the ECM platform and the shortcut location provides a mechanism to use a hierarchical structure for browsing physical structure of the ECM platform. The profile module is also configured to create authorization information associated with the profile, publish the profile, and store the authorization in a central repository. The system also includes a user interface configured to display the profile and at least one of the search location or the shortcut location associated with the profile, and accept an input provided via selection of one of the at least one search location or shortcut location. Moreover, the system includes an input/output module configured to provide the selection to the ECM platform, and retrieve results from the ECM platfonn based on the selection. The retrieved results include artefacts that an end user is allowed to access. The input/output module also configured to display the results on the user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011 ] At least one anangement of the present disclosure will now be described with reference to the drawings.

[0012] FIG. 1 is a block diagram illustrating an enterprise content management platfonn.

[0013] Figs. 2A and 2B depict a general-purpose computer system 200, upon which the various anangements described can be practiced.

[0014] FIG. 3 is a block diagram illustrating an access system.

[0015] FIG. 4 is a screenshot of an example final search query.

[0016] FIG. 5 is a screenshot of an example user interface displaying profiles.

[0017] FIG. 6 is a flowchart illustrating a method of processing content in the ECM platfonn. [0018] FIG. 7 is a flowchart illustrating another method of processing content in the ECM platform.

[0019] FIG. 8 is a screenshot of an example user interface displaying a content item.

[0020] While the systems and methods described herein are amenable to various modifications and alternative forms, specific implementations are shown by way of example in the drawings and are described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the systems and methods described herein to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.

DETAILED DESCRIPTION

[0021 ] Specific arrangements will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency.

[0022] In the following detailed description, numerous specific details are set forth in order to provide a more thorough understanding of the methods and system disclosed below. In other instances, well-known features have not been described in detail to avoid obscuring the disclosed methods and systems.

[0023] In organizations, content/data is created every day. To manage such data, organizations employ ECM platforms. However, these platforms are typically focused around the management of unstructured content (e.g. documents, emails, files, profiles, blogs, and so on) rather than highly transactional, relational data. Due to the high volume of unstructured content, often finding a particular document or folder on the ECM platform becomes extremely cumbersome.

[0024] Aspects of the present disclosure provide methods and systems to streamline the content access process and engage end users. To that end, the example access system provides a new technique for saving and accessing content within existing ECM solutions without modifying the existing infonnation architecture of the ECM solution or ECM platform. The access system and method are configured to create one or more solution profiles that include one or more customizable location or content items. The items may be tailored to the end user, thereby allowing users to save and access content they use frequently in a more efficient manner.

[0025] The access system as described herein may find utility in various applications. In one example, the access system is utilized in an ECM platform by organizations to manage, create, store, access and collaborate on organizational data. Alternatively, individual users can utilize the access system to manage and share their personal data. These applications are merely illustrative and the access system may be utilized in numerous other applications.

[0026] FIG. 1 is a block diagram of an ECM platform 100 where an access system 102 according to the present disclosure is implemented. The ECM platform 100 includes the access system 102 installed and executing on a server computer on a network 120 or on the user devices 104a, 104b, 104c ... 104n (collectively referred to as user devices 104). The network 120 interconnects and operatively couples the user devices 104 to the access system 102. Further, one or more users 108a, 108b... 108c (collectively referred to as users 108) operate the user devices 104. The ECM platform 100 further includes one or more storage devices 1 10, servers 1 12, and/or application platforms 1 14 operatively coupled to the network 120 and/or the user devices 104. Examples of the ECM platform 100 include a Microsoft* Office 365 platfonn or a Microsoft* Azure Platfonn amongst others.

[0027] The user devices 104 can be any electronic device that is capable of exchanging data over the network 120. Examples of such electronic devices include personal computers, laptops, tablets, mobile phones or other handheld devices. The user devices 104 are also capable of executing one or more client applications such as Microsoft Outlook^®, Windows File Explorer^®, Microsoft Office^®, Adobe Acrobat^®, web browsers or mobile applications. Moreover, as referred to in the present disclosure, a 'user' 108 of the platform 100 includes an individual person or an organization including multiple persons. In addition, the storage devices 110 include central repository servers on the network 120, such as shared databases maintained by one or more people or an organization.

[0028] Users 108 typically store and access data, such as text files, emails, videos, images, program files, system files, or executable files on one or more of these storage devices 1 10. Collectively, such data in any known format is termed as 'content' throughout this disclosure. Over time, as users continue to create and store content, and as the platfonn expands for multiple business solutions it becomes gargantuan. Often, users face difficulty in correctly identifying the locations of content when required. To aid users 108 in efficiently accessing and saving content on the ECM platfonn 100, the access system 102 is employed. The access system 102 enables users 108 to view, search, access, and potentially share content from within the ECM platfonn 100 in a fast and efficient manner.

[0029] To that end, the access system 102 creates and publishes profiles on the central repository 120. The created profiles include one or more location and/or content items. Based on user authorization, the created profiles can be retrieved from the central repository 120 onto the user devices 104. Subsequently, users 108 can access or save locations and content on the ECM platform 100 by selecting any one of the available items in the profile. Detailed functionality of the access system 102 will be described with reference to FIGS. 2-7.

[0030] As described above, the access system 102 can be executed on the network 120 (e.g., by the servers 1 12) or on the user devices 104. In case the access system 102 is executed on the network 120, the access system 102 can be retrieved from any user device 104 that is capable of connecting to the network 120, irrespective of the configuration of the user device 104. However, because the access system 102 is executed through the network 120, it is inaccessible without a network connection. In other implementations, instances of the access system 102 can be installed on each of the user devices 104. In this case, users can access the system 102 without a network connection. However, the access system 102 is inaccessible from user devices 104 on which the access system 120 is not installed.

[0031] Alternately, the access system 102 can be executed on one or more of the user devices 104 and on the network 120. In such a case, the access 102 can be opened from the network 120 when the user device 104 is connected to the network 120 and from the user device itself, when the user device 104 is disconnected from the network 120. Based on individual requirements, any of these computing network implementations may be selected.

[0032] Figs. 2A and 2B depict a general-purpose computer system 200, upon which the various arrangements described can be practiced. For example, one of the user devices 104 and/or one of the servers 1 12 may be in the form of the computer system 200. As seen in Fig. 2 A, the computer system 200 includes a computer module 201 ; input devices such as a keyboard 202, a mouse pointer device 203, a scanner 226, a camera 227, and a microphone 280; and output devices including a printer 215, a display device 214 and loudspeakers 217. A network interface 216 may be used by the computer module 201 for communicating to and from the communications network 120 via a connection 221. The communications network 120 may be a private network, such as a local area network (LAN) or a virtual private network (VPN), hosted by a single organization; a community network, such as a wide area network (WAN), hosted by multiple organizations; a public network, such as the Internet; or a hybrid combination of these networks. Furthermore, the connection 221 may be wired or wireless means. Wired connections include Ethernet cables, LAN cables, and the like; while, wireless connections include Bluetooth^®, 802.1 1 standard WLAN, Wi-Fi and the like.

[0033] The computer module 201 typically includes at least one processor unit 205, and a memory 206. For example, the memoiy 206 may have semiconductor random access memory (RAM) and semiconductor read only memory (ROM). The computer module 201 also includes a number of input/output (I/O) interfaces including: an audio-video interface 207 that couples to the video display 214, loudspeakers 217 and microphone 280; an I/O interface 213 that couples to the keyboard 202, mouse 203, scanner 226, camera 227 and optionally a joystick or other human interface device (not illustrated); and an interface 208 for the printer 215.

[0034] The I/O interfaces 208 and 213 may afford either or both of serial and parallel connectivity, the former typically being implemented according to the Universal Serial Bus (USB) standards and having corresponding USB connectors (not illustrated). Storage devices 209 are provided and typically include a hard disk drive (HDD) 210. Other storage devices such as a floppy disk drive and a magnetic tape drive (not illustrated) may also be used. An optical disk drive 212 is typically provided to act as a non-volatile source of data. Portable memory devices, such optical disks (e.g., CD-ROM, DVD, Blu-ray Disc^IM), USB-RAM, portable, external hard drives, and floppy disks, for example, may be used as appropriate sources of data to the system 200.

[0035] The components 205 to 213 of the computer module 201 typically communicate via an interconnected bus 204 and in a manner that results in a conventional mode of operation of the computer system 200 known to those in the relevant art. For example, the processor 205 is coupled to the system bus 204 using a connection 218. Likewise, the memory 206 and optical disk drive 212 are coupled to the system bus 204 by connections 219. Examples of computers on which the described arrangements can be practiced include IBM -PC's and compatibles, Sun Sparcstations, Apple Mac™ or a like computer systems.

[0036] The method of FIG. 6 may be implemented using the computer system 200 wherein the processes of Fig. 3, to be described, may be implemented as one or more software application programs 233 executable within the computer system 200. In particular, the steps of the method of FIG. 6 may be effected by instructions 231 (see Fig. 2B) in the software 233 that are carried out within the computer system 200. The software instructions 231 may be formed as one or more code modules, each for performing one or more particular tasks. The software may also be divided into two separate parts, in which a first part and the corresponding code modules performs the content access methods and a second part and the corresponding code modules manage a user interface 304 between the first part and the user.

[0037] The software may be stored in a computer readable medium, including the storage devices described below, for example. The software is loaded into the computer system 200 from the computer readable medium, and then executed by the computer system 200. A computer readable medium having such software or computer program recorded on the computer readable medium is a computer program product. The use of the computer program product in the computer system 200 preferably effects an advantageous apparatus for accessing content in the ECM platform 100. [0038] The software 233 is typically stored in the HDD 210 or the memory 206. The software is loaded into the computer system 200 from a computer readable medium, and executed by the computer system 200. Thus, for example, the software 233 may be stored on an optically readable disk storage medium (e.g., CD-ROM) 225 that is read by the optical disk drive 212. A computer readable medium having such software or computer program recorded on it is a computer program product. The use of the computer program product in the computer system 200 preferably effects an apparatus for accessing content in the ECM platform 100.

[0039] In some instances, the application programs 233 may be supplied to the user encoded on one or more CD-ROMs 225 and read via the corresponding drive 212, or alternatively may be read by the user from the network 120. Still further, the software can also be loaded into the computer system 200 from other computer readable media. Computer readable storage media refers to any non-transitory tangible storage medium that provides recorded instructions and/or data to the computer system 200 for execution and/or processing. Examples of such storage media include floppy disks, magnetic tape, CD-ROM, DVD, Blu-ray^IM Disc, a hard disk drive, a ROM or integrated circuit, USB memory, a magneto-optical disk, or a computer readable card such as a PCMCIA card and the like, whether or not such devices are internal or external of the computer module 201. Examples of transitory or non-tangible computer readable transmission media that may also participate in the provision of software, application programs, instructions and/or data to the computer module 201 include radio or infra-red transmission channels as well as a network connection to another computer or networked device, and the Internet or Intranets including e-mail transmissions and information recorded on Websites and the like.

[0040] The second part of the application programs 233 and the corresponding code modules mentioned above may be executed to implement one or more graphical user interfaces (GUIs) 304 to be rendered or otherwise represented upon the display 214. Through manipulation of typically the keyboard 202 and the mouse 203, a user of the computer system 200 and the application may manipulate the interface in a functionally adaptable manner to provide controlling commands and/or input to the applications associated with the GUI(s). Other forms of functionally adaptable user interfaces 304 may also be implemented, such as an audio interface utilizing speech prompts output via the loudspeakers 217 and user voice commands input via the microphone 280.

[0041] Fig. 2B is a detailed schematic block diagram of the processor 205 and a "memory" 234. The memory 234 represents a logical aggregation of all the memory modules (including the HDD 210 and semiconductor memory 206) that can be accessed by the computer module 201 in Fig. 2A. |0042] When the computer module 201 is initially powered up, an operating system 253 is loaded into the RAM memory 206, upon which the operating system 253 commences operation. The operating system 253 is a system level application, executable by the processor 205, to fulfil various high level functions, including processor management, memory management, device management, storage management, software application interface, and generic user interface.

[0043] The operating system 253 manages the memory 234 (209, 206) to ensure that each process or application running on the computer module 201 has sufficient memory in which to execute without colliding with memory allocated to another process. Furthermore, the different types of memory available in the system 200 of Fig. 2A must be used properly so that each process can run effectively. Accordingly, the aggregated memory 234 is not intended to illustrate how particular segments of memory are allocated (unless otherwise stated), but rather to provide a general view of the memory accessible by the computer system 200 and how such is used.

[0044] As shown in Fig. 2B, the processor 205 includes a number of functional modules including a control unit 239, an arithmetic logic unit (ALU) 240, and a local or internal memory 248, sometimes called a cache memory. One or more internal busses 241 functionally interconnect these functional modules. The processor 205 typically also has one or more interfaces 242 for communicating with external devices via the system bus 204, using a connection 218. The memory 234 is coupled to the bus 204 using a connection 219.

[0045] The application program 233 includes a sequence of instructions 231 that may include conditional branch and loop instructions. The program 233 may also include data 232, which is used in execution of the program 233. The instructions 231 and the data 232 are stored in memory locations 228, 229, 230 and 235, 236, 237, respectively. Depending upon the relative size of the instructions 231 and the memory locations 228-230, a particular instruction may be stored in a single memory location as depicted by the instruction shown in the memory location 230. Alternately, an instruction may be segmented into a number of parts each of which is stored in a separate memory location, as depicted by the instruction segments shown in the memory locations 228 and 229.

[0046] In general, the processor 205 is given a set of instructions, which are executed therein. The processor 205 waits for a subsequent input, to which the processor 205 reacts to by executing another set of instructions. Each input may be provided from one or more of a number of sources, including data generated by one or more of the input devices 202, 203, data received from an external source across one of the networks 120, data retrieved from one of the storage devices 206, 209 or data retrieved from a storage medium 225 inserted into the corresponding reader 212, all depicted in Fig. 2A. The execution of a set of the instructions may in some cases result in output of data. Execution may also involve storing data or variables to the memory 234.

[0047] The disclosed arrangements use input variables 254, which are stored in the memory 234 in corresponding memory locations 255, 256, 257. The arrangements produce output variables 261, which are stored in the memory 234 in corresponding memory locations 262, 263, 264. Intermediate variables 258 may be stored in memory locations 259, 260, 266 and 267.

[0048] FIG. 3 is a block diagram of the access system 102. The system 102 includes a profile module 302 to create and publish one or more profiles, a user interface 304 configured to display the profiles on a client application/device 310 (e.g., Microsoft Outlook*, Windows File Explorer^®, Microsoft Office*, Adobe Acrobat*, web browsers or mobile applications), and an input/output module 306 configured to provide a selection input to the ECM platform, receive results associated with the selection input, and display the results on the client application 310. The access system 102 is also operatively coupled to a storage device 1 10, such as a central repository, and a search engine 312. Further, the access system 102 is coupled to the user devices 104 through a suitable network 120 or is actively installed on the user devices 104.

[0049] Content saved to the ECM platform 100 is stored with a degree of relationship to the other content within the platform 100. Moreover, content is saved on the ECM platform 100 within an instance of an artefact. An artefact is one of the 'building blocks' or design components available in a specific ECM Technology Platform. There may be a number of artefacts available and each may have its own characteristics, capabilities and implicit relationship to other artefacts. For example, in SharePoint* examples of artefacts include Site Collections, Sites, Libraries, Lists, Folders and Document Sets. An instance of an artefact that allows content to be stored is referred to as a "Location" within the ECM platform 100. Typical ECM solutions provide end users three primary methods of saving and accessing content to or from respective locations. One such method involves browsing a physical structure (normally hierarchical) until the desired location is found, the second method includes saving content to a generic location for subsequent routing by a workflow process in the background and the third method is a general, non-solution specific search.

[0050] The access system 102 of the present disclosure provides a new method for end users to efficiently save and access content from locations within the ECM platform 100 without modifying the existing ECM solutions or ECM platform. Moreover, the disclosed access method can be made available for end users within the client applications 310, which may include, but not limited to Microsoft Outlook*, Windows File Explorer*, Microsoft Office*, Adobe Acrobat*, web browsers or mobile applications. [0051 ] The access system 102 is described in this disclosure in relation to a SharePoint* technology platform. However, the access system 102 could just as easily be implemented on other technology platforms without departing from the scope of the present disclosure.

[0052] The profile module 302 creates one or more profiles, such as solution profiles. The solution profiles may alternatively be referred to as corporate profiles. Each solution profile describes a solution to be made available to one or more user groups. Particularly, the profile can include one or more location items and/or content items. Location items are items that return locations in which content can be stored, while content items are items that return content such as documents, files, or lists, when selected.

[0053] Although each profile generally represents a specific ECM solution, this is not a requirement. For instance, a profile module 302 may create multiple profiles representing the same ECM solution on the ECM platform 100 or one profile representing multiple ECM solutions on the ECM platform 100. The decision about creating profiles may be influenced by factors such as security requirements and the geographic location of both the solution and the end users accessing the ECM solution on the ECM platform. Each ECM solution described by a profile may have vastly different information architectures. For example, in a technology platform such as SharePoint*, a legal case management solution could span multiple site collections while another implementation may be encompassed within a single document library.

[0054] In one implementation, the profile is implemented in the form of an Extensible Markup Language (XML) file describing an existing ECM solution or solutions on an ECM platform. However, it will be understood that in other implementations, the profile can be written using any other suitable computer language or code without departing from the scope of the present disclosure.

[0055] As described previously, each profile may include a definition of one or more location items. For example, the profile may include the definition of one or more search locations, shortcut locations (alternatively referred to as browse locations), and/or central register locations. Search locations provide a search based mechanism for presenting locations to save and access content within the ECM platform 100, and shortcut locations provide a mechanism to use hierarchical structures for browsing an ECM solution physical structure and selecting a location to save and access content. The central register location provides a central list containing items with associated metadata describing locations (e.g. Legal Matters, Projects). In addition to the metadata describing the location (e.g. project no. Project name, description, team members, owner, budget, etc), a URL to the actual location of the described item is also provided. |0056] Similarly, the profiles may also include definitions of one or more content items. For example, the profile may include the definition of search content items, shortcut content items, and/or intelligent content items. A search content item provides a search based mechanism for retrieving and presenting content within an EC solution, while the shortcut content item provides a mechanism to use a hierarchical structure for browsing content within in the ECM platform content. These content item (search content and shortcut content ) are similar to the search location and shortcut location items, but provide documents/files instead of locations as output. The intelligent content item provides content that might be most relevant to a user based on the user's activity on the ECM platform 100 or in a client application 310. In the case of SharePoint®, the intelligence can be provided by using the Microsoft Office Graph® technology to surface content relevant a specific user. Moreover, each profile may include authorization information to control access to the profiles and definitions of one or more behaviours and/or actions.

[0057] According to one implementation, the profile module 302 utilizes a software development kit (SDK) with a full application programming interface (API) to create the profiles, location and content items, authorization information, behaviours and actions. Additionally, the profile module 302 may utilize the user interface 304 to provide IT administrators with an easy way of creating the profiles and setting authorization information associated with the profiles. Alternatively, the SDK may be utilized independent of the user interface 304, thereby enabling the creation of profile module 302 and associated location and content items. The profile module 302 is further configured to save/publish the profiles to the central repository 1 10.

[0058] From the central repository 1 10, users 108 may retrieve the profiles through one or more client applications 310. Once the user 108 initiates a request for a profile, the identification of the user 108 is compared with the authorization information associated with the profile to determine whether the user is permitted to access the profile. If the comparison is successful, the user 108 is allowed to retrieve the profile. In one aspect, the user can retrieve one or more profiles from the central repository 120 based on the user's identification. Alternatively, profiles pertinent to the user may be automatically made available when a user enters their credentials. The access module 302 may also periodically check if any new or updated profiles are available for the user and retrieve such profiles, when detected. Once a profile is displayed on the client application 310, users 108 have a new method for saving and accessing ECM content efficiently from their application or device.

[0059] As described previously, the search location provides a search-based mechanism for presenting locations to save and access content within an ECM Solution. Each profile may contain an XML definition for one or more search locations. This XML definition forms part of the profile's XML Structure. The definition of the search location includes a location name, and a location description.

[0060] Moreover, the definition of the search location may include an input form, which typically includes metadata labels, metadata values and input types. For example, the input fonn may include "project number" as metadata label and metadata values, and "numeric" as the input type. Alternatively, the input form may include "project name" as the metadata label and the metadata values, and "text" as input type. Moreover, the input form may define more than one metadata label and value pairs. However, the two or more metadata label/value pairs are combined in an AND fashion in the input fonn. In alternate arrangement, the two or more metadata label/value pairs may be combined in an OR fashion.

[0061] Furthermore, initial defaul t values can be defined for one or more of the metadata label/value(s) pairs. The profile module 302 may set or change the default values based on properties of the data, such as content name (e.g., email subject), source of the data (e.g., Payroll or a CRM System), or real environment informati on such as the current user name, date/time, current user profile information such as current user 108 manager, department, geographic location, etc. The profile module 302 may also utilize the properties of the data to modify the base query.

[0062] The input form is optional. If specified, in the search location definition, an XML definition of the input form is saved as part of the search location definition. Further, for some specific technology platforms, an interface, such as a drop down menu, is provided to select available metadata Label/value(s) pairs. If the input form metadata label/value(s) is defined, the client application 310 that has access to the profile has the information required to present the interface to an end user to enter/select values and submit the values as part of a search query.

[0063] In addition to the input form, the search location definition may include a reference to use a predefined search and search scope on the technology platform. For the SharePoint* ECM Platform, this predefined search and search scope is known as a Result Source.

[0064] In addition, the search location definition may include definition of a base search query. A base search query is a free text area for entering a valid search query. The base search query may define the scope of the search location, Boolean conditions and other text/values to search. A combination of the result source, base search query and input form is termed as a "final query".

[0065] In some implementations, the search location definition also includes an option to flag automatic execution of the final query. If the automatic execution is set to yes, the final query is automatically executed and resulting locations are presented when a user selects the search location to save or access content. In this case, if the input form has been defined, default values of the metadata label/value(s) pairs are used along with the result source and base search query. Once the final query is automatically executed, the profile module 302 may also be configured to refine or modify the results prior to displaying them on the user interface 306. The user interface 304 can also provide an option to subsequently modify the input form search values or re-execute the search location.

[0066] Accordingly, on a SharePoint^® ECM Platform with a profile for a case management solution, one or more search locations can be created as indicated in table 1.

Table 1 : Examples of Search Location Definitions

[0067] To execute a search location according to the final query, implicit and explicit metadata of the physical structure is utilized. Each artefact within the ECM platform 100 includes both implicit and explicit metadata describing the artefact. Implicit metadata describes the implicit capabilities of an artefact and the relationship of an artefact to other artefacts. For example, a library artefact may include implicit metadata such as which Site the library belongs to, the folders or document sets contained within the library, type of artefact, etc. Explicit metadata on the other hand depends on the technology platform used and it typically includes business specific metadata. For example, in case of a folder, the explicit metadata may include the name of the folder, creation date, last modified date, author and solution specific metadata including project name, status, regions, etc.

[0068] The ability and the extent to which explicit metadata can be applied to artefacts is dependent on the technology platform. It will be understood that the technology platfonn used for the ECM platform 100 and the available infrastructure and implementation of an environment determine which implicit and explicit metadata is indexed and available through the execution of a final query. Moreover, the technology platform determines the syntax requirements and capabilities for a final query.

[0069] Generally, the input/output module 306 provides the search location definition of the search location selected by the user to the search engine 312 of the ECM platform 100. The search engine 312 then searches the ECM platform 100 based on the definition of the search location and determines the artefacts relevant to the final query.

[0070] As ECM platforms are implemented organization-wide, often confidential, private, privileged, or internal documents and sites may be present on the ECM platform 100. It is important that only authorized users be allowed to access such documents. Accordingly, the ECM platform 100 is configured to determine whether the user 108 is authorized to access the relevant artefacts. In one implementation, the ECM platform 100 returns only the search results (artefacts) that the end user has access to. Alternatively, the ECM platform 100 can be configured to return all the search results, but the end user may not be able to access or save content in the locations that the end user is not authorized to access.

[0071] The ECM platform 100 returns the results in an XML structure to the input/output module 306. The input/output module 306, in turn, displays the results on the user interface 304 based on the characteristics of the client application/device 310 and presentation and behaviour rules defined in the profile. Subsequently, the user 108 can select a location or a result can be automatically selected in the case that a single result (location) is presented.

[0072] FIG. 4 is a screenshot illustrating an example final query result 400 that is utilized to save content on the EMS platform 100. As illustrated in Fig. 4, the input form query includes the fields "matter number" and "client name." The base query for this search location is "active matters" and the scope of the search is limited to legal case management on the ECM platform. The end user is thus allowed to enter a matter number and/or a client name. The input/output module 306 subsequently combines the user input with the optional result source and base query to generate a final query. This final query is provided to the search engine 312, which searches the active cases in the legal case management sites for the particular matter number and/or client name within the ECM platform 100. The search engine 312 subsequently provides the results to the input/output module 306, which displays the results in the user interface 304 as illustrated in FIG. 4. A user can select any of the displayed locations to save data. Alternatively, the user can further expand a presented location to desired location. The search location can also be used to access content from the ECM platform 100. In that case, the search engine 306 displays all the relevant locations on the user interface 304 and the end user can select and if required further expand the locations to select the required content.

[0073] As described above, the shortcut location provides a mechanism to use a hierarchical structure for browsing the ECM platform and selecting a location to save and access content. Each profile may include the XML definition for one or more shortcut locations. This XML definition fonns part of the profile's XML Structure. The shortcut location definition includes a shortcut location name, a shortcut location description, and a fixed starting location. In SharePoint* the starting location is a URL, while in Windows* File Explorer, the starting location is a directory path.

[0074] In addition, the XML definition of the shortcut location may include options such as view/report name. Depending on the technology platfonn, there may be a predefined view/report, which has been created within the ECM solution or ECM platfonn. In SharePoint⁸, a view can be defined for a library artefact that shows the content locations within the ECM Solution, such as folders and document sets.

[0075] If an artefact in the ECM platform 100 allows for a view/report to be defined, the view/report's name can be added to the XML definition of the shortcut location. Accordingly, the shortcut location can use the view/report in the client application 3 10 to restrict the artefacts displayed in the browse interface to those available in the view/report.

[0076] Example shortcut locations for a solution profile for a case management system are depicted in table 2.

Table 2: Examples of Shortcut location Definitions [0077] When the user 108 selects a shortcut location from the user interface 304, the definition of the shortcut location is retrieved by the input/output module 306 and provided to the ECM platform 100. The ECM platform 100 uses the URL or directory path defined in the shortcut location to retrieve the hierarchical structure of the physical structure defined by the shortcut location. Further, if a view/report is selected, the ECM platform 100 may restrict the artefacts in the hierarchical structure to only those present in the view/report. Moreover, the ECM platform 100 is configured to determine whether the user has access to all the artefacts in the hierarchical structure and remove the artefacts that the user is not allowed to access. The trimmed resulting hierarchical structure is then provided to the input/output module 306 in an XML structure and the input/output module 306 displays the resulting structure in the user interface 304 based on the settings of the client application 310.

[0078] The central register location provides the ability to reference a central list containing items describing locations across the ECM platform 100. Each item in the central register includes metadata describing the locations (e.g. , project no. project name, description, team members, owner, budget, etc.), and a URL to the actual location. In one arrangement, the URL location can also be extended with sub-locations. For example, if an item in the central list, 'Project/Legal Matter 000777' has sub locations/folders (such as library 1 , Hbrary2, etc.), the central register location item allows dynamic additional URLs to be derived and provided for each of these sub-locations. It will be appreciated that a central list referenced by the central register location item may contain many list items. Each list item describes (via metadata) a location (reference via the URL provided).

[0079] The central register location item can be defined to filter locations based on the described metadata and to personalise the displayed locations based on the user. In a SharePoint* ECM Platform, a view/report of the central list can be referenced, thereby providing the ability to filter the list of items based on the available metadata. For example, the central register may be filtered to display only the items where the project budget is greater the $300,000 AND the project number starts with 5. Alternatively, the central register may be filtered by defining a specific filter query. For instance, in the case of SharePoint*, the central register may be filtered by defining a CAML (Categorical Abstract Machine Language) query.

[0080] In addition to filtering and personalizing the central list at definition time, the central register location item may also allow real time filtering and personalisation based on the current user 108. For example, a user may be allowed to filter the list of items in the central list to only show items where the current user 108 is a member of a 'Person/Group' metadata column. Accordingly, a user may be able to view only the projects starting with project number 5 where the budget is over $300,00 and the user is a team member, for instance. Other Environment variables such as time, user profile information (e.g. department, manager, geographic location, etc.) may also be used to implement dynamic filtering.

[0081] Example central register locations for a solution profile for a case management system are depicted in table 3.

Table 3: Examples of Central Register Location Item Definitions

[0082] In addition to the location items, the profile may also allow a user to define content items such as search content and insight content. The search content item allows a user to define a search query to return content. In one arrangement, the search content item removes all locations such as sites, libraries, and folders and only presents content such as documents, videos, .exe files, etc. This item is similar to the search location item with one difference being the type of results generated by the two items - while the search location item generates search results such as folders, libraries or sites, the search content item displays content such as documents, emails, videos, etc. Accordingly, using the search content option, a user may restrict the search scope to active cases, acti ve cases associated with the user, emails related to active cases, or word documents authored by the user, and so on. In one arrangement, the search content item can reference predefined searches and scoped content. These are known as results sources on the SharePoint* ECM Platform.

[0083] Example search content items for a solution profile for a case management system are depicted in table 4.

Table 4: Examples of Search Content Item Definitions

[0084] The intelligent content item uses the ECM platform's intelligence (if available) on content with respect to the current user, their actions, and association to other personnel. On the SharePoinf⁸ ECM platform, this intelligence is uncovered by Office Graph®. When the intelligent content item is selected, content relevant to the user may be presented based on intelligence/insights ascertained by the underlying intelligence technology and queried within the intelligent content item. For example, a user may be presented with legal case documents and a presentation discussed in a recent meeting the user attended. |0085] As described above, the profiles may also include definitions of one or more behaviours or actions. Behaviours may include popup prompts/windows that allow users to access or save data more effectively or integrate workflow processes with the ECM platform 100. For instance, a particular behaviour may display a minimal navigation tree in the user interface 304 to reduce clutter and remove artefacts that are not pertinent to the process that is invoked. Actions, on the other hand, refer to prompts or dialogue boxes that allow users to initiate a workflow action once a process (e.g., saving) is completed. One example of an action in a legal case management system may include a prompt to start an approval action workflow when an MS Word or PDF file is saved. Actions are typically business-related, allowing businesses to integrate one or more of their workflow processes into the ECM platform 100. Another example of an action includes automatically sending email notifications to concerned team members when a file is saved or modified.

[0086] The availability of behaviours and actions within the profile definition depends on the situation in which the location and/or content items are utilized. In this disclosure, these situations are termed as contexts. The context includes the type of user device (e.g., computer, tablet, phone), type of operating system (e.g., Windows⁴, iOS*, Android*), the type of client application (e.g., Microsoft Outlook*, MS Word*, Adobe Acrobat*, Windows Explorer), end user's authorization, and the process being performed (e.g., accessing or saving).

[0087] The actual behaviours and actions may vary in different contexts and may also change overtime. Moreover, the number of behaviours and actions may also vary over time or in different contexts. If defined in the profile, these behaviours and actions can be activated if a particular location and/or content item is selected. Table 3 illustrates examples of contexts and example behaviours and/or actions that can be available for the contexts.

Context Behaviour Behaviour 2 Behaviour 3 Action 1 - Action 2 - 1 - Prompt - Show - Show Start action start action with Save Results minimal approval email to SP Window navigation workflow notification Window tree workflow

Context 1 Yes No Yes Yes Yes

Device: All

Applications: All

Authorization: All

Process: Save

Context 1 No No No Yes Yes

Device: iOS-iPad

Applications: All

Authorization: All

Process: Save Context 1 N/A N/A Yes N/A N/A

Device: All

Applications: MS

Outlook

Authorization: All

Process: View

Table 3: Example contexts and associated example behaviours and actions

[0088] Typically to save content to the ECM platform 100, the user either browses all the hierarchical structures in the ECM platform to identify the correct location or saves content to a generic location for subsequent routing by a workflow process in the background. When saving content to a generic location for subsequent routing by a workflow process in the background, the user has to input the correct identification details such as location name to be able to save the content to that location. However, often, the end user may not remember the correct location name to save of subsequently retrieve content. In such a case the end user can only rely on the cumbersome process of browsing the entire hierarchical structure of the ECM platform to identify the correct location.

[0089] However, by utilizing the access system 102 of the present disclosure, the end user can be presented with direct access to a representation of one or more ECM solutions on the ECM platform through one or more solution profiles. Each profile allows the user to choose a location and/or content item (as defined in the profile definition) for saving and accessing content. Furthermore, the location and/or content items refine the locations presented to the user based on the definitions of the items. For instance, the central register location item may present only acti ve cases in which the user is a team member, or cases worked on in the last 2 weeks, or cases for which a deadline is approaching, etc., thus, considerably reducing the search/browse time required to identify the correct location for accessing or saving content. It will be understood that these location and content items are not static. Instead, the locations or content displayed by these items is dynamically updated (without the need to change the published profile definition).

[0090] FIG. 5 is a screenshot of a client application 310 with example solution profiles - legal matters 502, and project management 504. The legal matters 502 profile is expanded to depict various exemplary location and content items that may be defined within the legal matters profile. Specifically, these content and location items are - shortcut content 506 (e.g., "Legal Resources"), search content 508 (e.g., My Files (this week)"), shortcut location 510 (e.g., "clients"), central register location 512 ( "my open matters") and search location 5 14 (e.g., "my open matters" and "Matters opened this week"). By selecting any of these location or content items, a user may easily find a document or a specific location where the user wishes to save data. For instance, the user may wish to access a presentation that he/she made yesterday. In this case, the user may select the "My Files (this week)" search content item, which will show all the files created/modified by the user this week. The user can then easily identify and open the required presentation. Alternatively, if the user wishes to access all the files of a recent project/matter, the user can select the "My Open Matters" central register location 512 or the "My Open Matters" location search 514, which will present a list of all active matters/projects where the user is a team member. The user can then browse all the files in the required project/matter or save a file under the required project number.

[0091 ] Similarly, FIG. 8 is a screenshot of a client application 310 with example solution profiles - Legal Matters and Project Management. The figure also illustrates the search location items (e.g., "Matters opened this week" and "My open matters") and the search content item (e.g., "My Files (this week)" of the Legal Matters solution profile. Furthermore, the figure illustrates the content items 804 retrieved when the 'My Files (this week)' search content item 802 is selected.

[0092] FIGS. 6 and 7 are flowcharts illustrating methods 600 and 700 for accessing or saving content on an ECM platform. These methods 600, 700 will be described with reference to FIGS. 1-5. In one arrangement, the steps of the methods 600, 700 may be implemented as one or more software code modules of the software application program 233 resident in the ROM 260 and being controlled in execution by the processor 205 of the system 200. As described above, one of the user devices 104 and/or one of the servers 1 12 may be in the form of the computer system 200. Moreover, one or more method steps may be deleted, added, or reordered without departing from the scope of the present disclosure.

[0093] The method 600 begins at step 602 where one or more profiles are created. The profiles include definitions of one or more search locations and/or shortcut locations. The search locations provide a search based mechanism for presenting locations within the ECM platform 100 and the shortcut location provides a mechanism to use a hierarchical structure for browsing physical structure of the ECM platform 100. In one implementation, the profile module 302, under execution of the processor 205, utilizes an SDK with API to create the profiles having an XML construct. The created profiles may be stored in the storage module 209. Alternatively, the profile module 302 may utilize the user interface 304 to allow IT administrators to create profiles using the SDK.

[0094] At step 604, authorization information is created and applied to control access to the profiles. To that end, the profile module 302 may automatically create the authorization information or allow IT administrators to create the authorization information using the SDK. In one implementation, the authorization information is stored within the profiles. However, in other implementations, the authorization information can be set directly in the central repository 120. In this case, each profile is stored as an item within a SharePoint* list. Appropriate user and/or group level permissions are specified for each profile based on the definition of the profile. Any known technique for such security settings or mechanism to define permissions to restrict profiles can be utilized without departing from the scope of the present di sclosure.

[0095] Subsequently, at step 606, the profiles are published, under execution of the processor 105, to the central repository servers on the network 120. Next (step 608), the profile is displayed along with the one or more search and/or shortcut locations through the user interface 304 by a client application/device 310 associated with an end user. The user interface 304 may be displayed to the end user on the display device 214. If the user wishes to access the profiles from the central repository 120, the access system 102 performs a security check and/or check of profile membership to determine whether the user is authorized to consume the requested profile(s). If the access system 102 determines that the user is allowed access to consume the profile, the profile is displayed by the client applications/devices 310 associated with the user. Otherwise, the user is not allowed access to consume the profile. In another implementation, when the access system 102 is installed and executed on the ECM platfonn 100 or on the client applications 310, the access system 102 automatically compares the user's credentials with the authorization information and/or membership of the profiles to determine whether the user is authorized to access and consume the profiles. On successful comparison, the access module 102 automatically retrieves the profiles and displays them on the client application/device 310.

[0096] When the user wishes to access or save content on the ECM platfonn, the user may select at least one search location or shortcut location associated with the profile. Moreover, in case the user selects a search location that includes a search input form, the user can also input values for refining and executing the search (e.g., using the input form). The input fonn is subsequently combined with an associated base query to form the final query.

[0097] Subsequently, under execution of the processor 205, the input/output module 306 retrieves the user selection and determines whether the selected item is a search location or a browse location at step 609. In case search location is selected, the input/output module 306 provides the selection along with the associated definitions to the search engine 312 at step 610. Alternatively, the method proceeds to step 613.

[0098] Next (step 612), the search engine 312 obtains results (artefacts) associated with the selected search location based on the definition of the search location item. It will be understood that the results may be obtained in response to a final query associated with the search location. For example, in case the user selection was "search location 1" from table 1, the results could include a list of all artefacts related to the case number input by the user. |0099] In case a shortcut location item is selected, the input/output module 306 utilizes the URL or directory path defined in the shortcut location to retrieve the hierarchical structure of the physical structure defined by the shortcut location from the central repository 1 10 (at step 613). Further, if a view/report is selected, the input/output module 306 may restrict the artefacts in the hierarchical structure to only those present in the view/report.

[00100] Subsequently, the input/output module 306 trims the results based on access rights of the end user to the obtained results. To that end, the input/output module 306 associated with the ECM platform 100 determines whether the user is authorized to access all the obtained results and removes the results that the user does not have access to.

[00101] Lastly (at step 616), the trimmed results are displayed on the user interface 304.

As described above, the user interface 304 may be display on the display device 214. The user can further refine the results or select one or more locations from the displayed result locations to access content from or save content to.

[00102] If behaviours and actions are defined for the particular search or shortcut location, the client application 310 retrieves the XML definitions of the behaviour and/or action and initiations the behaviour/action either during or after the save or access process is completed. For instance, a behaviour that prompts users to enter additional metadata for a file is invoked when the file is being saved. Alternatively, an action prompting the user to begin a workflow process can be invoked once the file is saved to the EC platform 100.

[00103] Method 700 begins at step 702, where one or more profiles are created. The profiles include definitions of one or more location and/or content items. The location items provide a mechanism for presenting locations pertinent to the user within the ECM platform 100 and the content items provide a mechanism for presenting content pertinent to the user. Examples of location items include search locations, shortcut locations, and central register locations, while examples of content items include search content, shortcut content, and intelligent content. In one implementation, the profile module 302, under execution of the processor 205, utilizes an SDK with API to create the profiles having an XML construct. The created profiles may be stored in the storage module 209. Alternatively, the profile module 302 may utilize the user interface 304 to allow IT administrators to create profiles using the SDK.

[00104] At step 704, authorization information and/or membership information is created and applied to control access to the profiles. To that end, the profile module 302 may automatically create the authorization information or allow IT administrators to create the authorization information using the SDK. In one implementation, the authorization information is stored within the profiles. However, in other implementations, the authorization information can be set directly in the central repository 120. In this case, each profile is stored as an item within a SharePoint* list. Appropriate user and/or group level security can be set and further membership selection can be applied for each profile based on the definition of the profile. Any known technique for such security or membership settings can be utilized without departing from the scope of the present disclosure.

[00105] Subsequently, at step 706, the profiles are published, under execution of the processor 105, to the central repository servers on the network 120. Next (step 708), the profile is displayed along with the one or more location and/or content items through the user interface 304 by a client application device 310 associated with an end user. The user interface 304 may be displayed to the end user on the display device 214. If the user wishes to access the profiles from the central repository 120, the access system 102 performs a security check and membership check to determine whether the user is authorized to access and consume the requested profile(s). If the access system 102 determines that the user is allowed access and has membership to consume the profile, the profile is displayed by the client applications/devices 310 associated with the user. Otherwise, the user is not allowed access to the profile. In another implementation, when the access system 102 is installed and executed on the ECM platform 100 or on the client applications 310, the access system 102 automatically compares the user's credentials with the authorization information of the profiles to determine whether the user is authorized to access and consume the profiles. On successful comparison, the access module 102 automatically retrieves the profiles and displays them on the client application/device 310.

[00106] When the user wishes to access or save content on the ECM platform, the user may select at least one location or content item associated with the profile. Moreover, in case the user selects a location or content item that includes a search input form, the user can also input values for executing the search (e.g., using the input form). The input form is subsequently combined with an associated base query to form the final query.

[00107] Subsequently, under execution of the processor 205, the input/output module 306 retrieves the user selection and determines whether the selection is a search based item, such as search location or search content at step 709. In case the selection is search based, the input/output module 306 provides the selection and along with its definition to the search engine 312 at step 710.

[00108] Next (step 712), the search engine 306 obtains results (artefacts) associated with the search based selection. It will be understood that the results may be obtained in response to a final query associated with a search location or search content item. For example, in case the user selection was "search location 1 " from table 1, the results could include a list of all locations related to the case number input by the user. Alternatively, if the user selection was "Search Content 1 " from table 4, the results could include all documents created by the user in the last week.

[00109] In case the selection is not search based (e.g., the selection may be a shortcut location item, a central register item, or an intelligent content item), other mechanisms may be used to retrieve the results from the central repository 100. For instance, if shortcut location item or central register item is selected, the input/output module 306 utilizes the URL or directory path defined in the shortcut location/central register to retrieve the hierarchical structure of the locations defined by the item. Further, if a view/report or CAML query is selected, the input/output module 306 may restrict the artefacts in the retrieved locations to only those present in the view/report or CAML query. Alternatively, if intelligent content is selected, the input/output module 306 retrieves a list of the relevant documents from the intelligence engine of the underlying ECM platform 100.

[00110] Subsequently, the input/output module 306 trims the results based on access rights of the end user to the obtained results. To that end, the search engine 306 associated with the ECM platform determines whether the user is authorized to access all the obtained results and removes the results that the user does not have access to.

[00111] Lastly (at step 716), the trimmed results are displayed on the user interface 304.

[00112] If behaviours and actions are defined for the particular location or content item, the client application 310 retrieves the XML definitions of the behaviour and/or action and initiations the behaviour/action either during or after the save or access process is completed. For instance, a behaviour that prompts users to enter additional metadata for a file is invoked when the file is being saved. Alternatively, an action prompting the user to begin a workflow process can be invoked once the file is saved to the ECM platform 100.

[00113] Unlike traditional access methods, the systems and methods described in the present disclosure allow users to efficiently and quickly access location and/or content items on an ECM platform that are pertinent to the user. To this end, the disclosed systems and methods provide location and content items (search locations, shortcut locations, central register locations, search content items, shortcut content items, or intelligent content items) based on the end user into the confines of a solution profile (which normally but not necessarily represents a specific ECM solution on the ECM platform). Search. Moreover, the systems and methods disclosed herein can be implemented without any changes to the underlying ECM Solutions or ECM platform regardless of the information architecture/design of the ECM Solution. |00114] In the context of this specification, the word "comprising" means "including principally but not necessarily solely" or "having" or "including", and not "consisting only of. Variations of the word "comprising", such as "comprise" and "comprises" have correspondingly varied meanings.

Claims

1. A computer-implemented method for processing content on an Enterprise Content Management (ECM) platform, the method comprising:

creating a profile including definitions of at least one location item or content item, the location item providing a mechanism for presenting locations pertinent to a user within the ECM platform, the content item providing a mechanism for presenting content pertinent to the user within the ECM platform;

creating and applying authorization and/or membership information to the profile;

publishing the profile into a central repository;

displaying the profile along with the at least one location and/or content item through a user interface based on user authentication; and

accepting a selection of one of the at least one location and/or content item;

retrieving results, from the ECM platform, based on the selection, the retrieved results comprising artefacts pertinent to the user and available to the user to access; and

displaying the results on the user interface.

2. The method of claim 1, wherein the profile is an XML file.

3. The method of claim 1 , wherein the location item includes at least one of a search location, a shortcut location, or a central register location, wherein the search location provides a search based mechanism for presenting locations within the ECM platform, the shortcut location provides a mechanism to use a hierarchical structure for browsing physical structure of the ECM, and the central register provides a list of locations within the ECM platform along with metadata associated with the locations and URLs for each location.

4. The method of claim 1, wherein the content item includes at least one of a search content item, a shortcut content item, or an intelligent content item, wherein the search content item provides a search based mechanism for presenting content within the ECM platform, the shortcut content item provides a mechanism to use a hierarchical structure for browsing content within in the ECM platform, and the intelligent content item provides content most relevant to the user based on the user's activity.

5. The method of claim 1, wherein displaying the profile on the user interface further comprises:

comparing a user identification with the authorization and/or membership infonnation; and detennining whether the profile can be displayed on a client application based on the comparison.

6. The method of claim 1, further comprising:

searching the ECM system to obtain the results based on the selection;

determining access rights of the end user to the obtained results; and

trimming the results to discard artefacts that the end user is not allowed to access.

7. The method of claim 1 , further comprising:

refining or modifying the retrieved results before displaying the results on the user interface.

8. A system for processing content on an Enterprise Content Management (ECM) platform, the system comprising:

a profile module configured to:

create a profile, the profile including definitions of at least one location item and/or content item pertinent to the user, the location providing a mechanism for presenting locations within the ECM platform, and the content item providing a mechanism for presenting content within the ECM platform;

create authorization information associated with the profile; and

publish the profile along with the authorization information in a central repository;

a user interface configured to:

display the profile and at least one of the location and/or content item associated with the profile based on user authentication;

accept a selection of one of the at least one location and/or content item and an input/output module configured to:

provide the selection to the ECM platform; and

retrieve results, from the ECM platform, based on the selection, the retrieved results comprising artefacts that an end user is allowed to access; and

displaying the results on the user interface.

9. The system of claim 8, wherein the location item includes at least one of a search location, a shortcut location, or a central register location, wherein the search location provides a search based mechanism for presenting locations within the ECM platform, the shortcut location provides a mechanism to use a hierarchical structure for browsing physical structure of the ECM, and the central register provides a list of locations within the ECM platform along with metadata associated with the locations and URLs for each location.

10. The system of claim 8, wherein the content item includes at least one of a search content item, a shortcut content item, or an intelligent content item, wherein the search content item provides a search based mechanism for presenting content within the ECM platform, the shortcut content item provides a mechanism to use a hierarchical structure for browsing content within in the ECM platform, and the intelligent content item provides content most relevant to the user based on the user's activity.

1 1 . The system of claim 8, wherein the profile is an XML file.

12. The system of claim 8, wherein the profile module is configured to authorize a user to access the profile based on a comparison of the user's credentials with the authorization information.

13. The system of claim 8, wherein the profile includes definitions of one or more behaviours and/or actions associated with the location or content items.

14. A computer-implemented method for processing content on an Enterprise Content Management (ECM) platform, the method comprising:

creating a profile including definitions of at least one search location or shortcut location, the search location providing a search based mechanism for presenting locations within the ECM platform, the shortcut location providing a mechanism to use a hierarchical structure for browsing physical structure of the ECM;

creating and applying authorization information to the profile;

publishing the profile into a central repository;

displaying the profile along with the at least one search location or shortcut location through a user interface based on user authentication; and

accepting a selection of one of the at least one search locati on or shortcut l ocation; retrieving results, from the ECM platform, based on the selection, the retrieved results comprising artefacts that an end user is allowed to access; and

displaying the results on the user interface.

15. The method of claim 14, wherein the definition of the search location includes a search location name, a search location description.

16. The method of claim 15, wherein the definition of the search location further includes an input form and a base search query.

17. The method of claim 16, wherein if the selection is the search location, the method further comprises displaying at least one of the input form and the base search query to accept in input from the end user.

18. The method of claim 16, wherein if the selection is the search location, the method further comprising automatically entering default values in the input form and automatically retrieving the results associated with the selection based on the default values.

19. The method of claim 18, wherein the default values are selected automatically based on properties of the content.

20. The method of claim 14, wherein the definition of the shortcut location includes shortcut location name, shortcut location description, and shortcut location identifier.

21. The method of claim 20, wherein the definition of the shortcut location further includes a view/report name.

22. A system for processing content on an Enterprise Content Management (ECM) platform, the system comprising:

a profile module configured to:

create a profile, the profile including definitions of at least one search location or shortcut location, the search location providing a search based mechanism for presenting locations within the ECM platform, the shortcut location providing a mechanism to use a hierarchical structure for browsing physical structure of the ECM; create authorization information associated with the profile; and publish the profile along with the authorization information in a central repository;

a user interface configured to:

display the profile and at least one of the search location or the shortcut location associated with the profile based on user authentication;

accept a selection of one of the at least one search location or shortcut location; and

an input/output module configured to:

provide the selection to the ECM platform; and

displaying the results on the user interface.

23. The system of claim 22, wherein the definition of the search location includes a search location name, a search location description.

24. The system of claim 23, wherein the definition of the search location further includes an input form and a base search query.

25. The system of claim 22, wherein the definition of the shortcut location includes shortcut location name, shortcut location description, and shortcut location identifier.

26. The system of claim 25, wherein the definition of the shortcut location further includes a view/report name.

27. The system of claim 22, wherein the profile includes definitions of one or more behaviours and/or actions associated with the browse and/or search locations.