Five Phases of Grooper (Concept): Difference between revisions

From Grooper Wiki
made several changes to structure and relevant information // via Wikitext Extension for VSCode
No edit summary
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<blockquote>
<blockquote>{{#lst:Glossary|Five Phases of Grooper}}</blockquote>
Working with '''Grooper''' is made easier by considering how documents move through this system.
</blockquote>


==About==
==About==
Line 17: Line 15:
#* This is the first phase of the life of a document in '''Grooper'''. This is essentially the act of getting the document(s) into '''Grooper''' via means such as scanning or some type of electronic import.
#* This is the first phase of the life of a document in '''Grooper'''. This is essentially the act of getting the document(s) into '''Grooper''' via means such as scanning or some type of electronic import.
# '''Condition'''
# '''Condition'''
#* After documents come into '''Grooper''', they next need to be made ready for processing, or conditioned. This consists of '''[[Image Processing]]''' and the '''[[Recognize (Activity)|Recognition]]''' of text.
#* After documents come into '''Grooper''', they next need to be made ready for processing, or conditioned. This consists of '''[[Image Processing]]''' and '''[[Recognize|text recognition]]'''.
# '''Organize'''
# '''Organize'''
#* With ''cleaned'' up documents, and access to the documents' text, its critical to next identify/organize them, or specifically in '''Grooper''', '''[[Classify (Activity)|Classify]]''' them. '''Grooper''' doesn't know what to do with a document unless it knows what type of document it is, and that's the point of the activities performed in this phase. An example to consider what is done here is to think about a person given a stack of documents who is tasked with putting those documents in a filing cabinet. In order for the documents to go into the right area in the filing cabinet, the person would have to know the differences between the documents and be able to identify them.
#* With ''cleaned'' up documents, and access to the documents' text, its critical to next identify/organize them, or specifically in '''Grooper''', '''[[Classify (Activity)|Classify]]''' them. '''Grooper''' doesn't know what to do with a document unless it knows what type of document it is, and that's the point of the activities performed in this phase. An example to consider what is done here is to think about a person given a stack of documents who is tasked with putting those documents in a filing cabinet. In order for the documents to go into the right area in the filing cabinet, the person would have to know the differences between the documents and be able to identify them.
Line 28: Line 26:


=== Five Phases Activity Examples ===
=== Five Phases Activity Examples ===
# '''Acquire'''
Below are all the activities you can perform in '''Grooper''' organized by the "phase" they ''belong'' to.
#* Batch Transfer
 
#* [[CMIS Connection|CMIS Connection/Repository]]
==== Acquire ====
#** AppXtender
* Scan (via the [[Review]] activity and the [[Scan Viewer]])
#** Box
* Digital files are acquired via an [[Import Provider]], not an Activity step in a Batch Process.
#** CMIS
 
#** Exchange
==== Condition ====
#** FileBound
 
#** FTP
Text recognition
#** IBM FileNet Connector
* [[Recognize]]
#** IMAP
 
#** NTFS
Image file conditioning
#** OneDrive
* [[Image Processing]]
#** SFTP
 
#** SharePoint
PDF and TIF conditioning
#* [[Execute (Activity)|Execute]]
* [[Split Pages]]
#* OPEX Import
 
#* Scan (via [[Desktop Scanning in Grooper|Grooper Desktop]])
Microfiche conditioning
# '''Condition'''
* [[Clip Frames]]
#* Burst Book
* [[Detect Frames]]
#* Detect Language
* [[Initialize Card]]
#* Execute
 
#* Merge
Book photo conditioning
#* Microform Processing
* [[Burst Book]]
#** Clip Frames
 
#** Detect Frames
File format normalization
#** Initialize Card
* [[Render]]
#* Recognize
 
#* Remove Level
Language conditioning
#* [[Render (Activity)|Render]]
* [[Detect Language]]
#* Review
* [[Translate]]
#* [[Split Pages (Activity)|Split Pages]]
 
#* Split Text
==== Organize ====
#* Text Transform
* [[Separate]]
#* Translate
* [[Classify]]
#* [[XML Transform]]
* [[Remove Level]]
#* [[Image Processing (Activity)|Image Processing]]
* [[Deduplicate]]
# '''Organize'''
 
#* Classify
Text file organization
#* Deduplicate
* [[Split Text]]
#* Review
 
#* [[Separate (Activity)|Separate]]
==== Collect ====
#* Spawn Batch
 
# '''Collect'''
* [[Extract]]
#* Convert Data
 
#* Correct
The following typically happen after Extract runs. They relate to normalizing data post-collection.
#* Extract
* [[Apply Rules]]
#* Launch Process
* [[Convert Data]]
#* Redact
 
#* Review
==== Deliver ====
#* Spawn Batch
* [[Export]]
#* Train Lexicon
* [[Dispose Batch]]
# '''Deliver'''
 
#* Dispose Batch
These activities build files out of processed content before Export.
#* Execute
* [[Merge]]
#* Export
* [[Text Transform]]
#* Send Mail
* [[XML Transform]]
#* Spawn Batch
 
==== Misc/Multiple Phases ====
These activities either don't fit well into one of the five phase categories or could potentially be in more than one phase, depending on how they are used.
 
* [[Review]]
* [[Execute]]
* [[Correct]]
* [[Redact]]
* [[Spawn Batch]]
* [[Send Mail]]
* [[Train Lexicon]]
* [[Launch Process]]


[[File:five_phases_04.png]]
[[File:five_phases_04.png]]

Latest revision as of 10:11, 2 March 2025

The "Five Phases of Grooper" is a conceptual term that seeks to build understanding of how documents are processed through Grooper.

About

Grooper is a transient system that is meant to allow documents to move through it. The work that is done in Grooper builds the scaffolding that allows the movement of documents through Grooper. The goal of moving documents through Grooper is to produce data to be stored in a backend system of your chose that is impactful to your business. In working with Grooper, it is best to think about the flow of the documents through the system in five linear phases.

Five Phases of Grooper

What are the Five Phases of Grooper?

The Five Phases of Grooper are a framework to help conceptualize the path odocuments take through Grooper which help a designer more easily understand how to model with the tools available.

Five Process Phases

  1. Acquire the documents by bringing them into a Batch in Grooper.
    • This is the first phase of the life of a document in Grooper. This is essentially the act of getting the document(s) into Grooper via means such as scanning or some type of electronic import.
  2. Condition
  3. Organize
    • With cleaned up documents, and access to the documents' text, its critical to next identify/organize them, or specifically in Grooper, Classify them. Grooper doesn't know what to do with a document unless it knows what type of document it is, and that's the point of the activities performed in this phase. An example to consider what is done here is to think about a person given a stack of documents who is tasked with putting those documents in a filing cabinet. In order for the documents to go into the right area in the filing cabinet, the person would have to know the differences between the documents and be able to identify them.
  4. Collect
    • Now knowing what document is what, it is time to Extract the desired information from the documents. From a construction perspective, the scaffolding required to accomplish the activities performed in this phase will take the most amount of time and effort.
  5. Deliver
    • Finally, it's time for the collected data to make its way out of Grooper to whatever destination system is defined by your business via Export. This is, in a way, an inverse of Acquire, and the systems that things come in through, often mirror the systems they go to.

Five Phases Activity Examples

Below are all the activities you can perform in Grooper organized by the "phase" they belong to.

Acquire

Condition

Text recognition

Image file conditioning

PDF and TIF conditioning

Microfiche conditioning

Book photo conditioning

File format normalization

Language conditioning

Organize

Text file organization

Collect

The following typically happen after Extract runs. They relate to normalizing data post-collection.

Deliver

These activities build files out of processed content before Export.

Misc/Multiple Phases

These activities either don't fit well into one of the five phase categories or could potentially be in more than one phase, depending on how they are used.