Re: [bika-dev] These 'modules' first Alfonso?

[Alfonso de la G. <alf...@gm...>]

Lemoene,

Right now, i am as speaker in the Linuxcon Brasil, please let ne check
those features in the night for planning the roadmap.
Thanks!

Saludos,

--------------------------------
Alfonso de la Guarda
Centro Open Source(COS)
http://www.cos-la.net
http://alfonsodg.net
Twitter: @alfonsodg
Redes sociales: alfonsodg
   Telef. 991935157
1024D/B23B24A4
5469 ED92 75A3 BBDB FD6B  58A5 54A1 851D B23B 24A4



On Thu, Nov 17, 2011 at 05:49, lemoene <le...@bi...> wrote:
> Hi Alfonso
>
> Stop me when this gets too much (or we can go off-list - but in public here
> we might get some useful feedback - are you there Jean;-)
>
> Am not sure about your team's available capacity, but if you are going to
> dive into the Bika 3 code any time soon, I recommend tackling any of these
> semi-detached outstanding items first:
>
> 1. Pdf writing
>
> In Inkosi LIMS 2 pdfs are only used as results publication preference -
> client contacts may select it from amongst all the other publication
> preferences and receive their analysis results as pdf attachments to emails.
> Eventually, LIMS 3.1 say, we would also make it possible to save and email
> all reports as pdf.
>
> We used ReportLab for Inkosi and would consider it in conjunction with pisa
> this time round for its Plone/Zope integration and forward looking approach.
>
> 2. Graphing
>
> In Inkosi, we use Zope's RenderableCharts and Reportlab again, as well as
> Gary Strangman's stats.py for the stats calculations required for QC
> distribution curves etc.
>
> R is the most obvious improvement to stats.py. For their ease of integration
> with Plone, consider:
>
> Matplotlib http://matplotlib.sourceforge.net/
> http://www.scipy.org/Wiki/Cookbook/Matplotlib/Matplotlib_and_Zope
>
> PyChart http://home.gna.org/pychart/
> http://plone.org/documentation/kb/add-charts
>
> Graphs used in Inkosi/Health 0.3:
>
> Analysis results over time per sample point/patient
> Reference results per analysis over time
> Reference results distribution
> % Relative error for duplicates
>
> See QC reports and graphs re the last 3 in the Inkosi manual.
>
> 3. Working time calendar
>
> Written up in the Inkosi calendar here: Bika Calendar Manual. It is
> currently only used to determine accurate turn around times, excluding
> non-working hours, weekends and holidays, but has to be approached carefully
> so as not to exclude future scheduling requirements:
>
> Scheduling sampling in Bika  Water, some of it recurring - say sampling the
> same river on a weekly basis. The calendar will in this case be used to
> simply trigger the automated creation of  Analysis request, Sampling rounds
> and instructions, and alerting Samplers to it.
>
> Most complicated and notoriously challenging: to predict accurate expected
> turnaround times for clients based on the loads of instruments and analysts.
> Bika 3.5?-)
>
> See you on the hub!-)
> Bests
> l
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Bika-Developers mailing list
> Bik...@li...
> https://lists.sourceforge.net/lists/listinfo/bika-developers
>
>