Hi Justin,

Thanks for the information. We aer using marklogic 3.2 now, very soon we will
move to marklogic 4. We also have to think how to do upgrade.   I'll take a
look.

Thanks, Helen

>>> Justin Makeig <[email protected]> 08/26/09 12:44 PM >>>
Helen,

While others may have more insight into lib-search, I would recommend taking a
look at the new Search API that ships with MarkLogic Server 4.1. It is a
high-level XQuery library that simplifies building search applications. Most of
the concepts in the Search API will be familiar to lib-search/lib-parse users,
such as query parsing and declarative facets and search constraints. It also
includes a well defined mechanism to extend the API, for example to customize
the query grammar. The Search API is an officially supported Mark Logic product
that will improve and grow with MarkLogic Server. You can find more information
in the “Search Developer’s Guide”
<http://developer.marklogic.com/pubs/4.1/books/search-dev-guide.pdf>.

Please let me know if you have further questions or concerns.



Justin






Justin Makeig
Product Manager
Mark Logic Corporation
999 Skyway Road
Suite 200
San Carlos, CA 94070
+1 650 655 2387 Phone
[email protected]<mailto:[email protected]>
www.marklogic.com<http://www.marklogic.com>
<http://www.marklogic.com/><http://www.marklogic.com/>
This e-mail and any accompanying attachments are confidential. The information
is intended solely for the use of the individual to whom it is addressed. Any
review, disclosure, copying, distribution, or use of this e-mail communication
by others is strictly prohibited. If you are not the intended recipient, please
notify us immediately by returning this message to the sender and delete all
copies.  Thank you for your cooperation.



-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Helen Chen
Sent: Wednesday, August 26, 2009 8:05 AM
To: [email protected] 
Cc: Helen Chen
Subject: [MarkLogic Dev General] questions about lib-search



Hello there,



if I use lib-search, then all the configuration will be in file

lib-search-custom.xqy, and it is in the same directory of the search library.



I may have different applications/modules which requires different

configurations, I'm thinking to put all the search lib files into a global

directory as global lib, but I pull the file lib-search-custom.xqy out. and
then

for each applications/modules, I have a separate sub directory under my root

directory, I put the configuration into lib-search-custom.xqy for each sub

directory. This way I can specifically import the lib-search-custom.xqy file

from each directory so each application can have its own configuration.



for example, some application may want to have a search-path configuration,

some may not. If I have a single lib-search-custom.xqy file, then I don't know

how to control it. That's why I'm thinking to have a seperate

lib-search-custom.xqy file for each one, or at least some apps that require

special config can have itw own config.



I'm not sure if this is a good idea. It may also be a problem for upgrade.
Does

anybody have similiar situations like this? how did you handle it?



Thanks, Helen

_______________________________________________

General mailing list

[email protected] 

http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general

Reply via email to