#47 xml reports

Next Minor Release
closed-fixed
None
9
2013-04-30
2006-10-25
No

hello,

i was thinking if the report(s) would benefit of an xml
output. that could have two benefits:

- users could easily create there own xslt that
transforms the report in something completely what they
like.
- you could use that to unify the reports by creating
xslts for your out of the box reports, and provide them
as "resources" for the users to change.

in any case i'd appreciate some kind of "export all to
xml" functionality to make my own kind of lists.

and to add a second, related request: it would help a
lot if the reports would not only be applied to a
search result, but if it would also possible to apply
it to all items. currently i always have to switch the
maximum search results (which during normal operation i
have set to a lower value than during reporting).

markus

Discussion

  • Robert Jan van der Waals

    • assigned_to: nobody --> rwaals
     
  • Robert Jan van der Waals

    Logged In: YES
    user_id=455224

    Since I am planning to change the reporting mechanism
    altoghether I will
    take this into consideration. I am depending on tools such
    as jasper reports
    and itext for standards (as those are tre libraries I will
    probably be using)
    though.

    Reports will no longer be based on the search results in any
    case. This was
    a bad solution and is not needed anymore.

     
  • Robert Jan van der Waals

    Logged In: YES
    user_id=455224
    Originator: NO

    - Reports
    Complete overhaul after the 2.9.5 version (January ++).
    An XML report will be added as well

    - Item selection for reports:
    Next version. Reports will be based on filters (which can
    be saved and reused) or on all items in the database.
    Target: 10/12/2006

     
  • Robert Jan van der Waals

    Logged In: YES
    user_id=455224
    Originator: NO

    Bare with me here.. Data Crow's reporting mechanism will be changed after the 2.9.5 version.
    The 2.9.5 version is to be released at the end of February 2007. This request will be implemented
    in this new reporting mechanism.

    Sorry for the long wait,
    cheers,
    Robert Jan

     
  • Robert Jan van der Waals

    Logged In: YES
    user_id=455224
    Originator: NO

    Hi Markus,

    I hope you are still a satisfied user of Data Crow. I will
    release Data Crow 2.9.5 tonight after which I will focus on the
    reporting functionality.

    There are three ways to go with the new reporting mechanism:
    - Make sure Data Crow delivers data sets which can be used in
    other reporting tools
    - Use an open source library which is more powerful and flexible
    then the one I created
    - Upgrade the existing reporting mechanism (which I don't really want
    to do as this might become a project on itself and should not become
    the main focus of the Data Crow project).

    In all of these cases an Xml report will be made available.

    Any advice in this matter would be most appreciated! :)

    Robert Jan

     
  • Anonymous

    Anonymous - 2007-01-27

    Logged In: YES
    user_id=1584800
    Originator: YES

    hello,

    well, here is what i would do:

    i would not put much effort in an own reporting system, as there are a lot developend frameworks out there for doing so. for DC, i'd present the user a dialog quite like the one you currently have. no matter what the user selected, i'd let DC write an interim-xml file containing all the items to be reported in a very simple xml format:
    books
    book
    title
    id
    isbn

    and so on. if the user wanted "xml only", that's what he gets. if he wanted a fancy version (html output or pdf), i'd write XSLTs do convert that xml to html directly using xalan, or to XSL-FO, which i would throw into FOP (also from apache) to generate PDF. that output would then go to the user-specified output folder. i personally have some experience with FOP (layouting mass-mailing letters and double-sided japanese vocabulary cards for example), and despite some criticisms i think it is fast enough for this kind of operation.

    the idea is, that all reports a user can choose, are xslt files in a folder of DC. if a user wants to create a custom report, he can just add new xsl files into that folder, and DC would show them.

    so, to answer your question hopefully, i'd go for your suggestion 1 AND 2, so that your own reports are nothing differend from the ones a user can make/add. you could also encourage your users to send them their custom xslts back to you, so that you can integrate it into DC if they are nice and usefull.

    whether you want to use XSLTs or not directly in DC, or want to use FOP or not, my main point for this case was that - in case you don't want to - i can grab that raw xml somewhere, so that i can make my own XSLT around it.

    markus

     
  • Robert Jan van der Waals

    Logged In: YES
    user_id=455224
    Originator: NO

    Hi Markus,

    Thank you for your explanation!

    I will be using Jasper Reports for generating the reports.
    Data Crow will generate XML files which can be used by Jasper Reports
    and of course other reporting tools. I can see the benefit of allowing
    user to create their own reports using XSLT and / or Jasper Reports.

    Data Crow will allow users to add their own Jasper Report
    file to a folder of which the content will be selectable from the
    Report Dialog.

    I will need to delve into the XSLT part as I have no experience
    using the xalan and FOP libraries. I do not promise anything on the
    XSLT part but I intend to allow both XSLT files and Japser Report files..

    The upcoming beta will have the new reporting mechanism.

    Cheers,
    Robert Jan

     
  • Robert Jan van der Waals

    • milestone: --> Next_Release
    • priority: 5 --> 9
     
  • Robert Jan van der Waals

    Logged In: YES
    user_id=455224
    Originator: NO

    Implemented and to be released this week.
    A simple XML report with a XSD for validation.

    XSLT will be the next step (or either IReports, but so far
    I am not really impressed with the "ease" of report creation
    they offer). These steps we discussed all fall under the
    planned overhaul of the reporting functionality.

     
  • Robert Jan van der Waals

    • status: open --> closed-fixed
     

Log in to post a comment.