Ticket #462 (new enhancement)

Opened 1 year ago

Last modified 1 month ago

Create a filter framework to allow for 'smart' collection of objects.

Reported by: amit Assigned to: ronald
Priority: high Milestone: 0.9.1
Component: topaz Version: 0.8
Keywords: filter collections Cc:
Blocking: Blocked By: 1024

Description

One of the requirements for PLoS is to be able to run multiple virtual journals within the same application. The basic concept is to create a contextual set of filters based on a set of rules/configuration which limits all operations (within the application) to only those objects which match the filter/rules. This way application logic can set a context and not have to worry about modifying every query.

Dependency Graph

Change History

08/15/07 10:39:16 changed by amit

  • priority changed from critical to medium.

I believe most of this is done (see r3466) so I am downgrading it. Ronald can update this with the precise set of changes associated with this better than I can so I am leaving it open.

08/20/07 12:16:14 changed by ronald

Most of the work for this has been done in [3042], [3121], [3261], [3267], [3420], and many other smaller commits.

Oustanding issues with the core filtering are:

  • filters on queries (both OQL and Criteria) are not applied to superclasses of the filtered objects, only to subclasses. So for example a filter on Journal is not applied to queries for Aggregation's.
  • the object and field filtering in get() is broken in that it applies filters for both subclasses and superclasses of the object's or field's type without further distinction; the filters for subclasses must be further constrained to only be applied if the object or field actually has that type. This is similar to the point above, except that here it's implemented but in a broken manner.

08/21/07 09:55:54 changed by amit

  • version changed from 0.7 to 0.8.
  • milestone deleted.

Moving it out of 0.8.

09/08/08 16:41:46 changed by dragisak

  • blocking changed.
  • blockedby changed.
  • milestone set to 0.9.1.

09/08/08 17:23:11 changed by dragisak

  • blockedby set to 1024.

10/03/08 13:37:56 changed by pradeep

(In [6492]) Remove the rdf:type look ahead. Also removed is the requirement to filter associations. This makes the get(entity, id) queries simpler since the filtering is only needed for the object itself.

Closes #1024. Addresses #462.

10/27/08 13:51:38 changed by amit

  • priority changed from medium to high.