[Flask] Advice on best way :

Jonathan Chen tamasiaina at gmail.com
Thu Sep 26 05:47:22 EDT 2019

Hey Ben,

I have dealt with implementing an ERP System in the past (Oracle E-Business
Suite). There are some things though that depend on the scope of the
project. I'll be honest though depending on how large the project is and
how many people will be interacting with it, it could take a long time to
develop this system. If you have to deal with legacy data as well it can
add more time to it depending on how clean the data is. The key thing
though is that there should be good documentation on how to use and develop
the system. Are you a company building the software for the Courts or do
you work for the Chancery Courts? I'm free to talk on a private basis as

~Jonathan C.

On Wed, Sep 25, 2019 at 10:03 PM Gergely Polonkai <gergely at polonkai.eu>

> What you outlined here /is/ a full fledged ERP system. Without the actual
> requirement list itʼs somewhat impossible to devise anything. You should
> find a trustworthy software architect to do it. And that ainʼt cheap,
> especially given that this is for some government thingie (most people will
> double their price for govts).
> So if you need true advice here, youʼd better share the full requirements
> list which might even be illegal depending on your contract. If you donʼt
> have that, i think you shouldnʼt start the project.
> Best,
> Gergely
> On Wed, 25 Sep 2019, 21:02 Ben Duncan, <linux4ms at gmail.com> wrote:
>> Ok, have all my session, wtf_forms, libraries all sorted as well as some
>> nice macros for the templates, now seeking advice to build this whole
>> application.
>> It is basically a full fledged Accounting system (AR / AP / GL / OE /IV /
>> PR / PO ) fronted by a some very specific Court front ends (fees. fines,
>> restitution  )  for the Criminal / Civil side and then some stuff latter to
>> deal with the Chancery Courts.
>> It's going to be quite large, probably with a few hundred web pages ,
>> with interfacing with all the systems (Think ERP) with drill downs all the
>> way back to the originating document.
>> Any advice on how to structure, what next I need to read, design
>> considerations or any other adice this group can give me, would be
>> appreciated
>> Thanks ...
>> *Ben Duncan*
>> DBA / Chief Software Architect
>> Mississippi State Supreme Court
>> Electronic Filing Division
>> _______________________________________________
>> Flask mailing list
>> Flask at python.org
>> https://mail.python.org/mailman/listinfo/flask
> _______________________________________________
> Flask mailing list
> Flask at python.org
> https://mail.python.org/mailman/listinfo/flask
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/flask/attachments/20190926/f1625dae/attachment.html>

More information about the Flask mailing list