On Mon, Aug 5, 2013 at 6:14 PM, Mark H. Wood <mw...@iupui.edu> wrote: > From time to time someone suggests that an operation to be applied > across all EPersons would of course be done using a curation task.
You can easily abuse a curation task for that. You'll simply ignore the handle (I specify 123456789/0) and loop over all epersons, or epersons with a particular property you need. I see how adding an eperson id/email/netid on the curation task command line could be useful. But then we might ask ourselves why don't we generalize this for all current and future DSpace objects. Bitstreams? Bundles? Handles? DOIs? Authors? Organizational units? Journals? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
