Shannon,
Unfortunately there is no way currently to "alias" a collection name for search 
constraints and display beyond the prefix attribute in the search options.
There are a couple work-arounds that you might consider in the near-term:

* Write a custom constraint 
(<http://developer.marklogic.com/pubs/4.1/books/search-dev-guide.pdf>, Section 
2.5) that interprets your user-friendly names and turns them into collection 
queries for downstream consumption by the Search API. This would replace your 
existing collection constraint.

* Create parallel "user-facing" collections on your documents that could be 
tied to Search API constraints.

In the longer-term I've logged an RFE (1565) for this request. Any additional 
use cases or detail would be appreciated.

Thanks and, as always, please let me know if you have additional questions or 
concerns. Have a great weekend.

Justin


Justin Makeig
Product Manager
MarkLogic 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.


On Jun 11, 2010, at 12:12 PM, Shannon wrote:

Hello,

Assuming that collection names used internally may not be the most 
user-friendly naming conventions (in my case, the collection constraint name is 
"pub", and I want like to make it possible for the user to enter a query text 
of "pub:Jefferson" when the specified collection is named "TSJN" for internal 
reasons), is there a way to achieve this in the API? With an extension? What 
would be the best practice? Or should I send an RFE to Support? TIA.

Best,
Shannon
_______________________________________________
General mailing list
[email protected]<mailto:[email protected]>
http://developer.marklogic.com/mailman/listinfo/general

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

Reply via email to