Maybe use the individual digits in the number, so six one-digit numeric attributes instead one six-digit numeric attribute and then to capture ranges of numbers save really long queries of "OR second-digit Word Begins with 0 OR second-digit Word Begins with 1 OR second-digit Word Begins with 2 OR second-digit Word Begins with 3..." to your System Volume's "Slice Folder". Or try a LiveReport.
-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: August 21, 2001 4:07 AMTo: eLink RecipientSubject: how to manage numeric range attributes...
how to manage numeric range attributes...Posted by EtnoTeamUser1 on 08/21/2001 06:03 AM
Hi everybody,I'm a newbie in Livelink and I'm having troubles in finding a good solution to my problem....any idea and suggestion would be really appreciated.
The question is: we have to organise with Livelink 9 a great number of technical documents. The end user has a problem with a car (which is univoquely identified by its model and a numeric code)and should search a possible solution to his problem among the documents. Obvious search keys for the user should be car model and numeric code. Unfortunately, most of the documents contains ranges of identifiers: for example, the document "solution1.doc" could say "this solution applies to the model AAA, from code 111111 to code 222222, and to the model BBB, from code 444444 to code 888888.....".
How is it possible to classify documents in Livelink in such a way that if the user digits in the search page "model AAA" and "code 200000" the system is able to find the document "solution1.doc"? We were thinking of adding a new schema to Livelink DB, with the car model, the lower and upper limits of the range, and the volumeID-nodeID (taken from DTree table) of the document regarding that model and that range: each time a document is added to the workspace, for each model and range it refers to, a new record should be created in the table. When the end user searches a certain model and code, an SQL query scans the table searching for that model and all the ranges that can contain the numeric code, and returns the list of matching documents.
Could this be a correct way of solving the problem? And if so, is there any document or tutorial (other than Builder Help, which I admit I don't find very "friendly") which explains how to customize the search functions in Livelink?
Or is there any simpler solution, perhaps using categories and attributes, that we didn't think of?
Thanks in advance
Cristina
[To reply to this thread, use your normal e-mail reply function.]
============================================================
Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=view
Livelink Server:https://knowledge.opentext.com/knowledge/livelink.exe
