Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1.8
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Query functionality is imperative to this lab. It is a part of their daily work activity.

      Exploratory Plone Collection work to be dusted off. SQL like UI for report generation, FlySQL, etc. What does Crystal look like nowadays?

      1. Queryemail.png
        8 kB
      2. Queryform.png
        10 kB
      3. Queryresults.png
        6 kB

        Issue Links

          Activity

          Hide
          lemoene lemoene added a comment -

          > Afaik Plone collections will be best to mine data, then display & export. Sub-total, Graphs anybody?

          The main query language for ZODB is Python, as the ZODB looks just like
          a big 'ol nested dictionary. So a query might look like a recursive
          function that iterates over a hierarchy of objects.

          But that requires knowledge of the Bika objects and Plone/Zope APIs.

          For tools usable in the browser, I can think of these:
          https://pypi.python.org/pypi/eea.daviz
          https://pypi.python.org/pypi/eea.facetednavigation

          Show
          lemoene lemoene added a comment - > Afaik Plone collections will be best to mine data, then display & export. Sub-total, Graphs anybody? The main query language for ZODB is Python, as the ZODB looks just like a big 'ol nested dictionary. So a query might look like a recursive function that iterates over a hierarchy of objects. But that requires knowledge of the Bika objects and Plone/Zope APIs. For tools usable in the browser, I can think of these: https://pypi.python.org/pypi/eea.daviz https://pypi.python.org/pypi/eea.facetednavigation
          Hide
          lemoene lemoene added a comment -

          From IRC <lemoene>
          For Quries UI i can't add more to what was said on the list, the user identifies what he/she is searching for: Analyses, Samples, Invoices, Supply Orders, Patient, Doctor, Case, Set-up item, etc. and then build querie around its avaialble attributes from look-ups
          Will post Bika 1 screen shots. https://jira.bikalabs.com/browse/LIMS-1578

          Show
          lemoene lemoene added a comment - From IRC <lemoene> For Quries UI i can't add more to what was said on the list, the user identifies what he/she is searching for: Analyses, Samples, Invoices, Supply Orders, Patient, Doctor, Case, Set-up item, etc. and then build querie around its avaialble attributes from look-ups Will post Bika 1 screen shots. https://jira.bikalabs.com/browse/LIMS-1578
          Hide
          lemoene lemoene added a comment -

          Use Case from email:

          Searching for Results
          From mile up functional perspective, we need to answer the most common query: Where is that Analysis result? For parameters: start date, end date, Client, sample type, sample point etc. Later we go for Orders, Samples, etc.

          Query Form
          The Bika 2 manual used this very example, screenshots could be Bika 1... Anyhows, gives you an idea how users in a wine lab would use it. Any of the parameters can be left empty.

          Clients may run queries too, but are restricted to their own data only

          Nice to have:

          1. Wild cards in query parameters

          2. Field completion look-up widgetry

          3. Secondary parameters be delimited to primary ranges, e.g. in the above: once a client is selected, the sample IDs up for selection, must be from only that specific client's in the look-up. Note how no look-up is offered in the screen-shot...

          Query Results

          Note that results can be emailed. This can be integrated with Bika 3 save as CSV, as options for Query results and Reports e.g. save or email as HTML, PDF or CSV, etc.

          Show
          lemoene lemoene added a comment - Use Case from email: Searching for Results From mile up functional perspective, we need to answer the most common query: Where is that Analysis result? For parameters: start date, end date, Client, sample type, sample point etc. Later we go for Orders, Samples, etc. Query Form The Bika 2 manual used this very example, screenshots could be Bika 1... Anyhows, gives you an idea how users in a wine lab would use it. Any of the parameters can be left empty. Clients may run queries too, but are restricted to their own data only Nice to have: 1. Wild cards in query parameters 2. Field completion look-up widgetry 3. Secondary parameters be delimited to primary ranges, e.g. in the above: once a client is selected, the sample IDs up for selection, must be from only that specific client's in the look-up. Note how no look-up is offered in the screen-shot... Query Results Note that results can be emailed. This can be integrated with Bika 3 save as CSV, as options for Query results and Reports e.g. save or email as HTML, PDF or CSV, etc.
          Hide
          lemoene lemoene added a comment -

          Moved issue to the GSoC reporting Epic, https://jira.bikalabs.com/browse/LIMS-1852

          Show
          lemoene lemoene added a comment - Moved issue to the GSoC reporting Epic, https://jira.bikalabs.com/browse/LIMS-1852
          Hide
          lemoene lemoene added a comment -

          and then to COU, also see LIMS-2398

          Show
          lemoene lemoene added a comment - and then to COU, also see LIMS-2398

            People

            • Assignee:
              Unassigned
              Reporter:
              anneline Anneline Sweetnam
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Due:
                Created:
                Updated: