Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #1219 (new)

Opened 15 years ago

Last modified 14 years ago

Decide on proper Filter.limit handling in ITimeline

Reported by: jamoore Owned by: jamoore
Priority: major Milestone: Unscheduled
Component: General Version: 3.0-M1
Keywords: n.a. Cc: atarkowska
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.


Current limit is 50, which is obviously non-optimal.

Change History (4)

comment:1 Changed 15 years ago by atarkowska

  • Priority changed from minor to major

The purpose of getEventsByPeriod is to present how many events happens on the system in particular period. Maybe we need to have countEventsByPeriod what returns {"Image": number, "Dataset": number, "Project":number, and another types...} with no limits.

The particular day needs the data:

self.cal_days.append({'day':self.cal_weeks[week][day], 'counter': {'imgCounter':imgCounter, 'rdCounter':rdCounter, 'dsCounter':dsCounter, 'prCounter':prCounter }})

WARNING: event types currently supported: INSERT/UPDATE

comment:2 Changed 15 years ago by jmoore

  • Milestone changed from OMERO-Beta4 to OMERO-Beta4.1

comment:3 Changed 15 years ago by jmoore

  • Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2

comment:4 Changed 14 years ago by jmoore

  • Milestone changed from OMERO-Beta4.2 to Unscheduled
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.62826 sec.)

We're Hiring!