1 / 16

TUF23: TRIM User Forum 2010 Changing the Economics of IM

TUF23: TRIM User Forum 2010 Changing the Economics of IM . Rory Kleeman Software Architect, HP Information Management. Searching For TRIM 7. Why have a new search engine?. Support web-based applications Expand record search capabilities Improve consistency with wildcards and recursion

deon
Download Presentation

TUF23: TRIM User Forum 2010 Changing the Economics of IM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TUF23: TRIM User Forum 2010Changing the Economics of IM Rory Kleeman Software Architect, HP Information Management

  2. Searching For TRIM 7

  3. Why have a new search engine? • Support web-based applications • Expand record search capabilities • Improve consistency with wildcards and recursion • Improve search capabilities for other TRIM objects • Locations, workflow, schedules, ... • Improved language support • CMIS and e-Discovery, emerging requirements

  4. Key design goals • Simple string for embedding in web application urls • Support existing search capabilities • Support existing search optimisations • Provide multiple object navigation • Have a consistent approach to string wildcard expressions • Implement recursive object navigation in a standard way • Provide fully functional programming interface • Rich search capability for all TRIM objects • Saved searches to work for all locales

  5. Syntax • Search consist of one or more clauses • Clauses are combined with and or or • Use ( ) for precedence • Optional not for clauses or bracketed expressions title:inspection and registeredOn:this week registeredOn:this week and (assignee:helen or author:helen) registeredOn:this week and not assignee:me

  6. Syntax (cont.) • A clause has the form method:parameters • A method can be • generic, applying to many object types all, none, uri, usable, favorite, within, … • object-specific, each object has its own list of available methods assignee for records, surname for locations, … • an additional field the method name is the field name with no spaces • All methods have a format • determines how you specify the parameters string, word index, date, object, number, enumerated value, boolean

  7. String Format • Single search value inspection • Single search value with wildcards inspect* - finds inspector, inspects, inspection, inspections,… • Can be creative with wildcardsd?om*a?y – finds dromedary, camel, ship of desert • String range (no wildcards allowed) 87/00000 to 87/9999 • String value list (no wildcards allowed) prescribed, burning, hazard, reduction • Use quotes to include spaces, etc “*hazard reduction*”

  8. Word Index Format • Single word fire • Single word, with wildcard fire* • Multiple words (implicit and) fire warning system* • Multiple words (implicit or) fire, warning, system • Phrase “fire warning system”

  9. Date Format • Single date 1/1/77 • Single date with time 1/1/83 12:30:00 • Date range 1/1/77 to 1/1/83 • Date range shortcuts last 7 seconds/minutes/hours/days/weeks/ months/quarters/years this/next [fiscal] year/quarter year/quarter/month to date 2006, february 2006, february today, tomorrow, yesterday

  10. Number Format • Single number, suitable for type 107 $27.35 2.5 • Number Range 107 to 206 $100 to $999 • List of numbers (implicitly or’d) 10,17,222 $100, $200, $300

  11. Enumeration Format • Single value using caption: low addressee • Single value using underlying number 2 • Set of values using captionlow,mediumauthor,addressee • Set of values using underlying number 1,3,44

  12. Object Format • Single uri value (uri now exposed) 377 • Multiple uri values in a list 44,55,678 • Single uri value, recursive 377+ • Multiple uri values, maybe recursive 44,55+,678+ • Subquery [surname:smith and gender:male and dob:1964]

  13. Boolean Format • Has no parameters at all • Use not to negate search requirement active not active

  14. Language Support • Basic grammatical elements are translated • and/or/not/to • last/this/next/fiscal/to date • All search method names are translated • Caption editor is available for search methods • “Internal” search method names guaranteed to work • mainly for developers wishing to work with search strings

  15. Saving Searches • Any search can now be saved • see TRIM “Save Search As” menu item • A saved search can be embedded inside another search • use the generic saved method • Saved searches can be grouped hierarchically • Saved Searches can be assigned to an owner • can now be a project team or section • Saved searches use an XML search format • Saved searches are language independent • automatically converted to client’s locale

  16. For more information... • IM Digital Hub: www.hp.com/go/imhub • TRIM Home Page: www.hp.com/go/hptrim • Facebook: http://tinyurl.com/HPTRIM-7-Facebook • Twitter: www.twitter.com/HPInfoGov • www.twitter.com/thattrimguy • Twitter HashTag: #TUF23 • Blogs:www.hp.com/blogs/information-faster • HP Software Solutions Community: www.hp.com/go/swcommunity • TUF23 Post-event Website: Available April 2010

More Related