Isri99 02

A Comparison of Livelink 8 with DOE/LSN Requirements
ISRI Sta
Te hni al Report 99-02

Information S ien e Resear h Institute
University of Nevada, Las Vegas
May 3, 1999
1 Introdu tion
The following do ument reviews Opentext's Knowledge Management System, Livelink 8, with respe t to the
Department of Energy's (DOE) sear h and retrieval requirements for the Li ensing Support Network (LSN).
We used a \hands-on" evaluation to determine how losely this system meets ea h requirement.
1.1 Company and Produ t Information
Livelink is a produ t of Open Text Corporation whi h is publi ly traded on NASDAQ. The ompany was
founded in 1991 and has made several a quisitions to establish itself as one of the major providers of ap-
pli ation software for do ument management. Sin e the a quisition of Information Dimensions in 1998, the
ompany se ures 42.7% of the market share of worldwide enterprise do ument management installations.
Livelink applies a web-based interfa e and modular ar hite ture to provide a ollaborative working environ-
ment for enterprise do ument management, information retrieval, work ow and proje t ollaboration, and
enterprise group s heduling apabilities.
Livelink software requirements in lude:
Nets ape Enterprise Server 3.51
Nets ape Navigator 4.05 and/or Internet Explorer 4.01 with SP1
One of the following relational database systems: Ora le, Sybase, or Mi rosoft SQL
2 Colle tion Preparation

Livelink depends on the Internet and the World Wide Web (WWW) for general and publi a ess to its
do ument management system. The most ommon interfa e for the user of the Li ensing Support Network
will be a web browser. Browser apabilities together with the exibility of manipulating the system's interfa e
and the resour eful use of HTML will di tate how the LSN olle tion should be prepared for loading.
System administrators should thoroughly review the LSN requirements prior to olle tion preparation.
In parti ular, query, display, and print requirements ae t how the olle tion should be prepared. The three
data omponents of the LSN that should be onsidered arefully are the header re ord, the do ument text,
and the page images. The LSN olle tion needs to be prepared with the obje tive of page by page display,
text/image orresponden e and header in lusion. By onverting the text les to Hypertext Markup Language
(HTML), ISRI was able to dene do ument text pages, in lude do ument images and in orporate header
elds for sear hing. Using this omposite do ument format, we were able to meet several of the requirements
of the LSN in Livelink. See Figure 1 to view the HTML sour e for the do ument olle tion. Although by
<html>
<head>
<TITLE>Pro eedings of Workshop 28 on the Borah Peak, Idaho, Earthquake, O t 3-6, 1984</TITLE>
<Do umentType>
Reports
</Do umentType>
<Do umentSubtype>
Te hni al Reports
</Do umentSubtype>
<Publi ationDate>
19850000
</Publi ationDate>
<Author>
Stein, RS Bu knam, RC
</Author>
<Keywords>
EARTHQUAKES Hydrology Faulting Geodesy Seismology Geophysi s
Idaho
</Keywords>
</head>
<body bg olor="#ffffff">
<h1>Pro eedings of Workshop 28 on the Borah Peak, Idaho, Earthquake, O t 3-6, 1984</h1>
<hr>
Figure 1: HTML sour e for inserted header re ord elds
using HTML tags in the HEAD of the do ument, ISRI was able to make the header elds sear hable (see 1),
we did not for e the in lusion of these elds for display or printing in Livelink.
Through the use of HTML several of the requirements of the LSN were met but having a exible Appli-
ation Program Interfa e (API) ould make this omposite do ument an inherent omponent of the system's
user interfa e. Also, several requirements that ould not be easily met by manipulating HTML ould be ome
an intrinsi part of the do ument system. We were unable to evaluate the usefulness of Livelink's API for
meeting the LSN requirements sin e the Livelink API is not available for the Solaris platform.
Sin e Livelink is fully web-based, several of the display and printing requirements of the LSN are depen-
dent on the web browser and/or plugins in pla e. With several browsers and plugins available, it's diÆ ult
to know what apabilities are available to the user and what requirements of the LSN are being met. It is
our re ommendation that the DOE sele t and distribute a web browser after it has been tested thoroughly
with the Livelink system.
3 Requirements Pro ien y

3.1 General Requirements
(R) Year 2K Complian e. DOE-LSN is to be Year 2000 ompliant.

1. Livelink passed minimum onforman e tests ondu ted by ISRI.
2
2. Open Text states , \Livelink Version 8.1 is British Standards Institution DISC YEAR
2000 onformant for the years 1970 to 2037 with the following ex eptions:
This determination in ludes no statement regarding the operating systems or net-
work operating systems that Livelink omponents run on.
This determination in ludes no statement regarding any third party software that
Livelink may use or intera t with in any way,
Provided user represents dates in the manner required by the Software as set out in
the Livelink Software do umentation."
3. Overall Impression
ISRI tested Livelink Version 8.0.4 so the statement published on their website and quoted
here may not apply to the version we tested. We assume though that if Livelink is
sele ted for the LSN, the most re ent version (and the one to whi h this statement
applies) would be sele ted. For more information on Livelink's Y2K omplian e, please
onta t year2000opentext. om.
(R) Colle tion Size. DOE-LSN must a ommodate the anti ipated size of 1,000,000+ do uments ontain-
ing 10,000,000+ text pages and images.
REQUIREMENT NOT TESTED

(R) Internet A essible. DOE-LSN must be a essible on the Internet.
1. Livelink satises this requirement.
2. Livelink uses the paradigm of a web browser lient intera ting with a web server as its
way of providing a user interfa e to the system. Sin e standardized Internet proto ols
and onventions are used in ommuni ations between the lient and server, there are
virtually no restri tions on where the lient an be lo ated on a network to potentially
have a ess to a server running the Livelink system.
3. There are fa tors that may ae t a essibility of the system, all of whi h are onsidera-
tions for any Internet ommuni ations, not just for Livelink. Here are a few:
Internet rewalls. If ommuni ations between the lient and server must pass through
a rewall devi e, it is possible that ommuni ations may be restri ted due to se urity
poli ies.
Web proxy servers. Widely used espe ially by large ISPs, these devi es help to redu e
bandwidth demands by a hing lo al opies of frequently a essed web pages. Sin e
Livelink is su h a omplex system, it is possible that minor problems ould arise for
users who are for ed to go through proxy servers.
Network bandwidth. The transfer of do ument images and other types of data will
make onsiderable demands on available network bandwidth. Adequate bandwidth
on the server side must be available for Livelink to serve requests from all users who
wish to a ess the system.
Network laten y. Laten y is the apparent delay between the time some data is
transmitted from one point on the network to when it is re eived at another point.
With an intera tive system su h as Livelink, it is important to onsider the ee t
of network laten y on the usability of the system. For example, if the average delay
is too great between when a user li ks something and a response is re eived, many
users may feel that the system is too frustrating to use.
Number of li ensed users. To ensure a essibility on the Internet, are must be
taken to ensure an adequate number of li enses for the system exist to be able to
handle simultaneous requests from many users. System load will need to be arefully
monitored and li enses in reased, if ne essary.
3
Livelink is fully Internet a essible sin e this method of a ess is intrinsi to the system.
With the Internet being a fundamental element of Livelink's framework, Internet inter-
fa ing on erns are a nonissue. Ex lusion of all other forms of a ess may not ne essarily
be advantageous.
(R) Windows/Windows NT. DOE-LSN must be usable by lients on Windows and Windows NT oper-
ating systems.
1. Livelink meets this requirement. Sin e the user interfa e to the Livelink system is
through a web browser, and well-known and well-supported web browsers (su h as
Nets ape Communi ator and Mi rosoft Explorer) are available on the Windows/Windows
NT platforms, the system is ne essarily usable by lients on those platforms.
2. However, there are several requirements to be pla ed on that usability, given the vendor-
supplied user interfa e to the system:
Clients must use re ent versions of web browsers. Older browsers may not implement
some fun tionalities that Livelink uses, or their implementations may be buggy. Of
parti ular on ern is the browser's support for and orre t implementation of the
Javas ript language. Corruption of or unusability of the user interfa e to the Livelink
system ould result due to de ien ies in the browser's Javas ript implementation.
Windows/Windows NT lient ma hines must have suÆ ient pro essing power and
memory to be able to run modern versions of the popular web browsers. It is re om-
mended that lients follow the browser vendor's instru tions for at least the minimum
system requirements. Client browsers will use signi ant system resour es even while
simply navigating around Livelink, and espe ially while retrieving do uments and
their images.
Clients must enable Javas ript in their browsers for mu h of the Livelink user in-
terfa e to fun tion, parti ularly navigation aspe ts. Some users might view this as
a se urity on ern. Enabling Javas ript may open the lient ma hine up to se u-
rity holes even in the most re ent versions of popular browsers. This ould be an
una eptable risk for some users. In addition, browsers as of this writing do not im-
plement the ability to turn Javas ript on only when a essing user-spe ied websites.
And most users would nd it umbersome to turn Javas ript on when a essing the
Livelink user interfa e and then turn it ba k o when nished. So the result would
be that everyone wanting to a ess the Livelink system would enable Javas ript and
leave it enabled all the time. This would further in rease the se urity risk, sin e
now the user's ma hine is opened up to potential threats from websites all over the
Internet, not just those that might exist while a essing the Livelink system.
Overall Impression Livelink is a ompletely web-based produ t so meeting this
requirement is not diÆ ult. With this browser dependen e omes the inability to
ontrol the viewers interfa e to the system. In parti ular, Livelink has opted for
heavy use of Javas ript in their browser interfa e design whi h will ae t some users'
ability to employ all of Livelink's fun tionality.
Most systems will use the standard web browser interfa e for lient a ess so these
issues are not spe i to Livelink.
(B) Platforms/Operating System. DOE-LSN should run on one of the following platforms: Windows
NT, Sun Solaris, Alpha Unix.
1. Livelink meets this requirement. Livelink runs on Sun Solaris and Windows NT although
Sun Solaris is the only platform evaluated in this review. Spe i ations for the Sun
platform used in this evaluation an be found in the platform des ription se tion of the
summary report.
4
2. There do not appear to be any spe i issues whi h ae t the performan e of Livelink
on the sele ted platform, although the Livelink SDK (Software Developement Kit) is not
available for platforms other than Windows NT. We did not evaluate the SDK in this
review.
3. Livelink installation was aided by Opentext te hni al sta but the Installation Guide
seems very omplete. System Installation without vendor te hni al support is a hievable.
The installation was generally very smooth. There was a problem with the Ora le
installation that surfa ed after Livelink was installed but Livelink sta was able
to diagnose and solve it qui kly. Reinstallation of Ora le after Livelink to orre t
the problem did not have any adverse ee t on the Livelink installation.
(R) Con urrent Users. DOE-LSN shall support up to 150 on urrent users. [LSS2-064℄
REQUIREMENT NOT TESTED
3.2 Querying Requirements [LSS2-011℄
(R) Query for Do ument. The DOE-LSN shall provide the apability to query the system for a list of
all do uments that meet the query riteria and sort the displayed list on the basis of sele ted displayed
elds or relevan y to the query. [LSS2-011℄
1. Livelink returns a list of do uments that meet the query riteria.
2. Query for Do ument is an integral part of the Livelink interfa e. There are three dierent
ways a user an enter queries: They an sele t sear h from the \Go to" pull down menu
and 1) enter a qui k sear h natural language query; 2) sele t advan ed sear h and use
the Livelink advan ed query language; 3) enter a qui k sear h query dire tly from the
urrent web page. Figures 2 and 3 show ea h of these interfa es. If a user does not
spe ify how the query result list is to be presented, then the results are sorted in the
following order:
(a) Relevan y: The relevan e of the do ument to the query.
(b) Type: The MIME type of an item.
( ) Name: The name of an item.
(d) Date: The date an item was last modied.
(e) Size: The size of an item in kilobytes (KB).
(f) Lo ation: The Livelink Workspa e or higher-level item ontaining an item of interest.
where 2b through 2f are system parameters, not header elds. The user may adjust
whi h eld is to be given higher pre eden e when sorting, but is not able to add dis-
playable regions for the do uments in the olle tion and is not able to sort on them.
The user is given a hoi e to sort in either as ending or des ending order on the 6
aforementioned regions as well as sele t a desired weighting s heme.
3. These apabilities are well do umented and sear hable online in Livelink.
Livelink denitely has the apability to return a list of relevant do uments that satisfy
a given query. Furthermore, Livelink is able to sort the returned list on some of the
more ommonly desired elds su h as name, date, and size and does so on relevan e by
default. With the tools provided, we were unable to re ongure Livelink's interfa e to
allow the display and sorting of header elds.
Note: Sort order is assigned to a parti ular query rather than as a user preferen e. This
makes it ne essary to reset the Display Options ea h time a new query is run to provide
the sele ted display order.
5
Figure 2: Advan ed query interfa e in Livelink
Figure 3: Qui k sear h interfa e in Livelink
6
Figure 4: Header sear h interfa e
(R) Query Header. The DOE-LSN shall provide the apability to query the system by spe ifying the
ontent of one or more header elds to obtain a list of all do uments that satisfy the query. [LSS2-
011-1℄
Comment: The sear h will be able to sort appropriate elds, su h as date, a ession number, et . in as ending
or des ending order. It is anti ipated that the DOE-LSN will allow the user to sele t and sear h multiple
bibliographi header elds.
1. Livelink has the ability to return relevant do uments when queried on spe i header
elds or on ombinations of header elds. But sin e these regions are not displayable,
display options, su h as sorting, are a moot point. We were unable to re ongure
Livelink's interfa e to allow the display and sorting apabilities for header re ord elds.
2. After some investigation, we determined that the most natural way to in lude header
elds and asso iate them with a do ument was to in lude them as HTML-tagged regions
as shown in Figure 1. This use of regions makes the ability to \Query Header" an integral
part of the Livelink system. Figure 4 shows the header query interfa e.
3. In lusion of header elds within do uments was implemented by ISRI (see Se tion 2).
It is possible though that header in lusion ould have been developed using Livelink's
SDK if it were available for Solaris.
4. The user should be provided with some information of data format (e.g., Author eld:
last name, rst initial) sin e the header elds are relational and must mat h exa tly to
retrieve requested do uments.
In order to handle header eld sear hing, ISRI was for ed to reverse-engineer the Livelink
indexing pro edure and enter tags into the HTML le (thus reating an out-of-spe
HTML do ument). The orre t way would have been to represent metadata with the
HTML <META> tag, but it is not lear that it would be possible to do this with
Livelink. ISRI re eived virtually no support from Opentext during this pro ess.
Sear hing of header elds seems to work quite well, but this is little onsolation if the
sear hed elds are not displayable. One inelegant option would be to in lude the header
elds in the body of the text, but this would still not solve the issue of being able to sort
using these elds.
Note: Field names are ase sensitive, so if the user enters a query dire tly into the query
box, he must note the ase of ea h eld name.
(R) Query Text. The DOE-LSN shall provide the apability to query the system by spe ifying one or
more hara ter strings in the full text of the do ument to obtain a list of all do uments that satisfy
the query. [LSS2-011-2℄
7
Comment: Des ribe any query optimization te hniques used by your system.
1. Livelink provides the apability to spe ify hara ter strings to sear h the full text of the
do ument olle tion. Text sear hing is an integral part of the Livelink system.
2. Text sear hing an be a essed in three dierent ways in Livelink by: 1) entering a
qui k sear h natural language query; 2) sele ting advan ed sear h and using the Livelink
advan ed query language; 3) entering a qui k sear h query dire tly on the urrent web
page.
3. Text sear hing apabilities are well-do umented online.
The Livelink advan ed query language is omprehensive with respe t to its full text
sear hing apabilities. It provides several operators and modiers to onstru t omplex
queries. These will be listed and des ribed in detail in the \Text Query Parameters"
requirement in 3.2. A query builder is available to aid the user in the advan ed query
language.
No optimization te hniques were dis losed from Opentext support.
(B) Text Query Parameters. The DOE-LSN shall provide the apability to spe ify single and multiple
hara ter wild ards, to utilize proximity sear hing, and root sear hing as part of a full-text query and
to ombine multiple result sets. [LSS2-011-3℄
Comment: The intent of this requirement is to allow users to ombine any of the previously
exe uted sear hes that were performed during the same sear h and retrieval onne tion.
1. Livelink provides the query parameters listed, standard operators su h as AND, OR, BUT
NOT and has several more operators and modiers (des ribed in 1). Livelink does not
however, allow the apability to ombine query results sets. The operators and modiers
are an integral part of the advan ed sear h language.
2. Livelink provides a point-and- li k query builder interfa e that allows simplied on-
stru tion of omplex queries. Figure 2 shows the advan ed sear h page.
Livelink provides an extensive set of operators and modiers for sear hing the full text
of the do uments in the LSN. As in any query language, a good understanding of both
the syntax and the semanti s of the operators is required to onstru t meaningful ex-
pressions. Livelink does provide a \qui k sear h" interfa e as well for users who are
unfamiliar or are un omfortable with the advan ed query language. Queries or results
an be saved in Livelink, but there is no method for ombining queries.
(R) Query Header and Text. The DOE-LSN shall provide the apability to query the system by spe -
ifying a ombination of header eld values and the text query parameters from the full text of the
do ument to obtain a list of all do uments that satisfy the query. [LSS2-011-4℄
1. Livelink does have the ability to ombine sear hes of header elds with parameters of the
full text of the do ument. No obvious restri tions or problems were en ountered when
ombining these types of parameters and any possible ombination seems allowable.
2. Querying both the header and the text of a do ument an only be done on the advan ed
sear h page in Livelink but Livelink provides an easy to use interfa e for in luding header
eld sear hing into the user's query.
3. This apability is obvious to the user and system regions are do umented online. Cus-
tomized regions, like the LSN header re ord elds, are not do umented in the system
and the in lusion of these were not obvious at installation time.
8
Operator/Modier in Menu Keyword Ee t
Synonym or SOR same as OR, ex ept that
in addition the phrases to the left
and right are treated as synonyms
of ea h other. Mat hing s ores may
dier ae ting do ument rank
Ex lusive or XOR results in nding all items
ontaining exa tly one of the
two spe ied phrases, not both
Within n PROX[n℄ results in nding all
items ontaining both spe ied
phrases within n words of
ea h other
Lexi ally related to stem broadens the query to in lude
words derived from the main
part of the spe ied term
Sounds like phoneti broadens the query to in lude
words that sound like the
spe ied term
Synonyms of thesaurus broadens the query to in lude
words from the thesaurus entry
for the spe ied term
Begins with right-trun ation broadens the query to in lude
words whose beginning mat hes
the spe ied term
Ends with left-trun ation broadens the query to in lude
words whose ending mat hes
the spe ied term
Table 1: Operators and Modiers in Livelink
Livelink provides the ability to sear h both the full text and header elds in a single
query. The problems asso iated with displaying the results of header sear hes an be
found in the response to the Query Header requirement in Requirement 3.2.
Note: When a user wishes to query the full text of a do ument he/she is inadvertently
querying all regions. That is, the default region is set to \Everywhere." It is possible to
query just the full text region of the do ument olle tion however, sin e Livelink supplies
a negation operator that ex ludes spe ied regions from onsideration.
(R) Provide Query Status. The DOE-LSN shall provide the user an indi ation of the query status during
a query and allow the user to terminate queries in pro ess without terminating the session or losing
previous result sets. [LSS2-011-5℄
Comment: It is always possible to onstru t a query so broad that it results in an unmanageable
results list. Users should be able to determine that an ongoing query is too-broad and terminate
the query in pro ess. An indi ation that the session is still onne ted and that the query is working
is adequate.
1. Livelink does not provide any spe i query status indi ator while the system is sear hing
other than what's displayed by the browser. The browser indi ator is spe i to the
browser (i.e. A tive "N" i on in Nets ape Navigator, and spinning "e" i on in Internet
Explorer) while the request is in progress, the status line at the bottom of the browser
gives information about page download in bytes retrieved.
9
2. The download of any page transfer an be terminated by sele ting the \stop" i on on
the browser, but again, this is a browser feature and may dier from browser to browser.
This does not interrupt the urrent session and does not ae t any previously saved
result sets.
3. If the user is familiar with the browser in use, then the browser indi ator and the \stop"
i on an aid in query status and query termination.
4. Sin e these are browser features rather than an integral part of Livelink, no do umen-
tation is provided.
Sin e Livelink is a web-based system, the only interfa e to the DOE-LSN olle tion will
be a web browser. Most users will be familiar with their browser and will know how to
observe and use these features. The user an easily determine whether the query is still
in progress or stalled, but there is no other query status information.
Note: Livelink does not provide the total number of do uments retrieved.
(B) Query Assistan e. The DOE-LSN shall provide intera tive apabilities to assist the user in retrieving
do uments when the eld values that uniquely dene the do uments are not known to the user. [LSS2-
011-6℄
Comment: Examples might in lude synonym pro essing, thesaurus, natural language queries, or
other sear h aids. Be ause a variety of approa hes are used in the ommer ial market, no one
approa h is spe ied.
1. Livelink provides a natural language interfa e on its "Qui k Sear h" page. All other
listed sear h aids are a part of Livelink's "Advan ed Sear h" query language. These
apabilities are an integral part of the Livelink system.
2. A natural language query an be submitted from almost any page in Livelink by entering
the query in the sear h box as shown in Figure 3. The other features an be in luded
into the user's sear h on the \Advan ed Sear h" page with sele tions from drop down
menus as shown in Figure 2. These apabilities are easy to apply.
3. These apabilities are brie y des ribed online but the do umentation ould have been
more developed.
4. Livelink meets this requirement in that it gives the user the apa ity to apply query
assistan e parameters to his query. There are some short omings of the query assistan e
parameters that are addressed below:
Thesaurus: Livelink uses the Inso thesaurus te hnology (version if231e) and the Houghton
Miin Di tionary (version ETMR00512). This thesaurus is not viewable by the user
making it impossible to know if the expansion being applied is what the user had
in mind. Under the urrent Livelink onguration, it is not possible to utilize a
dierent thesaurus. It might be possible in the future, but not now.
Feedba k: Called similarity sear hing in Livelink, it an be applied to either a pre-run
query or sele ted text. Unfortunately, the user is unable to sele t the do uments
the system uses as feedba k; Livelink sele ts the top ten words from the top ten
do uments for the default feedba k terms. The numbers an be hanged by the
user, but the method is xed: A user an only hange the number of do uments (to
say 20) and the number of words sele ted from those do uments (to say 15). Livelink
would then take the top 15 words from the top 20 do uments. The user is unable to
tell the system whi h do uments he believes are relevant to his query.
Natural Language: As stated, natural language queries an be run from the "Qui k
Sear h" page. Advan ed queries an also be entered here although with no interfa e
assistan e. Natural language queries annot be run with dependable results from
the "Advan ed Sear h" page.
10
Sounds Like: broadens the query to in lude words that sound like the spe ied term.
Useful for phoneti ally misspelled words but doesn't show mu h promise for OCR
errors.
Livelink meets this requirement. Livelink though does not allow the user to apply these
sear h aids to their fullest:
A thesaurus is helpful if it an be browsed and the relationship between a term and its
synonym is known. Also some olle tions, like the LSN, have their own nomen lature.
This may require modi ation or augmentation of the default thesaurus whi h is
urrently not possible in Livelink.
Feedba k should in orporate the sense of the query writer. He should have the ability
to tell the system what do uments are most related to his query. Livelink does not
allow this ability in its \nd similar" me hanism.
The \sounds like" approximation doesn't en ompass OCR errors.
3.3 Display Capabilities [LSS2-012℄
NOTE: All display apabilities in Livelink are dependent on the user's browser. These requirements were
tested in several versions of both Nets ape and Mi rosoft Explorer but ex eptions may o ur.
(R) Display Do ument. The DOE-LSN shall provide the apability to display a do ument. [LSS2-012℄
1. Livelink meets only a part of this requirement. A do ument an be sele ted for display
only after a query is run. From the returned results list, a do ument an be sele ted and
displayed. Livelink returns a web-page based do ument with the ability to view do u-
ment text within the user's browser; images are viewable if the user has an appropriate
viewer with apabilities to display TIFF images, (see Requirement 3.3) installed on their
omputer. The ability to view the header elds of a do ument is not provided.
2. Displaying the header elds, the do ument images, and the do ument text as a single
unit is not an integral part of Livelink.
3. The on ept of a DOE-LSN do ument in Livelink was integrated into the HTML pages
as des ribed in 3.2. Although not diÆ ult to implement, it may not be the most natural
representation.
4. Overall Impression Livelink does not meet all the expe tations of this requirement
rst, sin e the header elds annot be displayed and se ond, be ause the asso iation
between an image and text page was implemented using HTML image tags embedded in
the do ument text. See Se tion 2 for more information on Livelink olle tion information.
(R) Display Header. The DOE-LSN shall provide the apability to display the header of a do ument.
[LSS2-012-1℄
1. Livelink does not meet this requirement. Although we were able to in orporate the
header elds as regions into the head of the HTML do ument, the header elds are not
displayable. Some default system regions in Livelink an be sele ted for display, but
user-dened regions annot. This requirement is not an integral part of the Livelink
system.
The Display Header requirement is not met in Livelink; the notion of user-dened do u-
ment meta data is evidently not a on ept that was onsidered by the system designers.
(R) Display Text. The DOE-LSN shall provide the apability to display a page of text of a do ument.
[LSS2-012-2℄
11
Text Format: The text representation of material in DOE-LSN shall be page-delimited ASCII
text. [LSS2-056℄
1. Livelink an display do ument text through the use of a browser. The notion of page-
delimited text is dened by the do uments original format and needs to be implemented
at the time of do ument loading.
2. On e the method of loading is well dened, viewing text pages of a do ument is obvi-
ous. Moving from page-to-page within a do ument is a omplished with HTML tagging
in luded by ISRI sta.
Displaying ASCII text is an integral part of the Livelink system, but in orporating single
pages into a omplete do ument while keeping these pages distin t is not. HTML though
is exible enough to enhan e do uments to improve display hara teristi s.
(R) Lo ate Sear h Terms in Do ument. The DOE-LSN shall provide the apability to lo ate the terms
in the do ument text that satisfy a full-text query and to move from one term to the next or previous
term without displaying intermediate text. [LSS2-012-3℄
Comment: This fun tion is performed as the user is viewing the do ument. It is typi ally im-
plemented by highlighting the sear h terms in the do ument and providing a \go to next term"
fun tion that pla es a ursor at the line or word of the sear h term.
1. Livelink does not dire tly support this requirement. The only way to highlight sear h
terms is by using the browser's find ommand. This is hardly a eptable be ause ea h
sear h term in the query would have to be sear hed separately by the user giving little
ontinuity to the do ument's relevan e.
2. This apability is not an integral part of the system but Livelink user support laims
term highlighting may be in orporated into the next release of Livelink.
3. Overall Impression Lo ating sear h terms in returned do uments is important feed-
ba k to the user. It gives them a lear understanding of why a do ument is returned by
the retrieval system. By not highlighting sear h terms, Livelink degrades the usefulness
of the system even if the relevan e of the do uments returned is high.
(R) Display Image. The DOE-LSN shall provide the apability to display-the images of a do ument,
page by page, in luding full page views of the images-of 8-1/2 by 11 in h pages up to E-size pages.
[LSS2-012-4℄
Image Formats:The ele troni image of do umentary material in DOE-LSN shall use Aldus Tagged
Image File Format (TIFF) Group 4 for bitonal images and Joint Photographi Experts Group (JPEG)
for olor and grey s ale images. These formats are part of the Adobe TIFF I Version 6.0 represen-
tation. Adobe TIFF is an industry standard developed and put into the publi domain by Adobe.
[LSS2-057℄
1. Livelink does not itself support this requirement. Sin e Livelink is browser-based, this
apability is dependent on the spe i web browser being used. This feature most often
omes as a plugin. Later releases of Internet Explorer and Nets ape Navigator for
Windows 95/98/NT and Nets ape for UNIX ome equipped with the ne essary viewing
plugin. Earlier versions may require the user to download the appropriate plugin.
2. Image display is not an integral part of Livelink. The ability to view a do ument image
requires the appli able HTML links to be added to the do ument and a separate plugin
for image viewing.
3. If the user is familiar with web browsing then viewing a do ument image is apparent.
12
Image display is a apability of the browser and plugin, not Livelink itself. It is also
dependent on the way the olle tion is generated for Livelink.1 Sin e Livelink is browser-
based, the user will have the ability to view an image using tools outside of the Livelink
system.
(R) Image Viewing. The DOE-LSN shall provide image viewing apabilities for image enlargement, re-
du tion, s rolling, and rotation. [LSS2-012-5℄
1. Livelink does not itself support this requirement. Sin e Livelink is browser-based, these
apabilities are dependent on the spe i web browser and plugin being used.
2. The listed requirements are in parti ular plugin spe i . The user must pro ure a plu-
gin that provides these abilities. Both Internet Explorer and Nets ape Navigator for
Windows 95/98/NT ome with an appropriate plugin for image enlargement, redu -
tion, s rolling, and rotation. On the UNIX systems, in most ases, a plugin must be
downloaded that supports image enlargement, redu tion, and rotation.
3. Overall Impression Again, Image Viewing is not dire tly supported by Livelink. Be-
ause it is browser-based and be ause plugins an easily be a quired, the user will have
the ability to manipulate an image using tools outside of the Livelink system.
(R) Display Image and Text. The DOE-LSN shall provide the apability to on urrently display an
image page of a do ument and its asso iated text. [LSS2-012-6℄
Comment: There must be a one-to-one orresponden e between ea h page of text and its orre-
sponding page image. This assumes ea h page will be tagged in the text version.
1. Displaying an image page and its orresponding text page is a hievable in Livelink but
is dependent on olle tion preparation (see Se tion 2) and use of an appropriate plugin.
2. Displaying image and text simultaneously is not an integral part of the Livelink system.2,
olle tion preparation is an important stage for implementing image/text orresponden e
and for in luding this ability into the do ument. Also, sin e Livelink doesn't dire tly
provide this apability, what the user a tually views is not ontrolled by Livelink. The
browser window displays the text of a page while the designated plugin displays the page
image.
3. Ease of using this apability depends heavily on initial olle tion preparation (refer to
Se tion 2) and the plugin being used.
For Livelink to meet this requirement, the olle tion needs to be prepared with the
obje tive of page by page display and text/image orresponden e.
(R) Viewing Options. The DOE-LSN shall allow the user to view the following ombinations: 1) header,
2) image, 3) text, 4) header and text, 5) header and image, and 6) text and image. [LSS2-012-7℄
Comment: The user must be able to look at text and headers without looking at images.
1. Livelink does not support all of the listed ombinations. The most obvious drawba k is
Livelink's inability to display the header elds.
2. Image viewing is dependent on olle tion preparation and plugins; text is presented in
the browser; the ombination of these two are des ribed ompletely in Se tion 2.
3. Overall Impression Due to Livelink's inability to support header elds display, this
requirement is not met. There may be ways to modify the interfa e to in lude header
eld display, but it is not apparent from Livelink do umentation or from responses
re eived from te hni al support. Also, display of any kind will always be dependent on
the browser and plugin in use. This may or may not be suitable for the DOE-LSN.
1 See Se tion 2 to view the HTML generated to in lude an image into a text page of a do ument.
13
3.4 Printing Requirements [LSS2-013℄
NOTE: All printing apabilities in Livelink are dependent on the user's browser. These requirements were
tested in several versions of both Nets ape and Mi rosoft Explorer but ex eptions may o ur.
(R) Print Do ument. The DOE-LSN shall provide the apability to print a do ument at a lo al printer.
[LSS2-013℄
Comment: It is assumed that the lo al printer is apable of printing the requested do ument type.
1. Livelink, through the use of a web browser, gives the user the ability to print what is
presented in the browser window (an HTML do ument) to any default printer.
2. Exhibit A shows a printed do ument from the Livelink system. It in ludes all do ument
pages, image links, and text links. Other do ument omponents, like image pages, would
have to be printed separately.
3. If the user is familiar with their web browser, printing a do ument is available and simple
to use.
4. Overall Impression Livelink depends ompletely on the user's browser apabilities to
print a do ument from the DOE-LSN olle tion. What the user re eives in printed form
will depend on the olle tion's preparation in HTML. See Se tion 2 for more details.
(R) Print Header. The DOE-LSN shall provide the apability to print a do ument header at a lo al
printer. [LSS2-013-1℄
1. Livelink does not meet this requirement sin e there is no method to display or a ess
the header elds.
2. The only interfa e given to the user of the DOE-LSN olle tion is what is provided by
the browser. This makes olle tion preparation ru ial for the display and the printing
of do ument omponents.
3. Overall Impression Printing the header elds, like displaying the header elds, is not
realized in the Livelink system be ause the notion of a \header eld" asso iated with
ea h do ument is not inherent in Livelink. These requirements ould possibly be met by
hanging the HTML do ument stru ture or by modifying the Livelink interfa e.
(R) Print Text. The DOE-LSN shall provide a user sele table apability to print from one page to all of
the text of a do ument, and any sele ted ranges of pages, at a lo al printer. [LSS2-013-2℄
Comment: The system must be able to dis ern pages within a do ument for printing.
1. Livelink depends on the browser's printing apabilities to print the text of a do ument.
The browser an print an \HTML page," whi h in this ase is the entire do ument; a
range of pages an be printed in some browsers but they will not be equivalent to the
pages in the do ument.
2. Livelink an print all the text of a do ument, but there is no on ept of \pages" that
orresponds dire tly with the printed pages of an LSN do ument.
3. Printing do ument text is an integral part of the browser interfa e; printing one page to
a sele ted range of pages within a do ument is not.
Livelink's dependen e on the user's browser governs do ument text printing. The \HTML
page" is what gets printed, whi h in this ase, is the omplete do ument. The do ument
stru ture ould be modied to adhere to this requirement but not without ae ting other
do ument a ess issues.
(B) Report Generation. The DOE-LSN should provide report generation apabilities for several of the
above listed tasks.
14
1. Livelink meets this requirement with two spe i report generating fa ilities: 1) Change
Agents; 2) LiveReports.
2. Change Agents are reports that are reated and by Livelink users to tra k hanges
to the olle tion based on user spe i ation. LiveReports are reated by the Livelink
administrator and disseminate information to users about hanges in the system or the
olle tion.
Report Generation an be dened in several ways. With these two reporting fa ilities
Livelink provides a method for users to request information about the olle tion based
on user-dened riteria. The system administrator is also given the apability to query
the underlying RDBMS to tra k statisti al information about database ontents. These
kinds of reports provide what traditional report generation would provide but an be
tailored to individual requests.
(R) Print Standard Image. The DOE-LSN shall provide a user sele table apability to print from one
to all images, and any sele ted ranges of images, of 8-1/2 by 11-in h (or smaller) pages of a do ument,
at a lo al printer, redu ed to a single 8-1/2 by 11-in h paper. This in ludes the apability of printing
an oversized page image , up to E-sized, on a single 8-1/2 by 11-in h sheet of paper. [LSS2-013-3℄
1. Livelink depends on the browsers apabilities as well as an appropriate plugin to satisfy
this requirement. This apability is not an integral part of the Livelink system.
2. Printing images, in parti ular TIFF images, may not be an inherent omponent of the
default browser in use. In many ases, the user will need to download a plugin before
they an view or print a standard image.
3. Most viewer plugins have the ability to print the urrent image to a lo al printer. View-
ers usually in lude the ability to redu e, enlarge, and rotate an image page, so these
apabilities should be met in general.
4. The ability to print a sele ted range or all page images of a do ument is usually not a
feature of viewer plugins and was not built into the stru ture of the HTML do uments
in our test olle tion. Apart from modifying the Livelink interfa e, a plugin viewer may
need to be adapted as well. Some modi ation to the HTML do ument stru ture may
also be required.
Adding this feature to the Livelink interfa e is only one onsideration of this requirement.
Sin e Livelink's browser interfa e depends on a separate plugin, modi ation to this
plugin must also be onsidered. Livelink's losed environment and dependen e on outside
software make this requirement more diÆ ult to realize.
(R) Print Oversized Image. The DOE-LSN shall provide the apability to print an oversized page image,
up to E-sized, on a single sheet of paper at 100 per ent of the size of the original image. [LSS2-013-4℄
1. Livelink depends on the browsers apabilities as well as the appropriate plugin to satisfy
this requirement. This apability is not an integral part of the Livelink system.
2. Printing oversized images may not be an inherent omponent of the default viewer plugin.
3. Many viewer plugins do not have the apability to display or print oversized images even
if the default printer has this ability.
Sin e Livelink's browser interfa e depends on the plugin's apabilities, the sele tion and
re ommendation of the plugin to LSN users is an important onsideration. See Se tion 2
for more information.
(R) Print Results List. DOE-LSN shall provide the apability to print some or all of the summary lines
of a results list. [LSS2-013-5℄
15
Figure 5: Livelink query results list page
1. Using the print apabilities of the browser, Livelink an print a page of results whi h
in ludes the do ument title (dire tory path and le name) and a short summary for ea h
do ument (see Figure 5).
2. The number of do uments per page (with restri tions) and whether summaries are dis-
played and printed an be sele ted by the user. Ea h page of results must be printed
separately to print all do uments returned in the results list.
3. The total number of do uments returned for a query is not dis losed making it diÆ ult
to determine if the query submitted is too broad.
4. Printing the ontent of any browser page is straight forward as long as the user is familiar
with the browser in use.
Livelink's dependen e on the user's browser governs results list printing. The \HTML
page" is what gets printed, whi h in this ase, is the number of \hits" returned per
page. The only ontrol the user has over results list printing is in the \Display Options"
sele tions whi h in ludes: 1) Number of Results 2) Show/Hide Summaries.
Note: The \Display Options" settings are tied to a query rather than to a user, making
it ne essary to resele t these options for ea h new query entered.
(R) Print S reen. DOE-LSN shall provide the apability of printing the s reen display. [LSS2-013-6℄
1. Using the print apabilities of the browser, Livelink an print the \HTML page" dis-
played. This may or may not dene the \s reen display." If the \s reen" is dened as
just the viewable area within the browser, printing just this portion is not possible unless
the full HTML page is in view.
2. Printing the ontent of any browser page is straight forward as long as the user is familiar
with the browser in use.
16
Printing the s reen display is a keyboard fun tion that is rarely used in graphi al user
interfa e (GUI) environments ommonly used today. This requirement seems to be a
arry-over from line-based interfa es and is probably not a strong requirement.
(R) Request Paper Copy. DOE-LSN shall provide the apability to submit an ele troni request for a
paper opy of the header, images, or text of a do ument or of an entire results set, in luding oversized
and olor images. [LSS2-014℄
1. \Request Paper Copy" would typi ally not be a standard feature of any sear h system.
Evaluation of this requirement is based on the simpli ity with whi h this feature ould
be added seamlessly.
2. \Request Paper Copy" ould possibly be met by \embedding" this ability within the
HTML do ument stru ture but would probably be more servi eable as a separate feature
of the Livelink interfa e.
3. It is possible that this requirement ould be added to Livelink using the the Livelink
SDK but sin e Livelink does not urrently support their SDK for Sun Solaris we were
unable to implement it in this evaluation.
\Request Paper Copy" is not a typi al out-of-the-box feature of any sear h engine but
with a exible interfa e (espe ially a browser interfa e), implementation should not be
diÆ ult. Short of OpenText's professional servi es, there was no simple way on the Sun
Solaris platform to in lude this feature into Livelink.
(R) Pro ess Paper Copy Requests. DOE-LSN shall provide the apability to re eive and read an ele -
troni request for a paper opy of a do ument and print the requested opy.
Comment: This is not anti ipated to be a highly automated fun tion. The requested body must
be able to re eive requests and print out the requested do ument. The rest of this fun tion may be
pro edurally implemented.
1. \Pro ess Paper Copy Requests" is the re eiving end of \Request Paper Copy" and would
not be a standard feature of any sear h system. Evaluation of this requirement is based
on the simpli ity with whi h this feature ould be added seamlessly to Livelink.
2. This requirement should be in orporated into the administrative omponent of Livelink.
3. It is possible that this requirement ould be added to Livelink using the the Livelink
SDK but sin e Livelink does not urrently support their SDK for Sun Solaris we were
unable to implement or test it for this evaluation.
\Pro ess Paper Copy Requests" is not a typi al out-of-the-box feature of any sear h
engine but with a exible interfa e (espe ially a browser interfa e), implementation
should not be diÆ ult. Short of OpenText's professional servi es, there was no simple
way on the Sun Solaris platform to in lude this feature into Livelink.
3.5 System Administration Requirements
(R) Monitor System Status. DOE-LSN shall provide authorized users the apability to monitor the
status of the system and ommuni ation omponents and to interrupt, restri t, or disable apabilities
in order to optimize use of system resour es. [LSS2-033℄
1. This requirement is marginally satised by the Livelink produ t.
2. The Livelink system allows the administrative user to monitor the indexing data ow
for all olle tions in the system. An authorized user an s hedule, enable, or disable
the File Walker, HTML onversion, and Indexing pro esses. This allows the Livelink
17
administrator to s hedule the pro esses su h that system resour es are used eÆ iently.
Additionally, the sear h apability for ea h olle tion in the Livelink system an be
independently enabled or disabled.
3. The Livelink retrieval system does not provide extensive system monitoring apabilities.
It provides limited feedba k as to whi h omponents of the system are urrently running,
s heduled to run, or disabled.
4. Livelink does not provide information about the per entage of system resour es being
utilized by ea h omponent.
The Livelink system allows the administrative user to ontrol system a tivities but does
not provide extensive monitoring of system resour es.
(R) Monitor Session A tivity. DOE-LSN shall provide the apability for an authorized user to monitor
user session a tivity levels and identify and an el queries or other system a tivities. [LSS2-033-1℄
1. This requirement is not satised by the Livelink system.
2. Sin e the Livelink do ument management produ t is a web-based system, it does not
provide session level auditing of user a tivity, nor does it provide the ability to an el
a tive queries.
3. These features ould be implemented through the web server apabilities, but would
require a non-trivial level of eort to extend the Livelink interfa e.
4. The Livelink produ t does provide an automated Change Agent that noties the admin-
istrator via email about hanges in the system status. The information available in the
Change Agent report is of minimal use for tuning system performan e. These reports
only ontain information about obje ts reated by users.
The only user level ontrol available to the Livelink administrator is the ability to reate
and delete users, disable and enable user login, and the ability to grant permissions to
users. There is no on ept of \session ontrol" granted to the Livelink administrator.
(R) Database Administration Tools. DOE-LSN shall provide authorized users the apability to assess
the availability, integrity, and performan e of the databases of the the DOE-LSN, in luding those per-
taining to the storage of do ument header elds, text, and image data, and adjust database performan e
parameters or restri t or disable database features in order to optimize system performan e.
1. This requirement is not satised by the Livelink system.
2. The Livelink system allows the administrator to determine the availability of the databases
in the system. It does not, however, provide the ability to determine the integrity of the
databases, or adjust performan e parameters for optimizing the overall system perfor-
man e.
3. Livelink provides the administrator with a limited ability to manage the Livelink ta-
blespa es in the underlying DBMS.
Livelink is not designed as a database repository for do ument header elds, text, and
images. There is no on ept of storing these omponents in databases, rather, these
omponents are left in their original les in their original formats. The index of the
olle tion is stored in Livelink but no information about the index is available to the
Livelink administrator.
3.6 Internet Requirements
(R) Web Server Interfa e. DOE-LSN must interfa e with a Web Server for querying the system and
returning query results.
18
1. The Livelink system satises this requirement.
2. The Livelink system requires the use of a web server in order to fun tion. Intera ting
with the Livelink system through the use of a web browser on the lient side and the web
server on the server side is the only supported method of intera ting with the system.
3. No ommand line interfa e or other user interfa e exists. All user onne tions with
Livelink go from the lient's browser ex lusively to the web server|never to any Livelink
server software dire tly.
4. Overall Impression The only method of a essing Livelink is through its web server.
Although Livelink fullls this requirement, ex lusion of all other methods of a ess may
not be advantageous.
(B) CGI and Perl5. DOE-LSN should use the CGI Standard and be a essible from the Perl5 program-
ming language.
1. Livelink uses the CGI standard ex lusively in servi ing requests from lient browsers.
Opentext has stated that,\all intera tion with Livelink is through HTTP GETs and
POSTs."[1℄
2. Opentext has further indi ated that there are at least two ways for their ustomers to
build their own ustom interfa e to Livelink:
By writing HTML forms using existing Livelink pages as examples and make requests
of the Livelink software run by the web server using HTTP GET and POST oper-
ations. This method would be somewhat limited sin e the lient would have little
or no ontrol over the format of the page and data that is returned from the server,
but nevertheless this might be suÆ ient if the lient is a small program designed to
a ept information, parse the results, and pro ess it.
By building a ustom interfa e to Livelink using the Livelink API whi h the ompany
states is urrently available in C/C++, Java, and Visual Basi . The ompany did
not indi ate it was possible to use the Perl 5 language with the API. They state that
the API is available \for platforms that support those languages."[1℄
3. Although the Livelink API was not part of this evaluation, the ompany seems to indi ate
that, using it, it is possible to build a ompletely ustomized interfa e to Livelink.
Finally, the ompany says:
There are no real limitations to an interfa e written using CGI, the API's or
HTML ex ept for the fa t that you would lose the benet of our work on the
interfa e|whi h may or may not be a problem.[1℄
4. Overall Impression Livelink provides the CGI standard for making some ustomization
and enhan ements to its basi interfa e. The API is urrently not available for the Sun
Solaris platform and therefore, we were unable to evaluate its potential.
(B) ODBC/JDBC Compatibility. DOE-LSN should be a essible using Open Database Conne tivity
(ODBC) and Java Database Conne tivity (JDBC).
1. Livelink is itself not ODBC/JDBC ompatible. Opentext states that, \for performan e,
reliability and s alability reasons there is no ODBC interfa e to Livelink."[1℄
2. Livelink uses Ora le to store some types of information. Depending on the stru ture
of the do ument olle tion and how it was loaded, some or all of the information in
that olle tion may a tually be stored in an Ora le database, not within Livelink. It
is possible to dire tly a ess an Ora le database through ODBC and JDBC and run
queries on data stored there.
3. Livelink states that it is possible to \write a Java appli ation that in orporates our Java
API and JDBC to a ess the RDBMS dire tly."[1℄ Again, this apability would depend
on the Ora le database server and related ODBC and JDBC drivers.
19
Query Average response time (se onds)
INJD-T3-Q1 8.5
TEJA-T3-Q2 8
Table 2: Timing for Retrieval of Results List
Sin e ODBC and JDBC are standard ways of a essing relational databases and sin e
Livelink is not a relational database itself, this requirement does not apply dire tly to
Livelink. The sele tion of the underlying RDBMS will determine ODBC/JDBC om-
patibility.
3.7 Timing Requirements
(R) Timing Strings. The DOE-LSN shall meet the average response times shown in Table 4. The perfor-
man e shall be a hieved with 15 on urrent DOE-LSN users a tive on the system. [LSS-065℄
The Livelink system annot be evaluated at this time under the minimum required load of
15 users, or with the required 5 million pages of do ument data. However, the minimum
timing requirements were analyzed with the smaller test olle tion of about 50,000 pages of
do ument data.
These tests were all performed on a remote Windows NT 4.0 lient ma hine. The lient PC is
a 450Mhz Pentium II running Nets ape Communi ator 4.5 to onne t to the Livelink server.
The ma hines are onne ted via a 10Mbit LAN. Sin e we are not testing Livelink under
operational onditions, the load on the server is relatively low ompared to its apabilities.
1. Retrieval of query results list. LSS2-065-2
The DOE-LSN requires that the query results list be retrieved in 45 se onds for
UNLV test queries INJD-T3-Q1 and TEJA-T3-Q2. Ea h query was made ve times,
the time to retrieve ea h result list was measured, and the average omputed for ea h
query over all trials omputed. Table 2 summarizes the Livelink average response
time for ea h queries.
Overall Impression These average times are for the retrieval of the rst ten rel-
evant do uments a ording to the Livelink system. Given the size of the urrent
olle tion and the light load on the system, it is unknown if Livelink will satisfy this
requirement.
2. Retrieval of header elds for do ument identied in query results list. LSS2-065-3
The Livelink system does not allow for retrieval of header elds information for
do uments returned in a query results list.
3. Retrieval of text data for do ument identied in results list. LSS2-065-4
The LSN requires that the rst page of text be retrieved in ve se onds, and ea h
subsequent page in one se ond. Under our implementation of the LSS prototype
olle tion in the Livelink system, when a do ument is sele ted from a query results
list, the entire do ument is returned. Note that thumbnail images for ea h page in
the do ument are returned as well as the orresponding text. Also, the text for the
page is returned and displayed almost instantaneously while the thumbnails ontinue
loading.
From a sample of 10 do uments retrieved from a query results list, the time to
retrieve the entire do ument from the Livelink server was measured. These results
are shown in Table 3.
Overall Impression From Table 3 it is shown that the average retrieval time per
page is approximately one se ond. From the results of this experiment, it is believed
that Livelink will satisfy this timing requirement.
20
Do ument Page Count Retrieval time (se onds)
1 3 2
2 2 1.5
3 1 1.5
4 2 1.5
5 2 4
6 2 4
7 16 13
8 14 18
9 7 4
10 4 4
Total: 53 53.5
Table 3: Timing for Retrieval of Do ument Text
4. Retrieval of image data for do uments identied in results list. LSS2-065-5

The DOE-LSN requires the rst page image to be retrieved in ten se onds, with ea h
subsequent image retrieved in two se onds.
From a sample of ten do ument pages, ea h page image was retrieved and displayed
in approximately seven se onds (on average). It is believed that mu h of this time
is wasted due to network traÆ . On the lo al ma hine running the Livelink system,
ea h page is returned in under one se ond (on average).
Overall Impression
On a network designated for LSN traÆ , it is believed that the Livelink system will
satisfy the requirement for the retrieval of the rst do ument page image. It is un-
known if the two se ond retrieval time requirement an be satised under operational
onditions.
21
Requirement Fun tion/Event Conditions Response Time
Identier (15/50 on urrent users)
LSS2-065-2 Retrieval of query results list. UNLV test query INJD-T3-Q1 or TEJA-T3- 45 se onds/70 se onds
Q2* Database ontains headers for at least
5 million pages of do uments. A total of 10
do uments found.
LSS2-065-3 Retrieval of header data for do - Database ontains headers for at least 5 mil- 5 se onds/8 se onds
ument identied in query results lion pages of do uments.
list.
22
LSS2-065-4 Retrieval of text data for do u- Database ontains at least 5 million pages of First page: 5 se onds/8 se onds
ment identied in query results do uments. Ea h subsequent page: 1 se ond at Main Fa ility
list. 2 se onds at supported sites
LSS2-065-5 Retrieval of image data for do u- Database ontains at least 5 million pages of First page: 10 se onds/15 se onds
ments identied in query results do uments. Ea h subsequest page: 2 se onds at site
list. 3 se onds at other sites
Table 4: Response Time Requirements
EXHIBIT A:
Printed Livelink Do ument

Isri99 02

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Isri99 02

Uploaded by

Copyright:

Available Formats

A Comparison of Livelink 8 with DOE/LSN Requirements

Te hni al Report 99-02

1.1 Company and Produ t Information

2 Colle tion Preparation

Figure 1: HTML sour e for inserted header re ord elds

3 Requirements Pro ien y

(R) Year 2K Complian e. DOE-LSN is to be Year 2000 ompliant.

REQUIREMENT NOT TESTED

3.2 Querying Requirements [LSS2-011℄

Figure 3: Qui k sear h interfa e in Livelink

Table 1: Operators and Modiers in Livelink

3.3 Display Capabilities [LSS2-012℄

3.5 System Administration Requirements

3.6 Internet Requirements

3.7 Timing Requirements

4. Retrieval of image data for do uments identied in results list. LSS2-065-5

Printed Livelink Do ument

You might also like

Isri99 02

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Isri99 02

Uploaded by

Copyright:

Available Formats

A Comparison of Livelink 8 with DOE/LSN Requirements

Te hni al Report 99-02

1.1 Company and Produ t Information

2 Colle tion Preparation

Figure 1: HTML sour e for inserted header re ord elds

3 Requirements Pro ien y

(R) Year 2K Complian e. DOE-LSN is to be Year 2000 ompliant.

REQUIREMENT NOT TESTED

3.2 Querying Requirements [LSS2-011℄

Figure 3: Qui k sear h interfa e in Livelink

Table 1: Operators and Modi ers in Livelink

3.3 Display Capabilities [LSS2-012℄

3.5 System Administration Requirements

3.6 Internet Requirements

3.7 Timing Requirements

4. Retrieval of image data for do uments identi ed in results list. LSS2-065-5

Printed Livelink Do ument

You might also like

Table 1: Operators and Modiers in Livelink

4. Retrieval of image data for do uments identied in results list. LSS2-065-5