Digital Archive prototype

I need a database architecture that mimics a file system structure. It needs to meet the following criteria 1. It should have a folder concept, folders should be able to be nested in a hierarchy (parent child) 2. A folder has a defined set of metadata that items in this folder can have. If a metadata is mandatory the database need to enforce this via referential integrity or constraints. A performance test need to be made to check if root folders (including childfolders) perform better if each rootfolder have its own table and when adding child folders this just is a nullable new column in this table or if it is tha same to have a properly nomalized diagram. 3. A child folder must have the parents metadata but can specify more and stricter criteria, i.e parent have “name?? (not mandatory) then child can have “name?? (mandatory or not mandatory) 4. Essentially the folder concept is also just metadata but to allow the database structure to offer some RI (referential integrity) the folders should be kept in their own table possibly the metadatadefinitions as well?. 5. There should be no limit to the amount of metadata that can be defined on a folder. I need a simple working client that allows creation of new folders and new metadatadefintions, please continue work on the GUI shell attached. The client should use [login to view URL] 2. The coding guidelines that are to be followed for the client are here [login to view URL] This is a step 1 out of 4 or 5 initial steps to get a working applications fully running. Later steps will involve writing Google Desktop search plugins... Unittest for all code, code coverage at least 90%. Not for [login to view URL] 2 itself ofcourse UPDATE: I have updated the database attached in the main bid ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform c# 2.0, [login to view URL] 2, Sqlserver 2005 Express