New application under development - would like your thoughts

[xlar54]

Hey folks,

Im working on an application that I find would be useful where I work, and I am looking for some general feedback on the idea itself.  I trust that you guys would give me some honest and fair feedback, as most of you are in the IT field, some even in development.  

The idea is pretty simple.  I am merging the concept of a Wiki, with a data dictionary.  The application dynamically reads in SQL Server database schemas, and then developers can add meta data about the database objects.  So for instance, frequently where I work, tables are designed and fields are added, but in no time people forget what a table is used for, or a field, etc.  Using this system which I call 'Dataweb', developers can go in and collaboratively update information about the database, table, field or stored proc.  What its used for, by what application, etc.  Enumerations, etc.  

Of course the system includes a history of all changes, and admin level users can rollback edits, etc just like any ordinary wiki.  The real power comes from being able to search on a word or phrase, and a resultset comes back with all the objects which have the phrase in the meta data.  It also has various user accounts and privelege levels such that BAs can perhaps read but not modify, etc.

I love the idea of wikis, and I think that targeting areas where people tend to be weaker on documentation is really where these things shine.  If you guys think this is a worthy project, let me know and Ill post a url where the current build lives.  So far the database folks I have spoken with think this is a very useful application, as well as the developers.

Thanks

Scott / xlar54

[Guest]

It would be great if you combined this Wiki with the built in comment features that practically all RDBMS systems provide so that an edit to the WIKI causes an ALTER on the table's comments.

[hydrophilic]

The ability to search comments and rollback changes sounds useful.  The question is will anybody actually use it?  Payton made me think about this because most databases have fields for comments at the table and field level, but these are almost always blank!  At least on 99% projects I've been called to work on.  Honestly, I rarely use the comments myself.  (in a database -- in code I think I use too many comments)

Maybe the Wiki format will actually encourage comments / documentation.  That alone may be reason enough to do it.