Search Session Threading based on Spiral Modeling for Internet Messaging

Internet Messaging using Mozilla Firefox and Thunderbird and SQLite Database Engine applies Spiral Principles at the
Single Point of Entry...........................................................................................................................................................................2
Choice of Components and Installation............................................................................................................................................2
Implementation of the Proof of Concept..........................................................................................................3
SearchIndex Entry. Store and File Search Sessions for prompt and qualified Use.....................................4
Types of Search Contacts encountered.............................................................................................................................................4
SQLite SearchIndex Table Fields......................................................................................................................................................4
Using the Terms to retrieve Information Resources.......................................................................................................................5
Project Flow Control promotes Information Flow along the Ring................................................................................................6
Example: SearchIndex Enter E-mail, Forum, Mailing List Contacts Inline................................................................................6
Example: Combine Information Assets from Internet Search Sessions........................................................................................6
Example: SearchIndex Combine Information Assets from Internet Search Sessions.................................................................6
Coherence. Discriminating between Entry in SearchIndex2 or ThreadSession...........................................................................6
Example: Evaluating Technology Dublin Core Meta Tags and BibTex.......................................................................................7
Facet as a simple Report of the Evaluation of Meta Tags and Bibtex...........................................................................................7
Tables SearchIndex2, ThreadSession, ThreadIndex collection of Search Assets.........................................................................7
Workflow Methods automate Search Session Threading..................................................................................................................8
Workflow to Assemble Transaction Search Sessions from Table SearchIndex2.........................................................................8
Methods for smooth Workflow in Search Session Workflow.........................................................................................................8
Method “T”........................................................................................................................................................................................8
Method “TS”......................................................................................................................................................................................8
Advantages of the Methods................................................................................................................................................................9
Transaction Search Session. Use Facets to Qualify potential Information Resources in Threads.............9
Example: Firefox causing 100% CPU Utilization over extended Periods.....................................................................................9
Transaction Search Session..............................................................................................................................................................10
Use SearchIndex_Lookup_Temp Table to List Session Resources in a Lookup Table.............................................................10
Maintain Threads using Workflow Methods.................................................................................................................................10
Standard Operations to manipulate Contacts...................................................................................................................................10
Method “T”......................................................................................................................................................................................10
Method “TS”....................................................................................................................................................................................11
Workflow Balance...........................................................................................................................................................................11
Logging processed records...............................................................................................................................................................11
Example of Smooth Workflow to complete Threads in Transaction Search Session................................................................11
Combine 1. Transaction Search Session Refresh. Edit SearchIndexes and Threads and add Resources................................11
Display ThreadSession SearchIndex SearchGrid.........................................................................................11
Reducing Hesitation. Assign ThreadSessions to Threads.............................................................................12
ThreadIndexes collect and organize Threads................................................................................................12
Improvement to Organize Browsing Content Inline.....................................................................................12
Reduce Interruption in Search Session Path History...................................................................................13
Mathematical Model of Ulam Spiral in Communication and Growth........................................................13
Limitations........................................................................................................................................................14
Next Generation................................................................................................................................................15
Free Source of Transaction Search Session...................................................................................................15
Bibliography......................................................................................................................................................15
Strategic Business Development, Sales Cycle Management.........................................................................................................15
Internet Messaging............................................................................................................................................................................15
References..........................................................................................................................................................................................16
Ulam´s Spiral.....................................................................................................................................................................................16
Web.....................................................................................................................................................................................................16
Glossary.............................................................................................................................................................17
Name...................................................................................................................................................................................................17
Key Terms in.....................................................................................................................................................................................17
Appendix 1 Facet as a simple Report of the Evaluation of Meta Tags and Bibtex............................................18
20091pub_10SyDbSessThreadProof2.doc 07.12.21 -1-
Internet Messaging using Mozilla Firefox and Thunderbird and SQLite Database Engine applies Spiral Principles at the
Single Point of Entry

Constructing the Single Point of Entry from spiral properties takes information contacts from the Message Cycle and threads them
for use in issue resolution and to-dos. Further qualification of the threads inserts them into projects to progress the team. Choosing
Strategic Business Development and Sales Cycle Management as test fields demonstrate how this model empowers small, flexible
teams to respond to customer needs. Implementation of the model fulfills the team application profile which is composed of team
members with individual, networked fields of responsibility and common goals. Targets of meeting project deadlines, cost and
performance network the team. Each member derives his or her responsibilities from team goals. While tangentially meeting; team
members work independently within their own areas of responsibility. Exchanging Information Resources enriches and adds
potentially useful material but members do not require all material accumulated by other team members. Communication between
team members selects and distributes pertinent and useful information which exchanges within the team and directly influences
team results and meeting team goals.

Arriving at the Single Point of Entry; search contacts feed Internet, email or document files. Unifying the Single Point of Entry
combines all contacts regardless of media and makes indexing information available in a single source. When searching for
resources the user needs only to search one index. Construction of the Single Point of Entry is explained in [RSPOE]. After almost
two years of testing; this system shows it’s reliability and facility of storing the contacts and flexibility of passing indexing
information to an SQLite database engine. Successful implementation allows the user to store and file material inline. Mozilla
Firefox interfaces and stores Internet search contacts while Thunderbird processes email and storage of the correspondence and
arriving Information Resources. ScrapBook a Firefox extension; stores the Internet Information Resources and provides indexing of
Internet contacts. Thunderbird extensions condense emails into indexes containing Subject;, X-Tags:, and file them in a .csv
(comma separated file) format. File managers produce file lists from folders containing (project) documentation and these lists
progress to a central index. Using .csv as a widely spread file format enables use of the information not only in the Internet
Messaging but is useful for spreadsheets and other commonly employed business applications. Within the prototype system; SQLite
Virtual Tables pick up the individual .csv files and centralize them in a database and index of Internet, email and document content
available for qualification. Users reference a central index of unified Information Resources derived from project experience and
know-how.

Information Resources qualify from incoming contacts based on the potential of useful adaptation to participate in team
requirements solving problems and issues. Contacts deemed without potential use remain as SearchIndexes in the contact pool.
They may mature to lend usefully information at a later time. Combination with other contacts may also produce useful information
to progress the team efforts. Contacts qualified as potentially useful are seldom useful alone but combine with other qualified
contacts in a thread. Usually threads identify by defining the thread topic which is also the search term used to identify the
information content. Qualified SearchIndexes are ThreadSessions. Search terms for the ThreadSessions are SearchKeys and
Search_Desc. Threading finds routinely used resources promptly in the SQLite database by using the SearchKey or searching the
search description (Search_Desc) which contains the session search results.

ThreadSessions refer to individual topics that are often key resources to solutions. As work progresses; ThreadSessions group into
ThreadIndexes where further adaptation and maturing continue. When complete; ThreadIndexes network sessions to build problem
solutions or provide documented information to address issues. They are the components for presentations and team as well as
customer communication. Transaction Search Session is an SQL application for the database engine SQLite implementing
threading for the user and displays facets to support issue resolution and problem solving.

Combining indexes from Internet Messaging enables the user to fluidly store incoming information contacts and qualify them.
Retrieval of useful resources occurs through this application. Entry processing separates contacts into topics and organizes them in
ThreadSessions.

Choice of Components and Installation

Limiting openness of the components restricts the ability to minimize and simplify team infrastructure as well as tailor it to needs.
Hence it is a major consideration for choice of components. Using the inspiration of Ulam Spiral suggests use in team applications
and not in headquarters centric structures. Hence openness of technology indicates use of the Mozilla Internet Messaging
framework, and individual, local team support recommends integration of SQLite as database engine.

A Single Point of Entry builds from Internet Messaging as described in [RSPOE]. Dividing the implementation into phases offers
stepped performance and periods of acquaintance for the user. Install the Single Point of Entry to introduce Search Session
Threading and Transaction Search Session storing and filing all incoming information contacts for the user. Ideally contact
processing occurs inline without interrupting the flow of the search session. Supported by a team database; store the contacts locally
for the user for timely retrieval when addressing problems. During this initial phase use standard wrappers for SQLite to file and
retrieve Information Resources which reduces training time. These SQLite wrappers such as the Firefox extension SQLiteManager
or SQLite Expert or the specialist application SpatialLite allow the user to manipulate Internet content. Focus on rapid and
transparent storage and retrieval to support meeting team deadlines and goals. After achieving familiarity and facility; advance to
use of a graphical interface (GUI) to support Search Session Threading. Finally extend the individual training to support Project
Management through the integration of threading. Each phase also optimizes and adapts the user interface to team specific
workflow.
20091pub_10SyDbSessThreadProof2.doc 07.12.21 -2-
How do you know if the [name ] Internet Message Cycle is working?
Feel the gratification at finding the needed resource when needed and in time to finish. Feel the satisfaction of finding an
interesting, and useful information fragment and combining it with others related to it while working online. Feel the confidence
when finished searching through accumulated documents for all possible pertinent information that nothing important has been
missed. Enjoy the satisfaction of threading information as it starts to fit into the solution pattern.

Why use a spiral model?

Original research into Ulam Spiral suggested that the that the winding coils around the spiral center would support team storage,
processing and communication and it’s members in a responsive way. Using only essential paths; it streamlines information
retrieval and use in activities. Contributions to Project Management would empower team members to meet requirements.

What is the spiral model? And What are the primary spiral principles that drive Search Sessions?
Ulam Spiral begins as the determination of what the Theorem of Inclusion/ Exclusion names the Inclusion. The Inclusion defines
the area of the middle of the spiral. Spiral growth uses the Inclusion as a building block and replicates and copies the Inclusion.
Each block attaches to the end of the preceding one. A spiral builds from a single, climbing line that includes all possible variations
of the properties of the Inclusion. As the line climbs it construct rings that open and close on a pre-determined point around the
Inclusion. In the transversal of the ring built between the opening and closing; each additional step changes the properties of the
previous point linearly. Each point occupies a unique position in the ring and coordinates identify this point. Applied to business
applications; activities and Information resources are the two coordinates necessary to fully describe each point in the ring and on
the climbing line. Usually suitable Information Resources preclude successful completion of an activity or to-do. To-do completion
starts by searching for sufficient information to complete it. Area of the Inclusion and the position completely determine spiral
growth. Using a single path to design business applications simplifies use for the user and reduces the necessary infrastructure to the
essential. It necessitates an action principle that to-do something requires an action. A single path requires that the action be a least
action and take the path of least resistence and distance. It predicts the need of only one processing system and eliminates duplicate
systems. Replicating the Inclusion fulfills the need of all actions and matches the action with the needed Information Resource.

What does Ulam Spiral offer to improve Information Flow and Availability?
Describe the Inclusion and this description will completely describe spiral growth and the path that it takes. Properties of the
Inclusion replicate throughout the ensuing structure. A wonderful spiral network rises from the Inclusion where 8 vertexes meet.
These vertexes carry communications throughout the filigree structure. Rising from the backbone; the Inclusion carries big, heavy
duty lines to the rings. Between the vertexes; risers climb from the Inclusion and intersect each slot or incremental ring position.
Each of these positions is the solution to a quadratic of the form (4x2 + bx + c). Each slot has an integer value hence all numbers
reside in the spiral structure and are solutions of this quadratic family.

What benefit does use of the spiral model for compact, responsive teams offer?
It orders tight, minimal, essential local systems to the team members who carry out activities centered around a midpoint. It
includes performance and security to cover all team needs. Offering communication through a central backbone with redundant
pathways it also directly connects members with similar interests and activities. It exchanges needed information without the
requirement of central information storage. Additionally it shows that local identification and requests of needed resources suffices
without central storage. This simplifies the system, database and communication needs. In the test it minimizes resources needed to
support team growth to respond to market needs. Based on a single path; it readily identifies information and task properties.

Continue reading for a more detailed spiral description of the math and it’s application or See [TIE] and [SUS] for the mathematical
derivation of the Theorem of Inclusion/ Exclusion and a description of it’s application.

Implementation of the Proof of Concept

Discussing the implementation of the Proof of Concept; this article presents the results of testing the application of these principles
within the framework of Strategic Business Development and Sales Cycle Management. Building the Single Point of Entry with an
Internet Messaging System; connected the flow of contacts to an SQLite database engine for storage and retrieval of contacts in
support of Project Management. Testing indexing and threading; the first phase concluded with an examination of the system
ability to reduce hesitation and interruption in search sessions.

Refer to these articles [QR] [BIA] [SSCM] [LCDO] to learn how the principles formulated in this article support Strategic Business
Development and Sales Cycle Management.

To build the Single Point of Entry using Mozilla Firefox and Thunderbird refer to these articles [MTD] [IMC]. Testing of this entry
point over almost 2 years demonstrates suitability for team use.

This Proof of Concept concludes testing of the threading infrastructure and the collection as well as combination to display
potential, ways and solutions in support of Project Management. It implements the Search Session and Transaction Search Session.

Continuing development appends Search Session Threading including a graphical interface to support Project Management.

20091pub_10SyDbSessThreadProof2.doc 07.12.21 -3-

SearchIndex Entry. Store and File Search Sessions for prompt and qualified Use
Types of Search Contacts encountered

Progress in activities require Information Resources. A question or problem often motivates searching. This path encounters not
only relevant search contacts but unqualified contacts that may have future use. What types of contacts are encountered? How can
they be processed inline by the user within a useful time period?

The Search Contact asks a question on how to resolve an issue or follow-up on an idea. It turns up and returns answers on
possibilities to address the present issue. Referring to the spiral model; it addresses the immediate issue or slot, but also includes
surrounding slots (range). Projects tend to localize as a vertex. Information peripheral to the SearchKey is also of value as it may
also contribute to a solution. Using the SearchKey and Search_Desc produces a range of topics that potentially address an issue. But
responses often include the second type of contact which produces information on the activities of a contact source.

Contact source information often turns up information on the products of a company or a library that offers suitable material. It
would be worthwhile to record an overview and summary at this slot of the offerings for future use. This source material may not
have current use but intuitively offer future potential. Record the information on this unqualified source for example: products,
company or content. Encompassing a range of possibilities beyond a single issue; a suspicion nags that sometime it would be good
to return to this contact. This material laterally connects threads and possibly projects. Neighboring slots contain similar and related
information and the similarities connect laterally. Addressing a range of issues; it offers multiple potential resources.

SQLite SearchIndex Table Fields

Figure 1 SearchIndex2 Inline Entry of Search Contacts in SQLiteManager

Table SearchIndex2 stores contact information and allows the user to qualify the potential, ways and solutions that the contact may
offer.

 Search Key. Enter the terms used to search.

 Search Engine. Enter Search Engines used.
 Search Description or Results. Search_Desc. Enter the contact content, results and further sources or references
encountered.
 SUrl_File. Address of downloaded files or content.
 Relate_Sterm. Enter information discovered relating to other potential or current topics.
 S_Query. Define a Saved Search id for this resource.
 SAct_IR. Enter the Activity the search relates to. Enter the project it belongs to or where it participates. Called the PN
(promotion number); the PN uniquely identifies the contact and includes the two coordinates of (Activity, Information
Resource).
20091pub_10SyDbSessThreadProof2.doc 07.12.21 -4-
Inline Filing, Storage, indexing and Cataloging:
SearchKey, X_Tags: X_Cat: and Tags may mix information and reduce search effectiveness. These terms control the
filing. They also target information areas for the user or reader. Define the terms to correctly control information flow.
Retrieve information using SearchKey. X_Tags: further refine the SearchKey for the contact. X_Cat catalogs topic groups.
X_Tags:
X-Tags: further refines the SearchKey for the contact. SearchKey relates to project or thread search terms. Each contact
covers individual topics. It relates to collected resources and provides tags used to file or store incoming information. The
tags refer to filing storage. Reference terms to recall information or find internal Information Resources for use. Terms
relate to filed Threads. It further refines the SearchKey.

Using the Terms to retrieve Information Resources

Use these terms to promptly retrieve Information Resources from the database.
SearchKey
Searching for info. SearchhKeys control the search and retrieve potential threads. Change or add to these terms to refine
the search. It records the serach terms used to locate information in search engines.
Search_Desc
Search_Desc contains a description of the cumulative search results and topics (Search Description). If the SearchKey did
not turn up the necessary contact; broaden the search to examine the content.
Tags or X_Tags
What terms lead users to this document and the concepts contained in it? This typical term is used to tag documents to find
information and categorize the information in the document. It defines tags for users to classify docs. Use tags to profile
the produced document for future readers or users. Tags refers to the commonly used designation and X_Tags names the
IM Mozilla implementation.
Relate_Sterm
Related Search Terms. What related information for other documents embed in this asset? It identifies future potential
assets or lateral assets located adjacently on the ring.

Project Flow Control promotes Information Flow along the Ring

A ring is a cyclical progression or variation of the PN (Activity, IR). PN stand for Promotion Activity and promotes successful
completion. It is the to-do completing the project. It opens at the opening node and meets this point at the end. Business applications
would use a business year or the Message Cycle opens with the approach and closes with the implementation [SSCM]. Progressing
around the ring brings a continuous flow of information that would pile up and wait for processing if it is not efficiently done inline.
Project Flow Control starts with threading the material for later use. Inline execution enters available material immediately before
proceeding to the next contact. Minimal requirements for following retrieval and application enter the SearchKey and Search_Desc.
Use of these terms allows threading and qualification.

Example: SearchIndex Enter E-mail, Forum, Mailing List Contacts Inline

For those readers interested in implementation of [name ] information on the database and a scripting language is of use for
evaluation and implementation. SQLite users mailing list sqlite-users@sqlite.org and TCL comp.lang.tcl@googlegroups.com offer
help in proceeding with the integration task and use of these resources leads to progress by offering highly qualified technical
information.

SQLite users mailing list corresponds with email and the Mozilla IM (Internet Messaging) system indexes, stores and catalogs these
information contacts readily inline. SQLite recommends use of the scripting language TCL although practically any established
scripting language offers suitable bindings. TCL comp.lang.tcl@googlegroups.com is a Google Group where the contacts arrive
grouped in digest form. Individual contacts cannot be indexed and stored individual. Inline entry of the Subject:, X_Tags:, and Http
link in an index database reference these contacts. Mozilla IM uses Thunderbird extensions to export the emails to an SQLite
database.

 Create a SearchIndex from Forum, E-mail List

 Generate a SearchIndex for the SQLite Users mailing list with use of X_Tags:. In Thunderbird detail the Subject with
further terms in the X_Tag:.
 Digest email from Google Groups requires a separate database to store the Subject, X_Tag:, Http link and message data.
Because the digest combines emails they cannot be individually indexed.

Example: Combine Information Assets from Internet Search Sessions

Build the material in Search Sessions from forums and mailing lists into useful and responsive information archives. Mailing lists
and participation provides detailed information to combine with Internet and add to Threads. Document useful information
contained in mailing list, forum discussion. Reference the e-mails to use in problem solving.
 Searchkey: enter X-Tag: (X-Tag: = Searchkey
 S_Engine: Search Engine = Mailing List Address
 SUrl_File: record any content downloaded

20091pub_10SyDbSessThreadProof2.doc 07.12.21 -5-

  Search_Desc: Enter (Searchkey) Description of contents.
 Relate_Sterm. Record Related Search Terms and Informtion. Record information that may be useful another time. This
information complements other topics and not the focus topic of the Search Session. It provides potentially valuable
information for the indentified SearchKey.

Example: SearchIndex Combine Information Assets from Internet Search Sessions

Internet Sessions document assets gleaned during Internet sessions. It records the SearchKey and the individual information assets
relating to the SearchKey enter in the Search_Desc. Using the same terms listed above for email, Internet contacts enter directly
inline into SearchIndex2. The Proof of Concept adequately demonstrates that contacts enter inline during the session. Using the
SearchKey or Search_Desc finds related contacts so that new contacts combine to thread with other topical items.

Coherence. Discriminating between Entry in SearchIndex2 or ThreadSession

Single Point of Entry. Contacts enter the single point of entry where contacts and threads collect. Inserting or storing info while
searching requires a decision whether to store in the table SearchIndex2 or qualify as a ThreadSession. Threads qualify by
addressing an action and store a unique PN, SearchKey and query. Contacts store and organize content on arrival by the SearchKey
but have no immediate potential. After qualification it stores in a thread. During a general search content stores in table
SearchIndex2 without relating to an action. Automation allows the user to build the ThreadSessions and ThreadIndexes inline from
the contacts in SearchIndex2. Potential use discriminates between a contact and thread. This definition is called Coherence and
allows resolving a contact into a ThreadSession. Potential use has not yet been identified for a contact, but a ThreadSession shows
promise of addressing an issue, problem or use as a to-do.

How does Coherence limit hesitation and interruption in inline entry?

Example: Consider the user learning to use Latex and has to comment Bibtex entries. After finding the material; where does it
store? After searching for the syntax for writing BibTex comments. How does the user decide if this content stores in SearchIndex2
or ThreadSession?

Answer: A PN has been assignened to it and it belongs to ApplTech_1_Office_Latex_Bibtex. It stores as ThreadSession threaded to
the ThreadIndex ApplTech_1_Office_Latex_Bibtex

Example: Evaluating Technology Dublin Core Meta Tags and BibTex

Building an infrastructure to meet user’s needs requires ideas that new technologies bring and evaluating those technologies for
integration. [name ] assists in this on-going task. If each document contains a SearchKey or Search_Desc then searching document
storage produces the documents related to these search terms. It is analog to the search in IM. Two technologies offered potential
for cataloging document search. BibTex is a document database for Latex. Dublin Core Meta Data indexes web documents and
could apply to all documents. Collect information on these technologies and apply Information Resources to evaluate the suitability
and usefulness.

Choosing the right technology for an implementation problem is an important application of searching. It identifies potential
implementation candidates. It collects information on implementation possibilities. It also stores information to use to compare and
evaluate the benefits of the different possibilities.

Example: Compare Dublin Core Meta Tags and BibTex Technologies.

Taken together both are redundant technologies and what information will help to identify the most useful one?
Use Transaction Search Session to filter and isolate resources collected and relating only to either Bibtex or Dublin Core Meta Data
and look at the potential. Compare the results of two different search terms "Dublin Core Meta Tags" and "Dublin Core Meta Tags
+ BibTex".

Transaction Search Session works on two levels in a session. 1) SearchIndex, 2) Threads. Is the information threaded or not? The
difficulty arises when under the pressure of searching and a level determination is necessary to find the material either in
SearchIndex or ThreadSessions. Hesitation reduces during the search by storing content in as unqualified and returning to qualify
later.
A variation in search terms produces the sources for evaluation.
 SearchKey: Dublin Core Meta Tags produces no records.
 SearchKey: Dublin Core produces the records.
 ThreadIndexes: TIndexId 23 Metadata template. Dublin Core XML, Html.
 The Search includes the intersection of Dublin Core Meta Tags + BibTex.
 SearchKey: BibTex produces no ThreadSessions but 2 SearchIndexes.
 SearchKey: Latex produces the records.
 Integrate Dublin Core Meta Tags and BibTex in Latex documents. Do not duplicate Dublin Core Meta Tags with BibTex.
Use BibTex as the primary storage.

20091pub_10SyDbSessThreadProof2.doc 07.12.21 -6-

Evaluation of the collected resources led to the decision to use the .html format as primary document format and implement the
terms SearchKey, Search_Desc as well as the other SearchIndex items in Meta Data.

Facet as a simple Report of the Evaluation of Meta Tags and Bibtex

This example demonstrates the use of facets to display Information Resources. Facets use SearchKey and Searc_Desc to filter
resources . Tables SearchIndex2, ThreadSession and ThreadIndex display all resources. Queries on these tables filter the applicable
resources. Transaction Search Session displays facets filtered by the terms. It reduces the scope of the search to only the resources
satisfying the search terms.

A simple report on the search results in Appendix I shows the results produced.

Tables SearchIndex2, ThreadSession, ThreadIndex collection of Search Assets

As the Message Cycle progresses around the ring and implementation proceeds, Search Session assets increase. Assets continue to
participate in on-going search and require maintaining and updating Search Sessions. Follow-up on the information gathered and
maintain it with additional material relating to the SearchKey or Search_Desc.

The secret to success uses common folders at the Single Point of Entry. Unified folders simplify filing and retrieval. Each media
organizes project files, project files for internal improvement of the infrastructure, and files to store the yearly collection of
SearchIndexes and ThreadSessions. A search session may index email, Internet or document contacts. Accessing the SQLite
database produces the index records.

Workflow Methods automate Search Session Threading

Table SearchIndex2 contains all contacts encountered on the path around the rings. Use this table to pick and assemble contacts to
build threads and extend projects. [QR] defines and discusses use of Standard Operations. Use the field SStandOp and automate
building threads. Transaction Search Session does the work of copying the details from SearchIndex2 to the records in tables
ThreadSession and ThreadIndex.

Workflow to Assemble Transaction Search Sessions from Table SearchIndex2

Search Sessions collect (unordered) material. Assemble the material to enable referencing, cross-referencing and integration into
threads. The following operations change the information assets in the database. Make at least two backups of the assets before
approving and releasing the changes. The entered information will not rollback to a previous entry.
 Pick and select suitable sessions for a current topic or thread
 Use SELECT LIKE to find suitable and qualified Search Sessions. List them using the command.
 SearchKey fields and Search_Desc fields may be similar use a Diff Operator to find identical records or the different ones.
Compare the fields SearchKey and Search_Desc.(Duplicates)
 Duplicate Function.
SELECT all Search Sessions with SearchKey LIKE '%TERM%' where TERM equates to the target SearchKey
SELECT all Search Sessions with Search_Desc LIKE '%TERM%'
List an index into TEMP with all SearchKey and rowid then compare the target with this list.
 Examine the Search Sessions for suitability and choose potential sessions with assets.
 Mark the Search Path to register and qualify sessions when changing the Search Key and adding to it.
 Use a SStandOp trigger to create new Search Path entries to record Search Sessions that were examined.

Filter Sessions and choose Candidates for use as assets in threads or projects.
 Use SearchKey and SearchDescrip Search LIKE to find an list possible asset candidates.
 Refer to the listed sources to review the material.
 Mark the Search Sessions with qualified material.

Assemble the filtered Search Sessions and Candidates into Threads

 Pick the suitable Thread Index
 Create a suitable Thread Index
 Create Thread Sessions for the Search Sessions linked to the Thread Index by using SQL Execution

Methods for smooth Workflow in Search Session Workflow

These methods apply in the Search Session and in the Facet as well. To avoid duplication and achieve a compact text; they focus on
use in the Search Session at this point. They are explained in more detail in Transaction Search Session.

Method “T”
Method “T” is useful and recommended to generate a complete Thread.
 Enter the information in SearchIndex_temp.
 Enter “T” in SStandOp to create a ThreadIndex_temp from the information entered in SearchIndex_temp.
20091pub_10SyDbSessThreadProof2.doc 07.12.21 -7-
  This creates a new ThreadIndex_temp automatically.
 Go to the new ThreadIndex_temp and enter “TS” in TStandOp which creates a new ThreadSession based on the
information entered into ThreadIndex.
You are finished and threaded the new assets.

Method “TS”
If a ThreadIndex has not been established use this method to create a SearchIndex and the qualified ThreadSession.
Complete SearchIndex and enter “TS” in SStandOp to create a ThreadSession from the information. This creates a new
ThreadSession automatically.
New qualified resources have been added to the database.

Advantages of the Methods

Apply TS when the thread content has not yet been identified. Use Method T to save time and eliminate routine. It creates a thread
and then a ThreadSession from the thread. Search Session tables of SearchIndex, ThreadSession and ThreadIndex and those in
Transaction Search Session use identical workflow methods.

Transaction Search Session. Use Facets to Qualify potential Information Resources in Threads

Figure 2 ThreadSession Qualification in SQLite Manager

Example: Firefox causing 100% CPU Utilization over extended Periods

Firefox while proven in use requires maintenance and tuning to reduce search interruptions. Intensive use of Firefox to solve Project
Management problems resulted in CPU utilization of 100% which blocked the PC for long periods of time. Work efficiency
dropped and left things to do at day’s end increasing frustration. Technically the problem is difficult because Firefox sits at the
intersection of a number of components including the PC Operating System, Internet linking and server media. Where did the
problem lie and how could it be solved to accomplish the day’s tasks? SearchKeys were defined and entered to find others with the
problem and possible solutions. As the search progressed these contacts were qualified. Continue to see an example of the search
results and how the problem and solution qualified. Searching indentified multiple resolutions including disabling the Flash plugin,
removing Google Desktop search, and quieting XP automatic update.

20091pub_10SyDbSessThreadProof2.doc 07.12.21 -8-

FACET of “Firefox 100% CPU Utilization”

Construct threads and thread sessions by using SearchIndex2 as potential information resources for use in development, research
and projects. Transaction Search Session selects candidate contacts and ThreadSessions to build threads and use in project support.
Build ThreadIndexes and ThreadSessions to contribute to project management and Issue Resolution. Use a term to SELECT
potential search contacts to find contacts to benefit the activity. Search Session takes contacts complying with the search term or
SearchKey, Search_Desc and presents them in an information grid. Enter the commands to use the contact information to build
threads or thread sessions. Using the entry commands also works to maintain threads and the thread sessions by editing them,
adding or deleting them from the database. Work in a temporary table which means that only after entering approval does the data
in the database change according to the entered information. It reduces the entries to the facet of the SearchKey.

Transaction Search Session

Transaction Search Session creates facets for SearchIndex2, ThreadSession and ThreadIndex and focuses the contacts based on the
entered SearchKey or Search_Desc. In the example it creates a family of temporary tables displaying potential resource candidates
for the SearchKey. Built as an SQL application; it installs easily as SQL execution “Select a Query” in SQLite Manager or as an
SQL script for most other wrappers. Obtain a Free Source Version by using the link at the end of the article. It builds the tables and
views for the Search Session and populates them with information filtered by the facet.

Use SearchIndex_Lookup_Temp Table to List Session Resources in a Lookup Table

To shorten the user introduction the first phase uses a standard SQLite Data Grid for the queries. Data enteres directly in the tables.
During the second phase a GUI improves data entry with a form built to facilitate flow. The first phase Lookup_temp displays the
facet search terms entered by the user which contradicts typical use and is somewhat cumbersome.

A Lookup Table lists the candidates from SearchIndex2. These candidates relate by the SearchKey. Enter interesting SearchKeys in
SearchIndex_Lookup_temp table and the matching candidates from SearchIndex2 list in SearchIndex_temp. Listing the candidates
enables the user to insert a search term and observe the stored resources that relate to the term. Modify and adapt the term to
optimize the combination and scope of potential resources.

Create SearchIndex_Lookup_temp to list SearchKeys. User inserts search terms into table SeachIndex_Lookup_temp with wild
cards. Matching resources insert into SearchIndex_temp, ThreadIndex-temp and ThreadSession_temp by using
SearchSessionTrig_ThreadIndexTMP_ThreadSessionTMP.

Insert a search term as SearchKey into the lookup table. Use the LIKE or matching operators (%, ) to load a list of matching search
indexes in SearchIndex_temp. Use these SearchIndexes to generate a list of information resources for Thread Indexes and Sessions.

Maintain Threads using Workflow Methods

Maintain and build information assets with Transaction Search Session . Make at least two backups of the assets before approving
and releasing the changes. Later the GUI will automate the backup for the user. The entered information does not rollback to a
previous entry in case of erroneous storage. Workflow Methods “T” and “TS” from the Search Session apply in Transaction Search
Session. When the new contacts contain a ThreadIndex use Method “T” because it adds a ThreadIndex and the indexing terms.
Adding ThreadSessions uses Method “TS”.

Standard Operations to manipulate Contacts

In each table field StandOp stores Standard Operations.

 Enter "U" to update entries. After entering the command the database changes to match the entered information.
 Enter "I" to INSERT a new record with the information from the contact.

Method “T”
Method “T” is useful to generate a complete Thread. It is the recommended method because it generates threads linked by the
TIndexId which is the threading id. It also relates any ThreadSessions or ThreadIndexes to the originating SearchIndex.
 Start with the SearchIndex_temp and enter the record information. Create a new record in the database by copying the
record after entering “I” in SStandOp. Enter “Ref” in SStandOp to refresh the new id number.
 Enter “T” in SStandOp to create a ThreadIndex_temp from the information entered in SearchIndex_temp. This creates
a new ThreadIndex_temp automatically.
 Go to the new ThreadIndex_temp and enter “I” in TStandOp. It inserts into the database. Enter “Ref” to refresh the
ThreadIndex_temp id.
 Create a new ThreadSession_temp based on the previous SearchIndex and ThreadIndex by entering “TS” in
TStandOp.
 Go to the new ThreadSession_temp and enter “I” in TSStandOp to insert this record in the database. Refresh the id
number with “Ref”.

20091pub_10SyDbSessThreadProof2.doc 07.12.21 -9-

Using “I” to insert the record in the database acts as an approval system and releases the record from the temporary to the actual
database. If a temp record is not to be used, then do not insert it.

Method “TS”
If a ThreadIndex has not been established use this method to create a SearchIndex and the qualified ThreadSession.
 Start with the SearchIndex_temp and enter the record information. Create a new record in the database by copying the
record after entering “I” in SStandOp. Enter “Ref” in SStandOp to refresh the new id number.
 Enter “TS” in SStandOp to create a ThreadSession_temp from the information entered in SearchIndex_temp. This
creates a new ThreadSession_temp automatically.
 Go to the new ThreadSession_temp and enter “I” in TSStandOp. It inserts into the database. Enter “Ref” to refresh the
ThreadSession_temp id.

Workflow Balance
Edit Information Resources in a Facet or use the Search Session. Temporary tables and main tables achieve a working balance. Edit
SearchIndex, ThreadIndex and ThreadSession in the Search Session. Focus the view by using a Facet and manipulate the contacts in
Transaction Search Session. Temporary tables are balanced to allow the user to choose between working in the temp or main tables.

Logging processed records

Table id and id number for all record entries processed with "U", "I", "D" log in table SearchIndex_Tran1 in the database
SearchIndex2. Should a previous value be necessary; return to an earlier backup of the database and export the needed value and re-
import it into the database. Leave unapproved ThreadSession_temps in the temp table and leaving the table erases them.

Example of Smooth Workflow to complete Threads in Transaction Search Session

ERUNT is a system management tool for Windows to backup the registry. Searching in the database found no entries and the tool
will be installed in the next week. Obviously this produces a complete thread including SearchIndex, ThreadIndex and
ThreadSession. Start in the _temp table to generate the thread from start to finish.
Create a complete thread
 Open SI_temp by entering at least SearchKey and Search_Desc.
 Enter "I" to INSERT the record to SearchIndex2.
 Enter "Ref" to refresh the SIndexId from SearchIndex2.
 Generate the ThreadIndex_temp from SearchIndex_temp with SStandOp= "T".
 Go to ThreadIndex_temp and enter "I" to make a new ThreadIndex.
 Refresh the TIndexId in ThreadIndex_temp by entering "Ref" in TStandOp.
 Enter "TS"In ThreadIndex_temp TStandOp to create the ThreadSession.
 In ThreadSession_temp enter "I" inserting the -temp to ThreadSession.
 Update ThreadSession_temp with the TSIndex by using "Re"

Combine 1. Transaction Search Session Refresh. Edit SearchIndexes and Threads and add Resources.

Looking at the contents of SearchIndex_temp may generate ideas for the user and include a complete SearchIndex and thread. This
idea generates ThreadIndex and the connected sessions.
Add Threads in _temp
Create SearchIndex_temp by adding
Mark "I" Inserts SearchIndex_temp into SearchIndex2 "Ref" refreshes SIndexId
Create ThreadIndex_temp
Mark "T" Inserts ThreadIndex_temp into ThreadIndex without TIndexId Mark=rowid "Ref" refreshes ThreadIndex_temp
with TIndexId from ThreadIndex
Create ThreadSession_temp
Mark "TS" Inserts ThreadSession_temp into ThreadSession without TIndexId, TSIndex Mark=rowid UPDATE TIndexId
"Ref" refreshes ThreadSession_temp with TIndexId, TSIndex from ThreadSession

Display ThreadSession SearchIndex SearchGrid

Recording a search session begins with selecting the suitable SearchKey and choosing the qualified activity. ThreadSession
SearchIndex SearchGrid lists these contacts matching the Searchkey in SearchIndex_Lookup_temp. Look in the SearchKey column
to find a matching contact. It offers the choice of entry in an open ThreadSession or SearchIndex. It also contains the TIndexId if a
thread has been opened.
Find open ThreadSessions or SearchIndexes for a selected SearchKey.
 Identify the topic in SearchKey
 Determine if a ThreadSession has been opened for that topic.
 Find SIndexId or TSIndex for the topic to refer and locate or browse to the record (for editing).
 If the ThreadSession has an entered TIndexId, a ThreadIndex has already been opened and it has been assigned to it.

20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 10 -
Reducing Hesitation. Assign ThreadSessions to Threads
The most frequent cause of hesitation is not knowing where to insert contacts or where to combine them. Views line up the threads
with the members and the user sees what ThreadSessions have been threaded, and which are open. Showing the qualified contacts,
the user also decides where to connect the contact. Fig. 3 shows contacts assigned to a thread with a TIndexId or ThreadSessions
(TSIndex). Unassigned contacts color red.

Threading assigns ThreadSessions to a ThreadIndex.

Maintenance for ThreadIndex includes creating a ThreadIndex from ThreadSession or correcting the TIndexId in a ThreadSession
attaching it to the right thread relationship where the terms in SearchKey fit. For parentless ThreadSessions, TIndexId-less
ThreadSession, assign them it to parentage and give it a relationship to a ThreadIndex with a fitting relationship in SearchKey.

Figure 3. ThreadAssign. Assign contacts to threads.

Threading. Attaching ThreadSessions to ThreadIndexes

Threading attaches ThreadSessions to ThreadIndexes by entering the ThreadId (TIndexId) into the ThreadSession. Principally
SearchIndex, ThreadIndex and ThreadSession should identify and be found by sharing SearchKey or PN (Similar terms=
Search_Desc)

ThreadIndexes collect and organize Threads

Browsing identifies contact relationships. These relationships network ThreadSessions into threads. Networking opens a
ThreadIndex or uses an existing one to assign the ThreadSession to it. SearchIndexes also qualify as ThreadSessions that then open
and attach to the ThreadIndexes. During browsing set up ThreadIndexes that collect ThreadSessions into topics to feed the
activities.
Organize the ThreadSessions by dividing them up and assigning them to ThreadIndex for easy use of the assets.
Open ThreadSession and SearchIndex for entry during browsing and use for later reference.
ThreadAssign offers support in identifying which threads offer resources for ongoing activities.
It helps answer what ThreadSessions contribute to the project management issues at hand.

Improvement to Organize Browsing Content Inline

Browsing turns up tidbits on not just the focus search terms, but other terms as well. Catalog these contacts and combine them with
topical contacts. Searching often complements content or material of previous search sessions. It expedites later use of the material
if information details add to the search session. Information scatters over all if details end up in a long list without cataloging them
in a topical search session. However it disrupts the search flow to look for the related search session.

Example of cataloging SearchIndexes and ThreadSessions in a search with the query “SearchKey LIKE SQLite” and observe how
the term SQLite integrates applications. How do online search results add to documented sessions?
Searching found a good tutorial for SQLite that was previously visited and probably saved somewhere. The new tutorial combines
with the tutorials already documented. It compliments it.
This adds to material already processed. Has it already been recorded? Where has it been recorded?
Example: Introduction to SQLite (C programming, C Code). How can the previously processed information be found and
annotated?
Query: SELECT SearchKey, Search_Desc from SearchIndex2 WHERE Search_Desc LIKE 'Introduction to SQLite' why
did this query not work. The successful query used the web address. http://www.fredshack.com/docs/sqlite.html
Entering terms to find the information when needed.
Modify and expand the SearchKey to include new queries and point to information contained in the session but perhaps
somewhat unrelated to the specific topic. This has the risk of producing search results mixing topics and including
unrelated items in the search results. Enter the information search terms or name, http in Relate_Sterm.

20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 11 -
Reduce Interruption in Search Session Path History
Most sessions begin by searching for suitable contacts to store information or the right contacts to extract information. Hesitation
occurs when resolving or qualifying the contact potential. Interruption occurs when threading and assigning to a suitable thread.
Listing encountered contacts; the Search Path is a history of the use of Information Resources. Almost any action begins by looking
for the right Information Resources to do the job. Proven spiral principles show that contacts tend to repeat within a time period on
the path. As the Message Cycle progresses around the ring; it utilizes first the properties (Activity, Information Resources) around
the slot. Using the present to define a point or slot on the path; most likely needed assets will store within an immediate range about
the present. Similarly incoming contacts tend to repeat the content and store in similar topics. Use these properties to speed up filing
and retrieval along the Search/ Spiral Path. Each Search Session automatically records incoming contacts as well as changes in
records to give the user a list of the search contacts. Use this Search Path History to reference recent and most probable contacts.
Experience confirms the spiral properties and first looking at recent contacts satisfies most needs for assets.
Use of spiral properties facilitates storage of information
contacts, resources and assets. Using the "Spiral
Desktop" recognizes that contacts within a period tend to
remain similar and to repeat themselves. Referring to
Search Path History, recent contacts and Thread Sessions
reduces time needed to locate specific topical points.
Find qualified contacts quickly within this period. If the
contact is qualified for use but is not yet qualified, use a
query to list ThreadSessions to decide where the contact
threads.
If the contact has already been qualified; then use a
query to resolve ThreadSession and project contacts.
Activities often reference immediately preceding ones.
Make search faster by listing previous contacts for
choice.
Search Session Path makes a consecutive list of changes in
inserting or editing records. Refer to this list to find the current
associations and relationships.

Search Path Grid contains records taking up info in the

SearchKey or Search_Desc. Maintaining a view of Search Path
Grid displays records adding and modifying information
resources. Observing these changes within a current range offers the most probable contacts for Issue Resolution and problem
solving. Reference items in the Search Path to find current items for prompt lookup. Maintain a table of Search Path, and
Transaction items to cut down search time. The SearchIndex_Trans_Grid offers another view of contacts participating in
transactions. It lists the changes in Standard Operations including insertions, updates and deletions. Referring to these operations
within the current period will also often shorten search time and lead to suitable problem solutions or resolutions.

Mathematical Model of Ulam Spiral in Communication and Growth

Ulam Spiral includes all integers without duplication and without missing any. Mathematics shows a system of continuous growth
with excellent potential for team based communications structures that minimize needed resources, have short paths and reduce to
the essential. Studying the mathematics confirms that using the model provides essential functionality with minimal resources and
the assurance that missing functionality will not impede future use. Further it demonstrates no need for parallel or complementary
systems to maintain growth but uses localized resources to sustain development.

Meeting Ulam Spiral as a guide starts at what the Theorem of Inclusion/ Exclusion [TIE] calls the Inclusion or origin. The Inclusion
defines the properties used to build the spiral and to include properties to ensure responsiveness to customer needs. The Proof of
Concept built the Internet Messaging Single Point of Entry as the Inclusion. Continuing expansion; the spiral replicates the
Inclusion and attaches it to the right side. It surrounds the Inclusion with replicate squares. As it attaches; each square is assigned a
number that increments by one from the previous one. The last square meets and closes with the first and constructs a ring.
Subsequent expansions continue adding rings to the Inclusion. As long as each additional square replicates the Inclusion; a vertical
spiral grows ensuring a communications and information structure suited for team needs. 8 spiral vertexes form at the diagonals and
axis of the Inclusion. These vertexes connect the rings. Each square in the ring is a slot and connects either to a vertex or vertically
to the next ring. The midpoint of each ring connects to a huge backbone ensuring an efficient vertical flow. Mathematically this
structure is interesting because it displays information about primes. Primes are integers that are only multiples of one and
themselves. Looking it from the side reminds of a slender, filigree structure standing on the Inclusion. Supporting the rings with
wonderful, slender silver risers it strives upwards in a breathless balance.

Threading uses spiral principles to control flow of the Information

Resources to provide timely retrieval and integration for team Figure 4. Ulam's Spiral
members. Modeling the contact processing after Ulam´s Spiral
communication; contacts enter the Single Point of Entry corresponding to the spiral origin. They continue to collect and store on a

20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 12 -
path analogous to the path climbing the spiral. Each slot in the spiral positions is given by the two independent coordinates (x,y).
Information contacts collect according to the coordinates Activity or project, and Information Resource. Need for targeted, qualified
information precludes each successful project activity. As the contacts continue to collect they build a spiral structure with vertexes,
rings and slots. Project Management uses a complete ring to organize a major project or business year. The ring opens with projects
connected to another until finally to close and open a new ring. Vertexes establish major focal points.

Communications qualities of the spiral structure support responsive team efforts. All slots start from the origin and replicate the
original properties. A ring connects the projects and shares knowledge and experience. A slot in the ring connects to other team
members through the exchange of useful information. Threads connect slots vertically below and above ensuring rapid vertical
connection of rings. Vertexes connect all rings vertically and also ensure adequate exchange of experience. The spiral has a large
central backbone rising from the origin that connects all rings and is a major communication tributary. Exploitation of the multiple
and redundant communication paths offers reliable and responsive communication between team members and customer
organizations.

Limitations
Single Point of Entry. Mozilla Firefox and Thunderbird excel for individual users. Tests demonstrate successful networking of
Firefox and Thunderbird as well as the extensions. Extended tests also demonstrate reliability. However networking performance to
network teams tends towards minimal levels. Network administration is minimal almost inadequate. Priorities expressed by product
development do not indicate improvement in performance and administration. Thunderbird 3 files are not compatible with
Thunderbird 2 limiting the openness of the product. Producing a messaging infrastructure would significantly improve suitability
for this application.

SQLite is an SQL database engine offering reliable, fast and proven storage primarily dedicated applications. It does not support
clients as a server. Limited to single write access; it limits the number of users writing and reading the database. It is not suitable
and does not function as a database server for large networks. Spiral communication paths reduce network traffic and localize it.
Additionally team members in a spiral configuration tend to focus on local, individual activities that only marginally touch
neighboring areas of responsibility which also limits traffic and access. Using defined search terms identifies networked resources
within the network and the resources forward based on need. Central data storage and access reduces in priority. Product flexibility
offers migration paths.

Workflow Methods. Wrappers are not adequate for the Search Session application. They serve as a test vehicle. A GUI simplifies
and automates refreshing the id in Method “T” and “TS”. It saves the user one step.

User training. Application of a spiral model produces enthusiastic results. However it requires significant user understanding in the
use of the principles in business applications. Using spiral facets brings improvements in flow and reductions in hesitancy and
interruption but require an investment in user practice and understanding to utilize and optimize workflow.

For security reasons Internet online use is not supported. Designed to store critical and sensitive information; this application relies
on the security of control in desktop and network use. Any information transmitted online should be selected and transmitted..

Next Generation

20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 13 -
Figure 5 Next Generation complements the Data Grid with a Resource Editor for the User
The next generation is currently under development and test. It adds a Resource Editor to complete the Data Grid. Users will have
fewer hesitations and interruptions in entry. organization and cataloging. It focuses on resource improvement.

Free Source of Transaction Search Session

Bibliography
Strategic Business Development, Sales Cycle Management

[QR] Gabriel, Gary. 2008. “Quick Reference to Sales Cycle Management Objects to driving Strategic Business Development
Aggregates”. Scribd. http://www.scribd.com/doc/9672319/Quick-Reference-to-Sales-Cycle-Management-Objects-to-drive-
Strategic-Business-Development-Aggregates.
URL: >>>

[BIA] Gabriel, Gary. “2008 Building Information System Aggregates to drive Strategic Business Development Team Resources”.
Scribd. http://www.scribd.com/doc/9629093/Building-Information-System-Aggregates-to-drive-Strategic-Business-Development-
Team-Resources
Start by asking the right questions and channel the answers to progress the team
URL: >>>

[SSCM] Gabriel, Gary. 2008. “Streamlining Sales Cycle Management with Internet Messaging. Scribd”.
http://www.scribd.com/doc/9643637/Streamlining-Sales-Cycle-Management-with-Internet-Messaging. Data Object definitions
participating in the Message Cycle and examples. Strategic Business Development employs the entire scope of business resources
within a dedicated, compact team.
URL: >>>

[LCDO] Gabriel, Gary. 2009: “Lead and Contact Data Objects, Transactions and Views participating in Sales Cycle Management”.
Scribd. http://www.scribd.com/doc/12320899/Sales-Cycle-Lead-Management .

Internet Messaging

[MTD] Gabriel, Gary. 2008. “Configure Mozilla Firefox and Thunderbird to share Project and Team To-Dos and simplify Follow-
up”. Scribd. http://www.scribd.com/doc/8497756/Configure-Mozilla-Firefox-and-Thunderbird-to-share-Project-and-Team-ToDos-
and-simplify-Followup .
URL: >>>

[IMC] Gabriel, Gary. 2008. “Configuration Guide to share Team and Project To-Dos and Follow-up for Mozilla Thunderbird and
Firefox”. Scribd. http://www.scribd.com/doc/9189210/Configure-Mozila-Firefox-and-Thunderbird-for-ToDos-and-Followup
>>>

20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 14 -
Start with this configuration guide and end with shared To-Dos in Internet Messaging using the Mozilla components

[IMB] Gabriel, Gary. 2008. “Basics of sharing To-Dos and Follow-up with Mozilla Thunderbird and Firefox. Improve Web
Research and Project Management”. Scribd. http://www.scribd.com/doc/8892628/The-Basics-of-sharing-ToDos-with-
Mozilla-Thunderbird-and-Firefox-Followup-Project-Management .
Development of Internet Messaging and how it supports Project Management and Web Research
URL: >>>

[MOZ] Gabriel, Gary. 2008. “Configure Mozilla Firefox and Thunderbird to share Project and Team To-Dos and simplify Follow-
up”. Scribd. : http://www.scribd.com/doc/8497756/Mozilla-Firefox-and-Thunderbird-simplify-the-Followup-of-ToDos

References

[RSPOE] Gabriel, Gary. 2009. “Reference for Views, Data Objects and Transactions at the Common Point of Entry in Sales Cycle
Management Processing”. Scribd. http://www.scribd.com/doc/13488933/Reference-for-Linking-Views-Data-Objects-and-
Transactions-at-the-Common-Point-of-Entry-in-Sales-Cycle-Management-Processing
Message Cycle.

Ulam´s Spiral

[MW1] Weisstein, Eric W. "Prime Spiral." From MathWorld--A Wolfram Web Resource.
http://mathworld.wolfram.com/PrimeSpiral.html

[NS] NumberSpiral.com. 2010. http://www.numberspiral.com/

[NS] Introduction

[US] Ulamspiral.com 2010.

[US] A visual analysis of prime number distribution http://ulamspiral.com/generatePage.asp?ID=1
Software http://ulamspiral.com/generatePage.asp?ID=5
Links http://ulamspiral.com/generatePage.asp?ID=19
Contact http://ulamspiral.com/generatePage.asp?ID=17

[TIE] Theorem of Inclusion/ Exclusion

[SUS] Spiral Action Principle drives Ulam’s Spiral

Web

Tclers Wiki. 2010. Ulam Spiral Demo. Updated 2009-04-02 http://wiki.tcl.tk/23052 UlamSpiral_demo.tcl
Tclers Wiki. 2010. Ulam spiral. Updated 2004-05-03. http://wiki.tcl.tk/11363. Primes in Ulam Spiral.

Glossary
Key Terms in
- Sales Cycle Management makes use of spiral principles to optimize Information Resources. It adapts the 3 Aggregates to
obtain responsiveness to customer needs and demands.
- Internet Messaging builds a Single Point of Entry to incorporate all incoming contacts. It sorts and stores the content of
these contacts for prompt use.
- Message Cycle
- (user experience) Inline means that at the end of the Search Session all potential contacts have been categorized, stored and
filed. Inline flow prevents distractions of hesitations and disruptions that distract the user from following the search logic.
However it does not prevent from following branching logic.
20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 15 -
 - Search Session files and stores all potential contacts from Internet, email or documents encountered when engaging and
searching for information to satisfy questions, issues or problems.
- ThreadSessions qualifies the contacts and evaluates potential use of the content.
- Threading takes the qualified content and organizes the content to address questions, issues or problems.
- Coherence. Discrimination and resoulution.
- Catalog, cataloging
- Laterally connected, networked. Neighboring slots contain similar and related information and the similarities connect
laterally. Cross referencing.
- Project Implementation. Project management assembles threads to apply to project goals and use in addressing problems
encountered during the implementation.
- Information Resources
- Information Assets
- Inline filing, storage and cataloging.
- Resource Editor.
- Facet. A facet uses search terms to focus and display the Search Session.
- Ulam Spiral
- Information Management
- Minimal, essential, responsive
- Potential, ways, solutions

20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 16 -
Appendix 1 Facet as a simple Report of the Evaluation of Meta Tags and Bibtex
SIndexId Searchkey
193 Dublin Core Metadata Initiative Dublin
core metadata template Dublin Core
Viewer
340 dublin core metadata editor Dublin core
metadata generator Dublin Core
Metadata Template
341 rdf dublin core html syntax Embeddable
RDF Bibliography citations
460 Bibtex SQLite Bibliography Citations
463 Dublin core DC-Text format
563 Bibtex SQLite Bibliography Citations
20091pub_10SyDbSessThreadProof2.doc 07.12.21
Search_Desc
The Dublin Core® Metadata Initiative. http://www.dublincore.org/
Firefox Dublin Core Viewer Extension. http://dublincore.org/tools/tools/tool-8.shtml
Dublin Core Viewer 0.6 firefox 1.5- 3.5. Displays Dublin Core Metadata embedded in HTML/XHTM
documents with META and LINK elements (as per http://www.dublincore.org/documents/dcq-ht
https://addons.mozilla.org/en-US/firefox/addon/528.
dublin core metadata editor
(software?) DC.MetadataGen http://webposible.com/utilidades/dublincore-metadata-
gen/index.php?lang=en
Dublin Core metadata editor http://www.ukoln.ac.uk/metadata/dcdot/
Dublin Core Metadata Template http://www.ad.jyu.fi/users/a/ankarjal/ITKD50/Dublin%20Core
%20Metadata%20Template.htm
Nordic Metadata Project Homepage http://www.kansalliskirjasto.fi/extra/muut/meta/
rdf dublin core html syntax
RDF Sitemaps http://www.ilrt.bris.ac.uk/discovery/rdf-dev/purls/papers/sitemap/
RDF Site Summary 1.0 Modules: Qualified Dublin Core
http://web.resource.org/rss/1.0/modules/dcterms/
(+) Dublin Core Viewer 0.8 FF 1.5- 3.6 https://addons.mozilla.org/en-US/firefox/addon/528 Firef
dublin core viewer extension description: http://www.splintered.co.uk/experiments/73/ A Mozi
Firefox extension that adds a button to the status bar (and optionally the toolbar) to access a list
Dublin Core metadata embedded in HTML and XHTML documents with META and LINK elements
[1064]
SearchTools.com: Background Topics Meta Data and Search
http://www.searchtools.com/info/metadata.html
Constructing Web subject gateways using Dublin Core, the Resource Description Framework and
Topic Maps http://informationr.net/ir/11-2/paper248.html
(+) Rdf In Html Embeddable RDF http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml
(+) RDFa http://en.wikipedia.org/wiki/RDFa
SEO with Dublin Core http://www.criticism.com/seo/dublin-core-metadata.php
Bibliography Citations
Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata
http://dublincore.org/documents/dc-citation-guidelines/index.shtml
Bibtex SQLite Bibliography Citations
Mendeley http://www.mendeley.com/faq/
Mendeley RE: Zotero to Bibtex to Lyx: A Problem not a baseball play
John Kane http://www.mail-archive.com/lyx-users@lists.lyx.org/msg78601.html
Zotero two way sync http://feedback.mendeley.com/forums/4941-mendeley-
Dublin core DC-Text format Expressing Dublin Core metadata using the DC-Text format
http://dublincore.org/documents/dc-text/index.shtml
Bibtex SQLite Bibliography Citations
EndNote web is a web-based product available to MIT users as part of the Libraries’ subscription
Web of Knowledge.
- 17 -
Technology Evaluation: Dublin Core Metadata Bibtex
SIndexId: 193 | SearchKey: Dublin Core Metadata Initiative Dublin core metadata template Dublin Core
Viewer
The Dublin Core® Metadata Initiative. http://www.dublincore.org/
Firefox Dublin Core Viewer Extension. http://dublincore.org/tools/tools/tool-8.shtml
Dublin Core Viewer 0.6 firefox 1.5- 3.5. Displays Dublin Core Metadata embedded in HTML/XHTML documents with META and
LINK elements (as per http://www.dublincore.org/documents/dcq-htm.. https://addons.mozilla.org/en-US/firefox/addon/528.
SIndexId: 337 | SearchKey: Rtf editor reader Firefox Tags Page annotations Dublin Core Meta Data
Rtf editor reader Firefox Tags
Firefox ext RDF Viewer 1.3 https://addons.mozilla.org/en-US/firefox/addon/2006 FF 2.0
Dublin Core NeViewer 0.4 https://addons.mozilla.org/en-US/firefox/addon/4418 Firefox plug-ins Operator and Dublin Core
NeViewer XHTML-RDF Template - Thomas Legg's Geek Blog. 2009_ProjectStoreSearch
Dublin Core Viewer 0.8 https://addons.mozilla.org/en-US/firefox/addon/528
Expressing Dublin Core in HTML/XHTML meta and link elements http://www.dublincore.org/documents/dcq-html/
Use bookmarks to tag pages. Tagsifter. Record info in the bookmarks.
Fark messages. Fark Tags. Farkode. It is based on the excellent BBCode, but is trimmed down and tailored ...
MetaTags displays page meta tag info.
Clippings. Save frequently-entered text for pasting later.
Keyword Box provides capabilities similar to Firefox's bookmark keywords
Site Information Tool. Provides information about a webpage (or website) including rankings, domain registration data (whois),
IP information, server response and page data, thumbnail and more.
SIndexId: 340 | SearchKey: dublin core metadata editor Dublin core metadata generator Dublin Core
Metadata Template
dublin core metadata editor
(software?) DC.MetadataGen http://webposible.com/utilidades/dublincore-metadata-gen/index.php?lang=en
Dublin Core metadata editor http://www.ukoln.ac.uk/metadata/dcdot/
Dublin Core Metadata Template http://www.ad.jyu.fi/users/a/ankarjal/ITKD50/Dublin%20Core%20Metadata%20Template.htm
Nordic Metadata Project Homepage http://www.kansalliskirjasto.fi/extra/muut/meta/
SIndexId: 341 | SearchKey: rdf dublin core html syntax Embeddable RDF Bibliography citations
rdf dublin core html syntax
RDF Sitemaps http://www.ilrt.bris.ac.uk/discovery/rdf-dev/purls/papers/sitemap/
RDF Site Summary 1.0 Modules: Qualified Dublin Core http://web.resource.org/rss/1.0/modules/dcterms/
(+) Dublin Core Viewer 0.8 FF 1.5- 3.6 https://addons.mozilla.org/en-US/firefox/addon/528 Firefox dublin core viewer extension
description: http://www.splintered.co.uk/experiments/73/ A Mozilla Firefox extension that adds a button to the status bar (and
optionally the toolbar) to access a list of Dublin Core metadata embedded in HTML and XHTML documents with META and LINK
elements. [1064]
SearchTools.com: Background Topics Meta Data and Search http://www.searchtools.com/info/metadata.html
Constructing Web subject gateways using Dublin Core, the Resource Description Framework and Topic Maps
http://informationr.net/ir/11-2/paper248.html
(+) Rdf In Html Embeddable RDF http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml
(+) RDFa http://en.wikipedia.org/wiki/RDFa
SEO with Dublin Core http://www.criticism.com/seo/dublin-core-metadata.php
Bibliography Citations
Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata http://dublincore.org/documents/dc-
citation-guidelines/index.shtml
SIndexId: 460 | SearchKey: Bibtex SQLite Bibliography Citations
Bibtex SQLite Bibliography Citations
Mendeley http://www.mendeley.com/faq/
Mendeley RE: Zotero to Bibtex to Lyx: A Problem not a baseball play
John Kane http://www.mail-archive.com/lyx-users@lists.lyx.org/msg78601.html
Zotero two way sync http://feedback.mendeley.com/forums/4941-mendeley-feedback/suggestions/372255-zotero-2-way-sync
Software to keep your PDFs and papers organized http://bytebaker.com/2009/06/26/software-to-keep-your-pdfs-and-papers-
organized/
SiSu http://www.sisudoc.org/sisu/sisu_manual/sqlite.html
SIndexId: 461 | SearchKey: Latex Bibtex Miktex TexNic Tutorial
Latex Bibtex Miktex TexNic Tutorial
SIndexId: 462 | SearchKey: Bibtex sxntax Bibtex comments
Bibtex sxntax Bibtex comments

20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 18 -
Bibtex comments (+) A summary of BibTex http://artis.imag.fr/~Xavier.Decoret/resources/xdkbibtex/bibtex_summary.html
BibTeX http://www.cs.arizona.edu/~collberg/Teaching/07.231/BibTeX/bibtex.html
SIndexId: 463 | SearchKey: Dublin core DC-Text format
Dublin core DC-Text format Expressing Dublin Core metadata using the DC-Text format http://dublincore.org/documents/dc-
text/index.shtml
SIndexId: 563 | SearchKey: Bibtex SQLite Bibliography Citations
Bibtex SQLite Bibliography Citations
EndNote web is a web-based product available to MIT users as part of the Libraries’ subscription to Web of Knowledge.

20091pub_10SyDbSessThreadProof2.doc 07.12.21 - 19 -