Governments, Federal, Provincial or Municipal, manage massive amounts of data and documents on daily basis; some of that information pertains to citizens personal information and that falls under very strict privacy and protection rules as much as other more sensitive types of information does.
With data, be it row data or content data, creation volumes expected to sore, the Government, just like private sector organizations, must continuously strive to find measures capable of ensuring adequate handling, storage, management, dissemination, security and above all, use of that data for planning and decision making.
The Government of Canada Data Strategy initiative is to address all the above and is intended to provide better Citizen services. But, with data and content residing in different solution repositories and with the lack of inter-governmental data sharing frameworks, the Data Strategy initiative is up against very serious challenges.
Government employees today look for information in multiple repositories, each designed to address specific needs or requirements, GCDocs and RDIMS (OpenText Content Servers and eDocs), Microsoft SharePoint and Dynamics, ERP, Databases and many more. Each solution has its own interface, terminology, security and storage methods.
Mass data migration and/or solutions integration projects are time and financial costly options that might address a subset of requirements or might have subpar results. They lack any intelligence that can assist users in daily tasks and operations and the return on investment, if any, would not be achieved in a short time frame.
The Enara approach employs the powers of connectors, plug-ins, crawlers and faceted navigation as well as direct deep integration with repositories such as Enterprise Content Management Solutions, SharePoint, ERP’s, Shared Drives, Dynamics, Salesforce, email servers and even social media.
Background engines use deployed connectors or plug-ins to empower a user interface that unifies search across all authorized and connected repositories.
The unified result list displays hits returned from all connectors, grouped by repository with additional sorting and filtering options. A single access point and a single interface to organization information based on user access rights to each connected repository.
Authorized users can even edit content and data in connected repositories without leaving the unified view interface and can export result lists for reporting purposes