December 2000 - Zope-Dev

keyword indexes
by Josh Zeidner 15 Dec '00

15 Dec '00

Hi, Currently I am wrestling with "keyword" indexes in ZCatalogs. How do I query the ZCatalog for all records of objects indexed on a particular keyword. For instance if my index is named MediaKeyword ive tried: <dtml-in "Catalog.searchResults( MediaKeywords = ['ouch'] )"> this has completely unpredictable results. <dtml-in "Catalog.searchResults( MediaKeywords in ['ouch'] )"> this returns all indexed objects! What am I doing wrong? Is there a special ZCatalog function for querying keyword indexes? I need some insight into this problem. Thanks! Josh Zeidner

2 2

CoreSessionTracking Release 0.2
by Chris McDonough 15 Dec '00

15 Dec '00

I had some reports yesterday of the Core Session Tracking development code not working against recent Zope 2.2 releases, so I removed dependencies in the code on the Interface module which were causing the incompatibilities. CoreSessionTracking 0.1 will work against Zope 2.3a1, but not against Zope 2.2.3, 2.2.4, etc. A new release of the code which has these dependencies removed, 0.2, is available from http://www.zope.org/Members/mcdonc/Products/CoreSessionTracking . This release works against all Zope 2.2.X based systems, AFAIK. Thanks! - Chris

1 0

more on keyword indexes
by Josh Zeidner 15 Dec '00

15 Dec '00

Hello, I did a little more investigiation into the problem, and couldnt really find any documentation anywhere on what the actual semantics are of keywords and how they are queried. For instance: I have three classes and each has an keyword index named KW: ObjectOne: KW = ['one','blue','furry'] ObjectTwo: KW = ['two','flying','purple'] ObjectThree: KW = ['three','one-eyed','purple'] If I were to query the ZCatalog with the following set of words: ['purple'] I would expect to get: ObjectTwo ObjectThree Right? If I query the database with ['one','two'] ( if this type of thing is at all possible ), I get : ObjectOne ObjectTwo This seems like the obvious result: BUT: it depends if you want a AND/OR type search. I could also expect to get nothing( if its an AND type search because no records match 'one' and 'two' ). Here is better example, what if I queried: ['purple','one-eyed']. Would I be expecting only ObjectThree or [ ObjectThree, ObjectTwo ] ( because they both match the keyword purple( a logical set-intersection ) ). Also I found the keyword indexes to have some more obvious bugs. If I only used one keyword for the matching critiria, for instance if I used 'purple' , I would only get ObjectTwo. Is anyone else using keyword indexes? In what way are you using them? Thanks, Josh Zeidner http://www.brooklynmedialabs.com

2 1

Catalog class--does it support boolean queries?
by Marc Conley 15 Dec '00

15 Dec '00

I am working on a project which requires the use of the Catalog class (versus ZCatalog) for indexing and querying. I have basic full text indexing and querying working correctly but boolean queries seem not to work. Should boolean queries work using Catalog or is it necessary to use ZCatalog instead to get that functionality? This is how I am submitting the query to the Catalog object: results = sdb.cat({"content" : query}) where sdb is a ZODB, cat is the catalog object, and content is the name of the full-text index. query is the query the user typed, which could be "(apples and oranges) or plums" (without the quotes) for instance. Thanks in advance for any assistance anyone can provide on this question.

3 2

RE: [Zope-dev] ZPatterns: General Design Question
by Roch'e Compaan 15 Dec '00

15 Dec '00

>However, if your application needs to have end-user (as opposed to integrator-user) What is a integrator-user? > There is also an option "c", which would be to model > LicensePropertyDefinition and LicenseProperty objects in your > domain model. > This approach leads to a bit more work defining your model, as well as in > setting up the specialists and their interactions, but the payoff is in > better documentation of what your app is doing and easier re-mapping from > one database type to another. Just to check if I understand correctly - will this result in a LicenseType instance with related LicensePropertyDefinition instances. If a new License of a particular LicenseType is created LicenseProperty instances will be created based on the LicensePropertyDefinitions of the selected LicenseType. Many thanks Phillip Roché

1 0

Re: [Zope-dev] Catalog class--does it support boolean queries?
by Dieter Maurer 14 Dec '00

14 Dec '00

Marc Conley writes: > .... > Should boolean queries work using Catalog > or is it > necessary to use ZCatalog instead to get that functionality? > .... ZCatalog is nothing more than a thin wrapper around Catalog (to make a Catalog a persistent object in ZODB). All search facilities of ZCatalog are in fact implemented by Catalog. This implies: Catalog can do boolean queries. Note: the catalog has notorious bugs (at least until Zope 2.2.2). If it does not work, it may be one of these bugs. Dieter

1 0

Core Session Tracking Development Release 0.1
by Chris McDonough 14 Dec '00

14 Dec '00

Hi, A development release of the fruits of the "core session tracking" Fishbowl project (http://dev.zope.org/Wikis/DevSite/Projects/CoreSessionTracking/FrontPage) is available at http://www.zope.org/Members/mcdonc/Products/CoreSessionTracking. It allows you to keep state across requests for anonymous users (much like FSSession, SQLSession, HappySession, etc.), but it is capable of storing sessioning data in the ZODB or in RAM. You need to be running a pretty recent Zope 2.2.X to use it. I've tested it continually against the current trunk release, and it works against that. Feedback appreciated! Thanks, Chris

1 0

ZClass registry repair utility
by Shane Hathaway 14 Dec '00

14 Dec '00

I've written a utility you can use to clean up the global registry of ZClasses. The registry can become corrupt through product upgrades--not ZODB corruption, but missing base classes and so forth. This utility recreates the registry. http://www.zope.org/Members/hathawsh/ZGlobalsRepair It's probably a good idea to run it after a major Zope upgrade. Shane

2 2

Re: [Zope-dev] ZPatterns: persistant objects hold DataSkin-Items -> KeyError: _v_dm_
by Ulrich Eck 14 Dec '00

14 Dec '00

hi Philip ... > >so for a database app that handles multiple tables > >it isnt useful to handle with a FwCS. > > Um, not necessarily. You can create regular Folders under the FwCS if you > want to keep them seperate. You can even use BTreeFolders or other > ObjectManagers, if you like. All that's required is that they support the > ObjectManager protocol. So you can have a folder for each meta_type. Of > course, the primary storage of the object has to be the ZODB. > > this is not really what i plan to do .. the main storage is the sql-database in this case .. if another application needs something else we can change it using other methods in our racks or customizers. > >I'll switch back to a Specialist which has many racks as data-providers > >which i can choose the right one with a method that has a "meta-type" > >parameter. > > > >is this right so far ?? > > Pretty much, although I'm not sure why you want to pick by meta type, since > one of the major reasons for having a Specialist is for the rest of the > application not to know about specific meta types. > I renamed my Product now to ZWorkflowManager which is a bit clearer. we want to develop pluggable parts for "big-multi-feature-app" like a network-inventory/documentation tools as part of the hole. in every part there are predefined Workflows e.g. a network-doc-tool has a Workflow: <Register a new Komponent> < add at least 1 Physical Port> <add for every Physical Port at Least One Logical Port> and so on ... to ensure reusability of the hole process I want to support several Metatype with my WorkflowManager which is derived from a Specialist now. these are for example form-rendering, property-validation (with plugins) and property-updates as well as creating new obects of every supported type via on the fly generated Workflows (defined through dependencies between Metatypes) Right now i my ZWorkflowManager is derived from a Specialist. It has Racks which hold every supported Metatype in a rack for it own. Those can be generated with a widzard which creates a ZClass_for_Dataskin all needed ZSQL-Method an a default-SkinScript for a DataBase Table It has a PluginContainer for Validators which can e.g. validate a certain ipaddress against lexical and logical rules. Every Plugin supports one or more different check_types e.g. string :), ipaddress, subnet, phone/faxnumber, ... Therefor I would need an extension of the DataSkinAttributePropertySheet which uses one more field in the _properties Dictionary and another for label definition of on-the-fly generated forms e.g. I _properties = ( {'id':'title','type':'string','mode':'w','check_type':'ipaddress','label':'I P-Address'}, ) can i Extend a DataSkinAttributePropertySheet by extending its basic attributes and modifying its manage_workspace(..) method to support my extensions ?? The ZWorkflowManager can reender new/edit-forms, delete-screens, views and search-forms/results for every Meta_Type stored in a rack of itself. perhaps there will be something like LinkToParentWorkflowManager :) my ZWorkflowManager provides the functionality to analyse and validate all metatypes attributes via check_types and hopefully a fitting validator-method in the Validators PluginContainer. The ApplicationIntegrator then can easily build different userscreens, browse-methods with related Information in the Specialist which serves a userinterface for the hole app in realation to network-doc-stuff. Is this the right design for an application i want to build ?? cya Ulrich Eck

1 0

ZPatterns: General Design Question
by Roch'e Compaan 14 Dec '00

14 Dec '00

As part of a Customer Relationship Management system our company is developing, we have a Licenses specialist which manages product licenses. All license objects do not have the same attributes however. The various attributes relating to different licence types are not known attributes from the outset. My idea is to have a LicenseType class for which the user can define extra attributes per instance eg: LicenseType1 with properties A,B,C LicenseType2 with properties D,E,F When new licenses are created the user first selects a LicenseType. Based on this selection the properties of the selected LicenseType are added to a specific License instance. As I see it one can take two approaches to this: a) either add a single dictionary property for both license and licensetypes which holds user defined attributes or b) explicityly call manage_addProperty per instance to add properties. Any ideas? Roché

2 1