I'm considering using ListX, an additional table (one to one with RepositoryObjects), and a view, to "add" fields to Repository objects. Just looking over the db schema. Is there a diagram of that someplace? I would like to do this as unobtrusively and safely as possible, if it is possible. The only entity that isn't immediately obvious to me, at first glance, is RepositoryObjectValues. What is that?

Thanks for any advice you have.

jb

Thanks. That's helpful, because I have been wondering about the consequences of populating attributes with many values (possibly hundreds). In the application that I'm considering, this could be done outside the Repository. Also, the uploads could be done with another application, then we'd use the Repository for presentation only. This seems like it would be perfect for getting our requirements met very quickly, at least in a preliminary way, but I don't know what kind of 'gotchas' or performance issues would appear. Any hints?

Actually, what I'm hoping for in a future release is administrator-definable add-on fields for the Repository where users could supply the vlaues via the upload form. Looks like the 'attributes' structure could provide something like that.