2023:Grooper Web Client (Application): Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
* This allows end-level users to process review based steps in a '''Batch Process''' in a web browser, without needing to install Grooper on their own machine. | * This allows end-level users to process review based steps in a '''Batch Process''' in a web browser, without needing to install Grooper on their own machine. | ||
* This allows admin-level users to architect document processing resources like '''Batch Processes''' and '''Content Models''' in a web browser, without installing Grooper on their own machine. | * This allows admin-level users to architect document processing resources like '''Batch Processes''' and '''Content Models''' in a web browser, without installing Grooper on their own machine. | ||
== Glossary == | |||
<u><big>'''Activity'''</big></u>: {{#lst:Glossary|Activity}} | |||
<u><big>'''Batch Process'''</big></u>: {{#lst:Glossary|Batch Process}} | |||
<u><big>'''Batch'''</big></u>: {{#lst:Glossary|Batch}} | |||
<u><big>'''Content Model'''</big></u>: {{#lst:Glossary|Content Model}} | |||
<u><big>'''Grooper Repository'''</big></u>: {{#lst:Glossary|Grooper Repository}} | |||
<u><big>'''Grooper Service'''</big></u>: {{#lst:Glossary|Grooper Service}} | |||
<u><big>'''Review'''</big></u>: {{#lst:Glossary|Review}} | |||
<u><big>'''Service'''</big></u>: {{#lst:Glossary|Service}} | |||
<u><big>'''Web Client'''</big></u>: {{#lst:Glossary|Web Client}} | |||
== About == | == About == | ||
The Grooper Web Client allows end users to process documents using an internet connection alone. With the Grooper Web Client, there is no reason for document review users to install Grooper on their workstations. Instead, Grooper is installed on a web server, and users simply access that server's Grooper Repository (or Repositories) using a web browser. They can process review tasks and edit '''Batch''' content using a web-based user interface instead of the traditional thick client. Furthermore, there is no reason for end users to be granted access to the '''Grooper Repository''' databases or file stores since only the service user configured on the web server needs those rights. | The Grooper Web Client allows end users to process documents using an internet connection alone. With the Grooper Web Client, there is no reason for document review users to install Grooper on their workstations. Instead, Grooper is installed on a web server, and users simply access that server's Grooper Repository (or Repositories) using a web browser. They can process review tasks and edit '''Batch''' content using a web-based user interface instead of the traditional thick client. Furthermore, there is no reason for end users to be granted access to the '''Grooper Repository''' databases or file stores since only the service user configured on the web server needs those rights. | ||
* The Grooper Web Client makes the review experience more modern, more secure, and more easily distributable. | * The Grooper Web Client makes the review experience more modern, more secure, and more easily distributable. | ||
Furthermore, as of version 2023, the entire Grooper Product Suite (except Grooper Config) is accessible with the Web Client. This means Grooper Design Studio users can do their work over the web as well. | Furthermore, as of version 2023, the entire Grooper Product Suite (except Grooper Config) is accessible with the Web Client. This means Grooper Design Studio users can do their work over the web as well. | ||
* Grooper Config is an administrative application and must be run locally on the web server. It cannot be accessed remotely with a web browser. | * Grooper Config is an administrative application and must be run locally on the web server. It cannot be accessed remotely with a web browser. | ||
** Grooper Config is required to create connections to Grooper Repositories and create Grooper Services (like the Activity Processing and Import Watcher services). | ** Grooper Config is required to create connections to Grooper Repositories and create Grooper Services (like the Activity Processing and Import Watcher services). | ||
Please visit the following articles for more information on the Grooper Web Client: | Please visit the following articles for more information on the Grooper Web Client: | ||
Revision as of 13:49, 10 May 2024
The Grooper user interface is accessed using a web browser from a URL. The Grooper Web Client is the application that installs the Grooper website on a web server.
- This allows end-level users to process review based steps in a Batch Process in a web browser, without needing to install Grooper on their own machine.
- This allows admin-level users to architect document processing resources like Batch Processes and Content Models in a web browser, without installing Grooper on their own machine.
Glossary
Activity: Grooper Activities define specific document processing operations done to a inventory_2 Batch, folder Batch Folder, or contract Batch Page. In a settings Batch Process, each edit_document Batch Process Step executes a single Activity (determined by the step's "Activity" property).
- Batch Process Steps are frequently referred by the name of their configured Activity followed by the word "step". For example: "Classify step".
Batch Process: settings Batch Process nodes are crucial components in Grooper's architecture. A Batch Process is the step-by-step processing instructions given to a inventory_2 Batch. Each step is comprised of a "Code Activity" or a Review activity. Code Activities are automated by Activity Processing services. Review activities are executed by human operators in the Grooper user interface.
- Batch Processes by themselves do nothing. Instead, they execute edit_document Batch Process Steps which are added as children nodes.
- A Batch Process is often referred to as simply a "process".
Batch: inventory_2 Batch nodes are fundamental in Grooper's architecture. They are containers of documents that are moved through workflow mechanisms called settings Batch Processes. Documents and their pages are represented in Batches by a hierarchy of folder Batch Folders and contract Batch Pages.
Content Model: stacks Content Model nodes define a classification taxonomy for document sets in Grooper. This taxonomy is defined by the collections_bookmark Content Categories and description Document Types they contain. Content Models serve as the root of a Content Type hierarchy, which defines Data Element inheritance and Behavior inheritance. Content Models are crucial for organizing documents for data extraction and more.
Grooper Repository: A Grooper Repository is the environment used to create, configure and execute objects in Grooper. It provides the framework to "do work" in Grooper. Fundamentally, a Grooper Repository is a connection to a database and file store location, which store the node configurations and their associated file content. The Grooper application interacts with the Grooper Repository to automate tasks and provide the Grooper user interface.
Grooper Service:
Review: person_search Review is an Activity that allows user attended review of Grooper's results. This allows human operators to validate processed contract Batch Page and folder Batch Folder content using specialized user interfaces called "Viewers". Different kinds of Viewers assist users in reviewing Grooper's image processing, document classification, data extraction and operating document scanners.
Service: Grooper Services are various executable programs that run as a Windows Service to facilitate Grooper processing. Service instances are installed, configured, started and stopped using Grooper Command Console (or in older Grooper versions, Grooper Config).
Web Client: The Grooper user interface is accessed using a web browser from a URL. The Grooper Web Client is the application that installs the Grooper website on a web server.
About
The Grooper Web Client allows end users to process documents using an internet connection alone. With the Grooper Web Client, there is no reason for document review users to install Grooper on their workstations. Instead, Grooper is installed on a web server, and users simply access that server's Grooper Repository (or Repositories) using a web browser. They can process review tasks and edit Batch content using a web-based user interface instead of the traditional thick client. Furthermore, there is no reason for end users to be granted access to the Grooper Repository databases or file stores since only the service user configured on the web server needs those rights.
- The Grooper Web Client makes the review experience more modern, more secure, and more easily distributable.
Furthermore, as of version 2023, the entire Grooper Product Suite (except Grooper Config) is accessible with the Web Client. This means Grooper Design Studio users can do their work over the web as well.
- Grooper Config is an administrative application and must be run locally on the web server. It cannot be accessed remotely with a web browser.
- Grooper Config is required to create connections to Grooper Repositories and create Grooper Services (like the Activity Processing and Import Watcher services).
Please visit the following articles for more information on the Grooper Web Client:
- Installation Guide
- This article shows you how to install the Grooper Product Suite.
- Pay close attention to the "Installing IIS" and "Installing Grooper Web Server" sections. After IIS and the Grooper Web Server application is installed, you will be able to access Grooper over the web using the Web Client interface.
- Review User Guide
- This article is geared towards end users who will use the Grooper Web Client to review Grooper's automated document processing results.
- Detailed information on how to use the various modules to review document classification, data extraction, and more is included in the article.
- Review Designer Guide
- This article is geared towards Grooper Design users in charge of architecting Grooper resources (Batch Processes, Content Models, etc).
- This contains information and advice for Design users on how to configure Review steps in a Batch Process and other tips to increase the value of the user's review experience.
|
⚠ |
The Grooper Web Client DOES NOT support Internet Explorer. The following browsers are supported:
Other modern browsers may work but have not been fully tested, such as:
|