database metadata

[Emile Kok <em...@toughguy.net>]

Has anyone any idea of how metadata for tables and fields could be 
generated at time of creation (ant init).  What I mean by this is 
user-specified fields which could be used to define and reference the 
current data fields and structures.  That way the fields could be easily 
presented to the user in a user-friendly way (descriptions) for flagging by 
the user in some way or a variety of ways (possibly fields made invisible, 
made private to communities or groups).  Also forms could be quickly 
generated for data capture or for reporting/tabulation, rules applied, 
etc.  Once in place, layers of rule-based business logic, personalisation, 
workflow could sit on top.

If this isn't available, I'd like to have a stab at it and would be keen to 
have input on how to engineer this.  I'm officially an architect, so might 
need some review of my coding (or some help), if it pans out that way.

:-)
Emile



---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org

Re: database metadata

[Rodney Schneider <ro...@bicamera.com>]

Hi,

You might want to take a look at DbForms for some ideas:

http://www.dbforms.org/
http://www.onjava.com/pub/a/onjava/2001/07/18/dbforms.html

It is based on Struts, and therefore JSPs and taglibs, but it would be
useful if you could come up with something similar based on Turbine and
Velocity.

Regards,

-- Rodney


On Wed, 22 Aug 2001, Emile Kok wrote:

> Has anyone any idea of how metadata for tables and fields could be
> generated at time of creation (ant init).  What I mean by this is
> user-specified fields which could be used to define and reference the
> current data fields and structures.  That way the fields could be easily
> presented to the user in a user-friendly way (descriptions) for flagging by
> the user in some way or a variety of ways (possibly fields made invisible,
> made private to communities or groups).  Also forms could be quickly
> generated for data capture or for reporting/tabulation, rules applied,
> etc.  Once in place, layers of rule-based business logic, personalisation,
> workflow could sit on top.
>
> If this isn't available, I'd like to have a stab at it and would be keen to
> have input on how to engineer this.  I'm officially an architect, so might
> need some review of my coding (or some help), if it pans out that way.
>
> :-)
> Emile


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org