A more general comment arising out of the discussion: IMHO attributes of specific repository objects should be *in the repository*, not buried in the ever-growing configuration. Whenever we find ourselves proposing to name specific object handles in a new config. term, we should look *hard* for a better way to do what is needed.
To the present issue: a list of config. terms is a reasonable first pass design, since we don't support container metadata yet. But when we do, we should go back and tuck things like this into the metadata, using the config. only to supply a default. Come to think of it, when containers have metadata record support, the default feedback address can be hung on the Site object and managed through the GUI. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart.
pgphX7n1lOwcp.pgp
Description: PGP signature
------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
