On Wed, Mar 7, 2012 at 22:10, Anton Angelo <[email protected]> wrote: > 1) I want to change the input forms. Do I edit inport-forms.xml (as > attached) in [dspace-source] rebuild & redeploy? Or do I edit it in > [dspace] and restart tomcat?
As with any change in config/ you have 2 options: 1) edit it in [dspace-source] rebuild & redeploy 2) edit it in [dspace] and restart tomcat. IMPORTANT: also copy it to [dspace-source] so that you don't forget about the change and overwrite it with an older version next time you're rebuilding (e.g. during an upgrade) The first option takes some time. The second option is prone to you forgetting to copy the changes. > Or, do I use the handy-dandy metadata registry in the interface, and if so, > where are the docs for that? I think it's rather self-explanatory, but here's the documentation: https://wiki.duraspace.org/display/DSDOC18/Configuration#Configuration-TheMetadataFormatandBitstreamFormatRegistries > 2) My repository needs to be kept from prying eyes - not just the data, I > can use embargo for that (I think) but the whole shooting match. WHat do > people recommend as a method for that? .htaccess? There many options (mostly not specific to DSpace), depending on what you want to achieve. Most importantly, who do you want to allow access? If you can define it as an IP range, I would recommend using your OS firewall. Regards, ~~helix84 ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
